Hello,

Is lapack ready for gcc-4.1.1? On my system profile 2006.1, these are
the options for lapack install

->emerge --search lapack

*  sci-libs/lapack-atlas
      Latest version available: 3.7.11
      Latest version installed: [ Not Installed ]
      Size of files: 6,924 kB
      Homepage:      http://math-atlas.sourceforge.net/
      Description:   Full LAPACK implementation using available ATLAS
routines
      License:       BSD

*  sci-libs/lapack-config
      Latest version available: 1.0.1
      Latest version installed: [ Not Installed ]
      Size of files: 0 kB
      Homepage:      http://www.gentoo.org/
      Description:   Utility to change the default LAPACK library
      License:       GPL-2

*  sci-libs/lapack-reference
      Latest version available: 3.0-r1
      Latest version installed: [ Not Installed ]
      Size of files: 4,934 kB
      Homepage:      http://www.netlib.org/lapack/index.html
      Description:   FORTRAN reference implementation of LAPACK Linear
Algebra PACKage
      License:       lapack

I've checked the homepage of lapack-atlas and it says

At present, it provides C and Fortran77 interfaces to a portably
efficient BLAS implementation, as well as a few routines from LAPACK.

This does not seem as a *full* lapack implementation as called for in
the Description field above.

Therefore I am leaning towards the installation of the lapack-reference
package instead. This what an emerge for lapack-reference would do

->emerge --pretend --verbose lapack-reference

These are the packages that would be merged, in order:

Calculating dependencies... done!
[ebuild  N    ] sci-libs/lapack-config-1.0.1  0 kB 
[ebuild  N    ] sci-libs/blas-atlas-3.7.11  USE="doc -debug" 1,991 kB 
[ebuild  N    ] sci-libs/lapack-reference-3.0-r1  USE="-debug -ifc"
4,935 kB

I suppose since the -ifc flag is the default, the intel compiler will
not be called and that the gcc gfortran (G95) compiler will. Is this a
correct assumption? Also what is the lapack-config package doing exactly
since the blas-config package is not pulled in.

Thanks,

--
Valmor

--
[email protected] mailing list

Reply via email to