Neil Bothwick wrote:
On Fri, 24 Jun 2011 22:29:12 -0500, Dale wrote:
I guess my first post was correct after all. Enable fortran USE flag
and keep things as it was before it got changed. It was working
fine.
Isn't that flag enabled by default? All you have yo do is not disable
it.
You seem to have forgot the dev had changed it. Since it got noticed
and all the dev changed it back in about a day or so. So, it was
enabled, got disabled by a dev then got enabled again by the same dev.
ISTR reading some mention of that. Do you mean the profile was changed?
That sounds a bit naughty, changing a profile should be done on a version
bump IMO.
I don't know for sure where it was changed but the dev that did the
change posted this:
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].
justin
That make sense?
Dale
:-) :-)
