Bug 146448 – g77 / gfortran and blas / lapack

• Status: RESOLVED FIXED
• Product: Gentoo Linux

[Description nicolas regnault 2006-09-05 13:31:56 UTC]

Since the gcc update from 3.4.6 to 4.1.1, the following ebuilds 
sys-cluster/lam-mpi-7.0.4
sci-libs/lapack-3.0-r1
sci-libs/blas-19980702-r1
complain about lacking g77 compiler. This should be related to the new name of g77 in gcc-4.1.1 (gfortran).

[Comment 1 Jukka Ruohonen 2006-09-11 06:29:55 UTC]

Just a footnote:

at least sci-libs/blas-19980702-r2 and sci-libs/lapack-3.0-r1 compiled fine on ~amd64 by just changing the name of g77 to gfortran, although the bug was still open in 11.9.2006.

[Comment 2 Heitzso 2006-09-16 09:12:42 UTC]

Another problem is you are instructed to emerge an earlier version of gcc w/ FORTRAN USE flag set.  This may be okay (I did it) but blas still does not compile because the new g77 executable has a version tag attached.  I then created a sym link to /usr/bin/g77* from /usr/bin/g77 and that allowed blas to compile.  I don't know if the compiler ABI cross up between the compiler versions will break everything, i.e. something compiled gcc 4.x calling blas library that was compiled gcc 3.x.  Please clarify whether I should, instead, of linked to gfortran, and what possible problems might arise. I also noticed a number of other dev/sci libraries and/or programs that are likewise still limited to g77.  Thanks.

[Comment 3 Martin Mokrejš 2006-09-20 01:25:46 UTC]

I have similar problem with gromacs unable to find g77. Yes, I have gcc-4.1.1-r1:

/etc
/etc/env.d
/etc/env.d/gcc
/etc/env.d/gcc/i686-pc-linux-gnu-4.1.1
/etc/eselect
/etc/eselect/compiler
/etc/eselect/compiler/i686-pc-linux-gnu-4.1.1.conf
/usr
/usr/bin
/usr/bin/c++-4.1.1
/usr/bin/cpp-4.1.1
/usr/bin/g++-4.1.1
/usr/bin/gcc-4.1.1
/usr/bin/gfortran-4.1.1
/usr/bin/i686-pc-linux-gnu-c++-4.1.1
/usr/bin/i686-pc-linux-gnu-cpp-4.1.1
/usr/bin/i686-pc-linux-gnu-g++-4.1.1
/usr/bin/i686-pc-linux-gnu-gcc-4.1.1
/usr/bin/i686-pc-linux-gnu-gfortran-4.1.1
/usr/i686-pc-linux-gnu
/usr/i686-pc-linux-gnu/gcc-bin
/usr/i686-pc-linux-gnu/gcc-bin/4.1.1
/usr/i686-pc-linux-gnu/gcc-bin/4.1.1/c++
/usr/i686-pc-linux-gnu/gcc-bin/4.1.1/cpp
/usr/i686-pc-linux-gnu/gcc-bin/4.1.1/g++
/usr/i686-pc-linux-gnu/gcc-bin/4.1.1/gcc
/usr/i686-pc-linux-gnu/gcc-bin/4.1.1/gccbug
/usr/i686-pc-linux-gnu/gcc-bin/4.1.1/gcov
/usr/i686-pc-linux-gnu/gcc-bin/4.1.1/gfortran
/usr/i686-pc-linux-gnu/gcc-bin/4.1.1/i686-pc-linux-gnu-c++
/usr/i686-pc-linux-gnu/gcc-bin/4.1.1/i686-pc-linux-gnu-cpp
/usr/i686-pc-linux-gnu/gcc-bin/4.1.1/i686-pc-linux-gnu-g++
/usr/i686-pc-linux-gnu/gcc-bin/4.1.1/i686-pc-linux-gnu-gcc
/usr/i686-pc-linux-gnu/gcc-bin/4.1.1/i686-pc-linux-gnu-gcc-4.1.1
/usr/i686-pc-linux-gnu/gcc-bin/4.1.1/i686-pc-linux-gnu-gfortran
/usr/i686-pc-linux-gnu/gcc-bin/4.1.1/protoize
/usr/i686-pc-linux-gnu/gcc-bin/4.1.1/unprotoize


while previously had

