| 1 |
Dear Valmor, |
| 2 |
|
| 3 |
* de Almeida, Valmor F. [2007-03-19 21:17]: |
| 4 |
> Is lapack ready for gcc-4.1.1? On my system profile 2006.1, these are |
| 5 |
> the options for lapack install |
| 6 |
|
| 7 |
Yes, it is ready and working well. I personally use testing ~x86 versions, |
| 8 |
so I can not say much about the stable ones, which are usually a bit |
| 9 |
outdated. ;-) |
| 10 |
|
| 11 |
[...] |
| 12 |
|
| 13 |
> I've checked the homepage of lapack-atlas and it says |
| 14 |
> |
| 15 |
> At present, it provides C and Fortran77 interfaces to a portably |
| 16 |
> efficient BLAS implementation, as well as a few routines from LAPACK. |
| 17 |
> |
| 18 |
> This does not seem as a *full* lapack implementation as called for in |
| 19 |
> the Description field above. |
| 20 |
> |
| 21 |
> Therefore I am leaning towards the installation of the lapack-reference |
| 22 |
> package instead. This what an emerge for lapack-reference would do |
| 23 |
|
| 24 |
In Gentoo, lapack-atlas is a joint package of a few optimised LAPACK |
| 25 |
routines from ATLAS and the rest from NetLib's reference LAPACK. So, it |
| 26 |
includes everything LAPACK has. If you care for performance, you should |
| 27 |
give lapack-atlas a try. |
| 28 |
|
| 29 |
> ->emerge --pretend --verbose lapack-reference |
| 30 |
> |
| 31 |
> These are the packages that would be merged, in order: |
| 32 |
> |
| 33 |
> Calculating dependencies... done! |
| 34 |
> [ebuild N ] sci-libs/lapack-config-1.0.1 0 kB |
| 35 |
> [ebuild N ] sci-libs/blas-atlas-3.7.11 USE="doc -debug" 1,991 kB |
| 36 |
> [ebuild N ] sci-libs/lapack-reference-3.0-r1 USE="-debug -ifc" |
| 37 |
> 4,935 kB |
| 38 |
|
| 39 |
If you do not want to use lapack-atlas, you might consider installing |
| 40 |
blas-reference (and optionally cblas-reference) instead of blas-atlas. |
| 41 |
|
| 42 |
> I suppose since the -ifc flag is the default, the intel compiler will |
| 43 |
> not be called and that the gcc gfortran (G95) compiler will. Is this a |
| 44 |
> correct assumption? |
| 45 |
|
| 46 |
Correct. |
| 47 |
|
| 48 |
> Also what is the lapack-config package doing exactly |
| 49 |
> since the blas-config package is not pulled in. |
| 50 |
|
| 51 |
lapack-config and blas-config are used for setting /usr/lib/lib* links to |
| 52 |
a particular blas/lapack library (reference, atlas, mkl, etc.). These are |
| 53 |
outdated tools and eselect {blas,lapack,cblas} are their replacement in |
| 54 |
testing ~ARCH. |
| 55 |
|
| 56 |
Besides, blas-config is a runtime dependency for blas-atlas-3.7.11: |
| 57 |
RDEPEND="sci-libs/blas-config", |
| 58 |
so you should have it already installed on your system. |
| 59 |
|
| 60 |
BR, |
| 61 |
/Adam |
| 62 |
|
| 63 |
|
| 64 |
-- |
| 65 |
-=#=- Adam Piatyszek - "ediap" -=#=- JID: ediap (at) jabber.org -=#=- |
| 66 |
-=#=- ediap (at) users.sf.net -=#=- PGP key ID: 0x83EFCBAA -=#=- |
Archives