1 |
Quoting Andrea Arteaga <andyspiros@×××××.com>: |
2 |
|
3 |
> Hi Francois. |
4 |
> So, the package lapack-reference is emerged, but the test suite fails, right? |
5 |
> Could you just write a very basic C or Fortran program using a routine |
6 |
> of the LAPACK and compile it with the instruction of pkg-config |
7 |
> lapack, after having emerged lapack-reference and skipped the tests? |
8 |
> |
9 |
Probably would work. I had a close look at one of the test programs: |
10 |
|
11 |
frb15@BlueFerniMac1 |
12 |
~/Desktop/Gentoo/var/tmp/portage/sci-libs/lapack-reference-3.3.1-r1/work/lapack-reference-3.3.1_build/bin |
13 |
$ ./xeigtstc |
14 |
dyld: Library not loaded: /Users/frb15/Desktop/Gentoo/usr/lib/libtmglib.dylib |
15 |
Referenced from: |
16 |
/Users/frb15/Desktop/Gentoo/var/tmp/portage/sci-libs/lapack-reference-3.3.1-r1/work/lapack-reference-3.3.1_build/bin/./xeigtstc |
17 |
Reason: image not found |
18 |
Trace/BPT trap |
19 |
frb15@BlueFerniMac1 |
20 |
~/Desktop/Gentoo/var/tmp/portage/sci-libs/lapack-reference-3.3.1-r1/work/lapack-reference-3.3.1_build/bin |
21 |
$ ls ../lib/ |
22 |
libreflapack.dylib libtmglib.dylib |
23 |
|
24 |
In short it is linked as if it was installed. So it doesn't find one of its |
25 |
essential library. I am not quite sure how to fix this - in a general fashion. |
26 |
I think I may be able to do something on OS X. It may actually be easier on a |
27 |
linux prefix by using LD_LIBRARY_PATH. But the real solution would be for the |
28 |
test run to have different linking options. |
29 |
|
30 |
Francois |