On 22/06/11 07:25, justin wrote: > On 22/06/11 06:31, Matthew Finkel wrote: >> On 06/21/11 23:55, Dale wrote: >>> I just did my updates and ran into this: >>> >>> * Maintainer: s...@gentoo.org >>> * USE: amd64 consolekit elibc_glibc kernel_linux multilib >>> policykit userland_GNU >>> * FEATURES: preserve-libs sandbox >>> >>> * Please install currently selected gcc version with USE=fortran. >>> * If you intend to use a different compiler then gfortran, please >>> * set FC variable accordingly and take care that the neccessary >>> * fortran dialects are support. >>> >>> * ERROR: sci-libs/blas-reference-20070226 failed (setup phase): >>> * Currently no working fortran compiler is available >>> * >>> * Call stack: >>> * ebuild.sh, line 56: Called pkg_setup >>> * ebuild.sh, line 1446: Called fortran-2_pkg_setup >>> * fortran-2.eclass, line 134: Called _die_msg >>> * fortran-2.eclass, line 120: Called die >>> * The specific snippet of code: >>> * die "Currently no working fortran compiler is available" >>> * >>> * If you need support, post the output of 'emerge --info >>> =sci-libs/blas-reference-20070226', >>> * the complete build log and the output of 'emerge -pqv >>> =sci-libs/blas-reference-20070226'. >>> * The complete build log is located at >>> '/var/log/portage/sci-libs:blas-reference-20070226:20110622-034357.log'. >>> * The ebuild environment file is located at >>> '/var/tmp/portage/sci-libs/blas-reference-20070226/temp/die.env'. >>> * S: >>> '/var/tmp/portage/sci-libs/blas-reference-20070226/work/lapack-lite-3.1.1' >>> >>>>>> Failed to emerge sci-libs/blas-reference-20070226, Log file: >>> >>>>>> >>> '/var/log/portage/sci-libs:blas-reference-20070226:20110622-034357.log' >>> root@fireball / # >>> >>> This is my gcc info: >>> >>> [ebuild R ] sys-devel/gcc-4.4.5 USE="gtk mudflap (multilib) nls >>> nptl openmp (-altivec) -bootstrap -build -doc (-fixed-point) -fortran >>> -gcj -graphite (-hardened) (-libffi) -multislot -nocxx -nopie -nossp >>> -objc -objc++ -objc-gc -test -vanilla" >>> >>> So, does everyone need to turn on the fortran USE flag so that they >>> don't break anything? May I also add, the USE flag description is >>> worth about as much as a screen door on a submarine. >>> >>> fortran - Adds support for fortran (formerly f77) >>> >>> That doesn't tell me very much. >>> >>> Heads up for folks about to do their updates, check into the USE flag >>> fortran to see if you need to add it to yours before updating a bunch >>> of stuff. >>> >>> Dale >>> >>> :-) :-) >>> >> If I had to guess, I'd say =sci-libs/blas-reference-20070226 requires >> fortran (ebuild depends on it) and you don't have another fortran >> compiler installed. >> >> Could be wrong though. >> >> - Matt >> > > That's right, > > blas-reference is written in fortran. > > 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 >
One little note, if portage requests that you should install dev-lang/ifc instead of gcc[fortran], you most probably have an entry sys-devel/gcc -fortran in your /etc/portage/package.use Just remove that. justin
signature.asc
Description: OpenPGP digital signature
