Add fortran compiler flags #148
Labels
No Label
blocked upstream
bug
build-failure
duplicate
enhancement
help wanted
informational
invalid
invalid/corrupt package
packaging issue
priority: high
question
support
wontfix
No Milestone
No project
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: ALHP/ALHP.GO#148
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
In
/etc/makepkg.conf
, we specifyCFLAGS
andCXXFLAGS
(as does ArchLinux). I think we should also be specifyingFFLAGS
(flags to be passed to a fortran 77 compiler) andFCFLAGS
(flags to be passed to a 9x compiler). Further documentation on this can be found in sections 8.14 and 8.15 in the automake documentation.I would suggest:
I'm not very familiar with fortran, should we be adding more flags? Test compiles of programs including fortran code, such as
libtool
worked fine with this flag added. Additionally, should I open an issue with Arch Linux upstream and see what they think about these flags before we add them here, potentially letting Arch Linux devs add them?As #149 describes, makepkg needs to know about that var otherwise it's not exported. So I think the only way besides a patched makepkg is to get it upstreamed or use whatever solution we can come up with for #149 (which affects GOAMD64).
https://bugs.archlinux.org/task/75893
Alright, let's see what happens.
To anyone who sees this:
If you have an Arch Linux Bugs account (or want to make one anyway) please go upvote this bug as fixing it is required to make any headway on this issue. Thanks so much for helping this amazing project as well as Arch Linux!
I added them to our flags to be exported in the
makepkg.conf
.