Gentoo Archives: gentoo-user

From: Dale <rdalek1967@×××××.com>
To: gentoo-user@l.g.o
Subject: Re: [gentoo-user] Do we have to build gcc with fortran now?
Date: Wed, 22 Jun 2011 20:56:54
Message-Id: 4E0256B0.4010105@gmail.com
In Reply to: Re: [gentoo-user] Do we have to build gcc with fortran now? by Matthew Finkel
1 Matthew Finkel wrote:
2 > On 06/22/11 14:10, Dale wrote:
3 >
4 >> I put -fortran in make.conf. I ran emerge -uvDNa world and let it
5 >> rebuild a few packages. Then I get this:
6 >>
7 >>
8 >>>>> Emerging (1 of 2) sci-libs/blas-reference-20070226
9 >>>>>
10 >> * lapack-lite-3.1.1.tgz RMD160 SHA1 SHA256 size ;-)
11 >> ...
12 >> [ ok ]
13 >> * Package: sci-libs/blas-reference-20070226
14 >> * Repository: gentoo
15 >> * Maintainer: sci@g.o
16 >> * USE: amd64 consolekit elibc_glibc kernel_linux multilib
17 >> policykit userland_GNU
18 >> * FEATURES: preserve-libs sandbox
19 >>
20 >> * Please install currently selected gcc version with USE=fortran.
21 >> * If you intend to use a different compiler then gfortran, please
22 >> * set FC variable accordingly and take care that the neccessary
23 >> * fortran dialects are support.
24 >>
25 >> * ERROR: sci-libs/blas-reference-20070226 failed (setup phase):
26 >> * Currently no working fortran compiler is available
27 >> *
28 >> * Call stack:
29 >> * ebuild.sh, line 56: Called pkg_setup
30 >> * ebuild.sh, line 1446: Called fortran-2_pkg_setup
31 >> * fortran-2.eclass, line 134: Called _die_msg
32 >> * fortran-2.eclass, line 120: Called die
33 >> * The specific snippet of code:
34 >> * die "Currently no working fortran compiler is available"
35 >> *
36 >> * If you need support, post the output of 'emerge --info
37 >> =sci-libs/blas-reference-20070226',
38 >> * the complete build log and the output of 'emerge -pqv
39 >> =sci-libs/blas-reference-20070226'.
40 >> * The complete build log is located at
41 >> '/var/log/portage/sci-libs:blas-reference-20070226:20110622-180601.log'.
42 >> * The ebuild environment file is located at
43 >> '/var/tmp/portage/sci-libs/blas-reference-20070226/temp/die.env'.
44 >> * S:
45 >> '/var/tmp/portage/sci-libs/blas-reference-20070226/work/lapack-lite-3.1.1'
46 >>
47 >>
48 >>>>> Failed to emerge sci-libs/blas-reference-20070226, Log file:
49 >>>>>
50 >>
51 >>>>>
52 >> '/var/log/portage/sci-libs:blas-reference-20070226:20110622-180601.log'
53 >> root@fireball / #
54 >>
55 >> Am I going in circles again? I don't drink because I don't like being
56 >> drunk. I also don't spin around in my chair for the same reason. One
57 >> of those may be needed to reverse the problem here.
58 >>
59 >> Now to go see how to fix this mess once and for all.
60 >>
61 >> Dale
62 >>
63 >> :-) :-)
64 >>
65 >>
66 > Do correct me if I'm wrong, but wasn't blas-reference pulled in by
67 > merging gcc with USE="fortran"? Or did you install blas-reference for
68 > another reason?
69 >
70 >
71 >
72 >
73
74
75 No clue. I just -c'd some stuff and kept running revdep-rebuild and
76 emerge -uvDNa world until it all got sorted. It took a few times but I
77 finally got a clean result.
78
79 The funny thing is this. I removed about 3 packages but had to install
80 close to a dozen to satisfy what was missing. Cantore, or something
81 like that, was left with no backend when I removed R.
82
83 So, removed some bloat then installed some more bloat. Ain't that a peach?
84
85 Dale
86
87 :-) :-)

Replies

Subject Author
Re: [gentoo-user] Do we have to build gcc with fortran now? Todd Goodman <tsg@×××××××××.net>