[MacPorts] #57365: slatec @4.1: f77: No such file or directory
MacPorts
noreply at macports.org
Fri Oct 19 10:37:20 UTC 2018
#57365: slatec @4.1: f77: No such file or directory
-------------------------+----------------------
Reporter: ryandesign | Owner: smaret
Type: defect | Status: reopened
Priority: Normal | Milestone:
Component: ports | Version:
Resolution: | Keywords:
Port: slatec |
-------------------------+----------------------
Comment (by smaret):
Replying to [comment:7 ryandesign]:
> This port uses the compilers portgroup, which I have never understood
very well, so it is difficult for me to know in advance what will work and
what will not. Now that I look at it closer, I understand that the
compilers portgroup creates variants for you to choose what compiler to
use, and the code that chooses that compiler is in each variant. Variants
get evaluated after the main part of the portfile has been evaluated,
which is why adding `FC=${configure.fc}` to `build.args` in the main part
of the portfile doesn't work right, because `configure.fc` hasn't been set
by that point. But appending to `build.args` in a `pre-fetch` block wasn't
right either, since the fetch phase doesn't need that information; the
build phase does. So it should be done in a pre-build block.
Thanks for looking into this. I've tried to set FC in a pre-build block
(with an export) but it didn't work either. The only solution I could come
up with is the following:
{{{
build {
system -W ${worksrcpath} "${build.cmd} -j${build.jobs}
FC=${configure.fc} ${build.target}"
}
}}}
Not very elegant, but it works.
--
Ticket URL: <https://trac.macports.org/ticket/57365#comment:9>
MacPorts <https://www.macports.org/>
Ports system for macOS
More information about the macports-tickets
mailing list