| 1 |
I just did my updates and ran into this: |
| 2 |
|
| 3 |
* Maintainer: sci@g.o |
| 4 |
* USE: amd64 consolekit elibc_glibc kernel_linux multilib |
| 5 |
policykit userland_GNU |
| 6 |
* FEATURES: preserve-libs sandbox |
| 7 |
|
| 8 |
* Please install currently selected gcc version with USE=fortran. |
| 9 |
* If you intend to use a different compiler then gfortran, please |
| 10 |
* set FC variable accordingly and take care that the neccessary |
| 11 |
* fortran dialects are support. |
| 12 |
|
| 13 |
* ERROR: sci-libs/blas-reference-20070226 failed (setup phase): |
| 14 |
* Currently no working fortran compiler is available |
| 15 |
* |
| 16 |
* Call stack: |
| 17 |
* ebuild.sh, line 56: Called pkg_setup |
| 18 |
* ebuild.sh, line 1446: Called fortran-2_pkg_setup |
| 19 |
* fortran-2.eclass, line 134: Called _die_msg |
| 20 |
* fortran-2.eclass, line 120: Called die |
| 21 |
* The specific snippet of code: |
| 22 |
* die "Currently no working fortran compiler is available" |
| 23 |
* |
| 24 |
* If you need support, post the output of 'emerge --info |
| 25 |
=sci-libs/blas-reference-20070226', |
| 26 |
* the complete build log and the output of 'emerge -pqv |
| 27 |
=sci-libs/blas-reference-20070226'. |
| 28 |
* The complete build log is located at |
| 29 |
'/var/log/portage/sci-libs:blas-reference-20070226:20110622-034357.log'. |
| 30 |
* The ebuild environment file is located at |
| 31 |
'/var/tmp/portage/sci-libs/blas-reference-20070226/temp/die.env'. |
| 32 |
* S: |
| 33 |
'/var/tmp/portage/sci-libs/blas-reference-20070226/work/lapack-lite-3.1.1' |
| 34 |
|
| 35 |
>>> Failed to emerge sci-libs/blas-reference-20070226, Log file: |
| 36 |
|
| 37 |
>>> |
| 38 |
'/var/log/portage/sci-libs:blas-reference-20070226:20110622-034357.log' |
| 39 |
root@fireball / # |
| 40 |
|
| 41 |
This is my gcc info: |
| 42 |
|
| 43 |
[ebuild R ] sys-devel/gcc-4.4.5 USE="gtk mudflap (multilib) nls |
| 44 |
nptl openmp (-altivec) -bootstrap -build -doc (-fixed-point) -fortran |
| 45 |
-gcj -graphite (-hardened) (-libffi) -multislot -nocxx -nopie -nossp |
| 46 |
-objc -objc++ -objc-gc -test -vanilla" |
| 47 |
|
| 48 |
So, does everyone need to turn on the fortran USE flag so that they |
| 49 |
don't break anything? May I also add, the USE flag description is |
| 50 |
worth about as much as a screen door on a submarine. |
| 51 |
|
| 52 |
fortran - Adds support for fortran (formerly f77) |
| 53 |
|
| 54 |
That doesn't tell me very much. |
| 55 |
|
| 56 |
Heads up for folks about to do their updates, check into the USE flag |
| 57 |
fortran to see if you need to add it to yours before updating a bunch of |
| 58 |
stuff. |
| 59 |
|
| 60 |
Dale |
| 61 |
|
| 62 |
:-) :-) |
Archives