I just tried to install dev-python/rpy. This led to a dependency on sci-libs/blas-reference, which failed in a non-standard way because my gcc wasn't compiled with fortran enabled. This should be fixed somehow (i.e. enabling fortran for sys-devel/gcc, then restarting the emerge should be enough to fix it).
Please attach full build.log and output of emerge --info sci-libs/blas-reference please. The ebuild uses the fortran.eclass which should check for available fortran compilers and die in case there is none. I this mechanism doesn't work, we have to workout why.
It *did* work, it'd just be nice if it used the standard mechanism of doing so (gcc[fortran]) instead of having custom handling that requires taking extra steps.
(In reply to comment #2) > It *did* work, it'd just be nice if it used the standard mechanism of doing so > (gcc[fortran]) instead of having custom handling that requires taking extra > steps. > As you probably know there are more than one fortran compiler available in the tree. So one is able to compile the package with gcc[-fortran]. Therefor we are using the fortran.eclass to check for available and working fortran compiler. And forcing gcc[fortran] is _no_ solution in that case. So please provide the requested information, so that we can find out, why the eclass didn't die, as you have no working compiler installed.
Like I said, it *did* die as wanted. If there are multiple fortran compilers, why not DEPEND on || ( gcc[fortran] other-compiler )? What does the manual check provide?
Okay, sorry. I understand it that way, that the emerged failed but the eclass didn't die. You are right, we should rewrite the eclass to use EAPI="2" and have USEdeps. I will take a look into that.
(In reply to comment #5) > You are right, we should rewrite the eclass to use EAPI="2" and have USEdeps. I > will take a look into that. > I have been trying to avoid the fortran eclass for a while in all ebuilds I touch, it is buggy and obsolete. But I am not sure enforcing compiler dependency is a good idea. May be we should try to have a mechanism which pulls gcc[fortran] if no fortran compiler is to be found (e.g. as checking that FC or F77 variable compiles a very simple program). This way we leave it open to any fortran compiler.
*** Bug 338659 has been marked as a duplicate of this bug. ***
fortran.eclass isn't used any more in the tree.
