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