| 1 |
On 26/09/12 17:52, Kacper Kowalik wrote: |
| 2 |
> On 09/26/2012 05:09 AM, Andrey G. Grozin wrote: |
| 3 |
>> Hello *, |
| 4 |
>> |
| 5 |
>> I don't understand how the blas stuff (from the science overlay) works. |
| 6 |
>> I have blas-reference and atlas (and also eigen) installed, atlas |
| 7 |
>> eselected. But /usr/lib/libblas.so is a file (not symlink) owned by |
| 8 |
>> blas-reference. So, a program demanding -lblas will be linked to this |
| 9 |
>> library from blas-reference, right? And what eselect blas then is doing? |
| 10 |
>> |
| 11 |
>> This question is related to the new gsl-shell package. Its Makefile just |
| 12 |
>> says -lblas. It works on my computer (linking to /usr/lib/libblas.so |
| 13 |
>> from blas-reference, I suppose). But what should I write as the |
| 14 |
>> dependency? virtual/blas? (docs say that atlas should be OK). |
| 15 |
> Change -lblas into $(pkg-config --libs blas) |
| 16 |
> Cheers, |
| 17 |
> Kacper |
| 18 |
> |
| 19 |
Just to add to Kacper's answer. eselect changes the link to the blas |
| 20 |
pkg-config file. Any ebuild using blas/cblas/lapack should be configured |
| 21 |
using the values from pkg-config. |
| 22 |
If Sebastian had pushed it a little bit more we could have had |
| 23 |
/usr/lib(64)/libblas-reference.so and no libblas whatsoever. Which may |
| 24 |
be an idea just to catch packages that just do -lblas. |
| 25 |
|
| 26 |
Francois |
Archives