On 06/22/11 14:10, Dale wrote: > I put -fortran in make.conf. I ran emerge -uvDNa world and let it > rebuild a few packages. Then I get this: > > >>> Emerging (1 of 2) sci-libs/blas-reference-20070226 > * lapack-lite-3.1.1.tgz RMD160 SHA1 SHA256 size ;-) > ... > > [ ok ] > * Package: sci-libs/blas-reference-20070226 > * Repository: gentoo > * 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-180601.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-180601.log' > root@fireball / # > > Am I going in circles again? I don't drink because I don't like being > drunk. I also don't spin around in my chair for the same reason. One > of those may be needed to reverse the problem here. > > Now to go see how to fix this mess once and for all. > > Dale > > :-) :-) >
Do correct me if I'm wrong, but wasn't blas-reference pulled in by merging gcc with USE="fortran"? Or did you install blas-reference for another reason?