/etc
/etc/env.d
/etc/env.d/gcc
/etc/env.d/gcc/i686-pc-linux-gnu-3.4.6
/etc/env.d/gcc/i686-pc-linux-gnu-3.4.6-hardened
/etc/env.d/gcc/i686-pc-linux-gnu-3.4.6-hardenednopie
/etc/env.d/gcc/i686-pc-linux-gnu-3.4.6-hardenednopiessp
/etc/env.d/gcc/i686-pc-linux-gnu-3.4.6-hardenednossp
/etc/eselect
/etc/eselect/compiler
/etc/eselect/compiler/i686-pc-linux-gnu-3.4.6.conf
/usr
/usr/bin
/usr/bin/c++-3.4.6
/usr/bin/cpp-3.4.6
/usr/bin/g++-3.4.6
/usr/bin/g77-3.4.6
/usr/bin/gcc-3.4.6
/usr/bin/i686-pc-linux-gnu-c++-3.4.6
/usr/bin/i686-pc-linux-gnu-cpp-3.4.6
/usr/bin/i686-pc-linux-gnu-g++-3.4.6
/usr/bin/i686-pc-linux-gnu-g77-3.4.6
/usr/bin/i686-pc-linux-gnu-gcc-3.4.6
/usr/i686-pc-linux-gnu
/usr/i686-pc-linux-gnu/gcc-bin
/usr/i686-pc-linux-gnu/gcc-bin/3.4.6
/usr/i686-pc-linux-gnu/gcc-bin/3.4.6/c++
/usr/i686-pc-linux-gnu/gcc-bin/3.4.6/cpp
/usr/i686-pc-linux-gnu/gcc-bin/3.4.6/g++
/usr/i686-pc-linux-gnu/gcc-bin/3.4.6/g77
/usr/i686-pc-linux-gnu/gcc-bin/3.4.6/gcc
/usr/i686-pc-linux-gnu/gcc-bin/3.4.6/gccbug
/usr/i686-pc-linux-gnu/gcc-bin/3.4.6/gcov
/usr/i686-pc-linux-gnu/gcc-bin/3.4.6/i686-pc-linux-gnu-c++
/usr/i686-pc-linux-gnu/gcc-bin/3.4.6/i686-pc-linux-gnu-cpp
/usr/i686-pc-linux-gnu/gcc-bin/3.4.6/i686-pc-linux-gnu-g++
/usr/i686-pc-linux-gnu/gcc-bin/3.4.6/i686-pc-linux-gnu-g77
/usr/i686-pc-linux-gnu/gcc-bin/3.4.6/i686-pc-linux-gnu-gcc
/usr/i686-pc-linux-gnu/gcc-bin/3.4.6/i686-pc-linux-gnu-gcc-3.4.6
/usr/i686-pc-linux-gnu/gcc-bin/3.4.6/protoize
/usr/i686-pc-linux-gnu/gcc-bin/3.4.6/unprotoize


It seems to me something similar to gcc-config should exist. eselect-compiler is not an option for me as it broke my system (which seems to be well-known issue). So, shall I introduce myself symlink as /usr/bin/g77 or will some ebuild do it for me? Or a tool?

I have gcc-3.4.6 and 4.1.1 installed, but obviously prefer 4.1.1. ;-)

[Comment 4 Jukka Ruohonen 2006-09-20 03:43:20 UTC]

Hi,

I resolved the issue by making the mentioned symlink of ln -s /usr/bin/gfortran /usr/bin/g77, which enabled both packages to emerge fine, although, as my message was only a footnote, I haven't actually yet done any real work with blas nor lapack. 

Please note that according to #30453 and #131974 both sci-libs/blas and sci-libs/lapack are deprecated in favour of the new blas-* and lapack-*. Note also the #147159 and the new eselect modules for blas, cblas and atlas. The new versions sci-libs/blas-reference-19940131-r4 and sci-libs/lapack-reference-3.0-r4 include references also to gfortran. (Both compiled fine on amd64 with gcc 4.1.1-r1 and without any fuzzy symlinks.) Thus, it seems that the issue is going to be resolved when the move to the new packages happens.

[Comment 5 Donnie Berkholz (RETIRED) 2006-09-26 01:07:38 UTC]

Newer lam-mpi is stable now on x86 at least.

[Comment 6 Bo Ørsted Andresen (RETIRED) 2006-10-06 03:33:44 UTC]

Created attachment 98918 [details, diff]
makes blas compile with gfortran

Well, if anyone cares here is a patch for the sci-libs/blas-19980702-r2 ebuild.. This is really a simple fix..

[Comment 7 Bo Ørsted Andresen (RETIRED) 2006-10-06 03:47:24 UTC]

Created attachment 98922 [details, diff]
makes lapack compile with gfortran

and the same thing for sci-libs/lapack-3.0-r1...

[Comment 8 Sébastien Fabbro (RETIRED) 2007-10-11 08:17:35 UTC]

This was fixed a while back. all mentioned packages have moved on and are now compatible with gfortran.