| 1 |
-----BEGIN PGP SIGNED MESSAGE----- |
| 2 |
Hash: SHA1 |
| 3 |
|
| 4 |
On Mon, 19 Mar 2007, de Almeida, Valmor F. wrote: |
| 5 |
>> -----Original Message----- |
| 6 |
>> From: Markus Dittrich [mailto:markusle@g.o] |
| 7 |
>> Sent: Monday, March 19, 2007 5:00 PM |
| 8 |
>> To: gentoo-science@l.g.o |
| 9 |
>> Subject: Re: [gentoo-science] status of lapack install |
| 10 |
> |
| 11 |
> [lines deleted] |
| 12 |
> |
| 13 |
>> |
| 14 |
>> The currently stable lapack-atlas and blas-atlas (3.7.11) compile |
| 15 |
>> fine with gcc-4.x. |
| 16 |
>> Should you go with lapack-reference you will need the most |
| 17 |
>> recent lapack-reference-3.1.1 not lapack-reference-3.0-r1. |
| 18 |
>> The reference ebuilds (both lapack and blas) take less time |
| 19 |
>> to compile but provide less optimized routines. Hence, you have |
| 20 |
>> to decide what is more important to you. |
| 21 |
>> |
| 22 |
>> cheers, |
| 23 |
>> Markus |
| 24 |
> |
| 25 |
> Hi I went for lapack-atlas and the required blas-atlas did not compile. |
| 26 |
> It suggested an interactive approach so I did |
| 27 |
> |
| 28 |
> interactive=1 emerge blas-atlas |
| 29 |
> |
| 30 |
> and answered the questions. Finally it died here. Looks like sed is |
| 31 |
> looking for an input file. |
| 32 |
> |
| 33 |
|
| 34 |
You probably have a newer CPU type on which blas-atlas' |
| 35 |
configure routine is chocking. I'd try the most recent versions |
| 36 |
in ~ARCH, i.e., blas/lapack-atlas-3.7.24. |
| 37 |
|
| 38 |
Good luck, |
| 39 |
Markus |
| 40 |
|
| 41 |
|
| 42 |
- -- |
| 43 |
Markus Dittrich (markusle) |
| 44 |
Gentoo Linux Developer |
| 45 |
Scientific applications |
| 46 |
-----BEGIN PGP SIGNATURE----- |
| 47 |
Version: GnuPG v1.4.6 (GNU/Linux) |
| 48 |
|
| 49 |
iD8DBQFF/wuxxlRwCwb7k40RAmeeAJ93eO7peTJ6WQT4bLPww8Vyglh/bwCePwNc |
| 50 |
DlryZNKaVylExudd+b641os= |
| 51 |
=XYM7 |
| 52 |
-----END PGP SIGNATURE----- |
| 53 |
-- |
| 54 |
gentoo-science@g.o mailing list |
Archives