1 |
200206 Ian Zimmerman wrote: |
2 |
> On 2020-02-06 09:56, Mick wrote: |
3 |
>> Otherwise the latest sci-libs/lapack is 3.8.0, |
4 |
> so your links above look correct as far as I can tell. |
5 |
> Note that sci-libs/lapack and sci-libs/lapack-reference |
6 |
> are 2 distinct packages. The OP presumably has the latter. |
7 |
> Both of them existing may be the real bug here. |
8 |
|
9 |
FWIW my own set-up seems to support that. |
10 |
|
11 |
872: ~> ls -l /usr/lib64/liblapack.* |
12 |
lrwxrwxrwx 1 root root 14 Nov 16 17:11 /usr/lib64/liblapack.so -> liblapack.so.3 |
13 |
lrwxrwxrwx 1 root root 18 Nov 16 17:11 /usr/lib64/liblapack.so.3 -> liblapack.so.3.8.0 |
14 |
-rwxr-xr-x 1 root root 6637008 Nov 16 17:11 /usr/lib64/liblapack.so.3.8.0 |
15 |
873: ~> |
16 |
|
17 |
When I checked earlier today, there were broken symlinks to lapack-reference , |
18 |
but deleting them made no difference : the pkg isn't installed. |
19 |
Octave opens & calculates '1+1' without any problems. |
20 |
|
21 |
So the solution to the OP's problem mb simply to unmerge lapack-reference . |
22 |
|
23 |
-- |
24 |
========================,,============================================ |
25 |
SUPPORT ___________//___, Philip Webb |
26 |
ELECTRIC /] [] [] [] [] []| Cities Centre, University of Toronto |
27 |
TRANSIT `-O----------O---' purslowatchassdotutorontodotca |