1 |
On 22/06/11 07:25, justin wrote: |
2 |
> On 22/06/11 06:31, Matthew Finkel wrote: |
3 |
>> On 06/21/11 23:55, Dale wrote: |
4 |
>>> I just did my updates and ran into this: |
5 |
>>> |
6 |
>>> * Maintainer: sci@g.o |
7 |
>>> * USE: amd64 consolekit elibc_glibc kernel_linux multilib |
8 |
>>> policykit userland_GNU |
9 |
>>> * FEATURES: preserve-libs sandbox |
10 |
>>> |
11 |
>>> * Please install currently selected gcc version with USE=fortran. |
12 |
>>> * If you intend to use a different compiler then gfortran, please |
13 |
>>> * set FC variable accordingly and take care that the neccessary |
14 |
>>> * fortran dialects are support. |
15 |
>>> |
16 |
>>> * ERROR: sci-libs/blas-reference-20070226 failed (setup phase): |
17 |
>>> * Currently no working fortran compiler is available |
18 |
>>> * |
19 |
>>> * Call stack: |
20 |
>>> * ebuild.sh, line 56: Called pkg_setup |
21 |
>>> * ebuild.sh, line 1446: Called fortran-2_pkg_setup |
22 |
>>> * fortran-2.eclass, line 134: Called _die_msg |
23 |
>>> * fortran-2.eclass, line 120: Called die |
24 |
>>> * The specific snippet of code: |
25 |
>>> * die "Currently no working fortran compiler is available" |
26 |
>>> * |
27 |
>>> * If you need support, post the output of 'emerge --info |
28 |
>>> =sci-libs/blas-reference-20070226', |
29 |
>>> * the complete build log and the output of 'emerge -pqv |
30 |
>>> =sci-libs/blas-reference-20070226'. |
31 |
>>> * The complete build log is located at |
32 |
>>> '/var/log/portage/sci-libs:blas-reference-20070226:20110622-034357.log'. |
33 |
>>> * The ebuild environment file is located at |
34 |
>>> '/var/tmp/portage/sci-libs/blas-reference-20070226/temp/die.env'. |
35 |
>>> * S: |
36 |
>>> '/var/tmp/portage/sci-libs/blas-reference-20070226/work/lapack-lite-3.1.1' |
37 |
>>> |
38 |
>>>>>> Failed to emerge sci-libs/blas-reference-20070226, Log file: |
39 |
>>> |
40 |
>>>>>> |
41 |
>>> '/var/log/portage/sci-libs:blas-reference-20070226:20110622-034357.log' |
42 |
>>> root@fireball / # |
43 |
>>> |
44 |
>>> This is my gcc info: |
45 |
>>> |
46 |
>>> [ebuild R ] sys-devel/gcc-4.4.5 USE="gtk mudflap (multilib) nls |
47 |
>>> nptl openmp (-altivec) -bootstrap -build -doc (-fixed-point) -fortran |
48 |
>>> -gcj -graphite (-hardened) (-libffi) -multislot -nocxx -nopie -nossp |
49 |
>>> -objc -objc++ -objc-gc -test -vanilla" |
50 |
>>> |
51 |
>>> So, does everyone need to turn on the fortran USE flag so that they |
52 |
>>> don't break anything? May I also add, the USE flag description is |
53 |
>>> worth about as much as a screen door on a submarine. |
54 |
>>> |
55 |
>>> fortran - Adds support for fortran (formerly f77) |
56 |
>>> |
57 |
>>> That doesn't tell me very much. |
58 |
>>> |
59 |
>>> Heads up for folks about to do their updates, check into the USE flag |
60 |
>>> fortran to see if you need to add it to yours before updating a bunch |
61 |
>>> of stuff. |
62 |
>>> |
63 |
>>> Dale |
64 |
>>> |
65 |
>>> :-) :-) |
66 |
>>> |
67 |
>> If I had to guess, I'd say =sci-libs/blas-reference-20070226 requires |
68 |
>> fortran (ebuild depends on it) and you don't have another fortran |
69 |
>> compiler installed. |
70 |
>> |
71 |
>> Could be wrong though. |
72 |
>> |
73 |
>> - Matt |
74 |
>> |
75 |
> |
76 |
> That's right, |
77 |
> |
78 |
> blas-reference is written in fortran. |
79 |
> |
80 |
> We restructured the dependency chain for fortran support, which includes |
81 |
> a compile test now. The failure can be seen above. |
82 |
> |
83 |
> The Problem was in short, USE=fortran was enabled by default for linux |
84 |
> arches, but people tend to disable it. Depending on gcc[fortran] doesn't |
85 |
> work completely as gcc:4.4[fortran] and gcc:4.5[-fortran] with gcc-4.5 |
86 |
> select can be installed, which would full fill the dependency but |
87 |
> nevertheless doesn't give a working compiler. |
88 |
> |
89 |
> So now packages depend on virtual/fortran and use an eclass to check for |
90 |
> a working compiler. So if you see this message, this means you somehow |
91 |
> worked around gcc[fortran]. |
92 |
> |
93 |
> |
94 |
> justin |
95 |
> |
96 |
|
97 |
One little note, |
98 |
|
99 |
if portage requests that you should install dev-lang/ifc instead of |
100 |
gcc[fortran], you most probably have an entry |
101 |
|
102 |
sys-devel/gcc -fortran |
103 |
|
104 |
in |
105 |
|
106 |
your /etc/portage/package.use |
107 |
|
108 |
Just remove that. |
109 |
|
110 |
justin |