Re: [gentoo-user] Re: octave won't run

2020-02-06 Thread karl
Ian:
> On 2020-02-06 09:56, Mick wrote:
> 
> > Otherwise the latest sci-libs/lapack is 3.8.0, so your links above look 
> > correct as far as I can tell.
> 
> Note that sci-libs/lapack and sci-libs/lapack-reference are 2 distinct
> packages.  The OP presumably has the latter.
> 
> Both of them existing may be the real bug here.

 The refrence one isn't installed:

# emerge --search sci-libs/lapack-reference
  
[ Results for search key : sci-libs/lapack-reference ]
Searching...

*  sci-libs/blas-reference
  Latest version available: 20070226-r4
  Latest version installed: [ Not Installed ]
  Size of files: 5208 KiB
  Homepage:  http://www.netlib.org/blas/
  Description:   Basic Linear Algebra Subprograms F77 reference 
implementations
  License:   BSD

*  sci-libs/lapack-reference
  Latest version available: 3.2.1-r4
  Latest version installed: [ Not Installed ]
  Size of files: 4694 KiB
  Homepage:  http://www.netlib.org/lapack/index.html
  Description:   FORTRAN reference implementation of LAPACK Linear Algebra 
PACKage
  License:   BSD

Regards,
/Karl Hammar




Re: [gentoo-user] Re: octave won't run

2020-02-06 Thread Philip Webb
200206 Ian Zimmerman wrote:
> On 2020-02-06 09:56, Mick wrote:
>> Otherwise the latest sci-libs/lapack is 3.8.0,
> so your links above look correct as far as I can tell.
> Note that sci-libs/lapack and sci-libs/lapack-reference
> are 2 distinct packages.  The OP presumably has the latter.
> Both of them existing may be the real bug here.

FWIW my own set-up seems to support that.

  872: ~> ls -l /usr/lib64/liblapack.*
  lrwxrwxrwx 1 root root  14 Nov 16 17:11 /usr/lib64/liblapack.so -> 
liblapack.so.3
  lrwxrwxrwx 1 root root  18 Nov 16 17:11 /usr/lib64/liblapack.so.3 -> 
liblapack.so.3.8.0
  -rwxr-xr-x 1 root root 6637008 Nov 16 17:11 /usr/lib64/liblapack.so.3.8.0
  873: ~> 

When I checked earlier today, there were broken symlinks to  lapack-reference ,
but deleting them made no difference : the pkg isn't installed.
Octave opens & calculates '1+1' without any problems.

So the solution to the OP's problem mb simply to unmerge  lapack-reference .

-- 
,,
SUPPORT ___//___,   Philip Webb
ELECTRIC   /] [] [] [] [] []|   Cities Centre, University of Toronto
TRANSIT`-O--O---'   purslowatchassdotutorontodotca




Re: [gentoo-user] Re: octave won't run

2020-02-06 Thread Marc Joliet
Am Donnerstag, 6. Februar 2020, 18:45:12 CET schrieb Ian Zimmerman:
> On 2020-02-06 09:56, Mick wrote:
> > Otherwise the latest sci-libs/lapack is 3.8.0, so your links above look
> > correct as far as I can tell.
>
> Note that sci-libs/lapack and sci-libs/lapack-reference are 2 distinct
> packages.  The OP presumably has the latter.
>
> Both of them existing may be the real bug here.

You motivated me to look this up on my system, and I don't think that's right:

- octave depends on virtual/lapack, and
- virtual/lapack does *not* depend on lapack-reference:

  RDEPEND="
   >=sci-libs/lapack-3.8.0[eselect-ldso?]
   eselect-ldso? ( || (
   >=sci-libs/lapack-3.8.0[eselect-ldso]
   sci-libs/openblas[eselect-ldso] ) )
  "
  DEPEND="${RDEPEND}"

Note also that lapack-reference has no eselect-ldso USE flag, which Karl
changed as per one of his other emails.

Karl, what exactly is the error message you get?  Can you find anything
related on bugs.gentoo.org?  FWIW, my octave installation starts just fine,
but I use openblas:

% eselect lapack list
Available LAPACK (lib) candidates:
  (none found)
Available LAPACK (lib64) candidates:
  [1]   openblas *
  [2]   reference
% eselect blas list
Available BLAS/CBLAS (lib) candidates:
  (none found)
Available BLAS/CBLAS (lib64) candidates:
  [1]   openblas *
  [2]   reference

HTH
--
Marc Joliet
--
"People who think they know everything really annoy those of us who know we
don't" - Bjarne Stroustrup


signature.asc
Description: This is a digitally signed message part.


[gentoo-user] Re: octave won't run

2020-02-06 Thread Ian Zimmerman
On 2020-02-06 09:56, Mick wrote:

> Otherwise the latest sci-libs/lapack is 3.8.0, so your links above look 
> correct as far as I can tell.

Note that sci-libs/lapack and sci-libs/lapack-reference are 2 distinct
packages.  The OP presumably has the latter.

Both of them existing may be the real bug here.

-- 
Ian