On 6/25/2011 8:04 AM, Dale wrote:
We restructured the dependency chain for fortran support,
which includes
a compile test now. The failure can be seen above.
The Problem was in short, USE=fortran was enabled by
default for linux
arches, but people tend to disable it. Depending on
gcc[fortran] doesn't
work completely as gcc:4.4[fortran] and gcc:4.5[-fortran]
with gcc-4.5
select can be installed, which would full fill the
dependency but
nevertheless doesn't give a working compiler.
So now packages depend on virtual/fortran and use an
eclass to check for
a working compiler. So if you see this message, this means
you somehow
worked around gcc[fortran].
That make sense?
Yes. He's saying they didn't change the USE flag, they
changed the fortran dependency test to actually do a
run-time check for fortran because the USE flag alone wasn't
sufficient.
Which means you most likely had a non-working cantor and no
fortran compiler before and just didn't notice :)
--Mike
