[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Octave-bug-tracker] [bug #59475] Exceptions Running Octave with 64-
From: |
David Laxer |
Subject: |
Re: [Octave-bug-tracker] [bug #59475] Exceptions Running Octave with 64-bit Indexes |
Date: |
Tue, 17 Nov 2020 16:19:57 -0000 |
I did read the doc you alluded to and followed the instructions.
I download, built and installed OpenBlas, LAPACK, etc. and built them for 64
bit.
E.g.
make BINARY=64
Clearly, I did something wrong!
> On Nov 17, 2020, at 7:57 AM, John W. Eaton <INVALID.NOREPLY@gnu.org> wrote:
>
> Follow-up Comment #1, bug #59475 (project octave):
>
> Was your BLAS library actually compiled to use 64-bit indexing? What about
> other libraries that also use the BLAS? They all need to be consistently
> using 64-bit integers for indexing.
>
> Have you read
>
> https://octave.org/doc/v5.2.0/Compiling-Octave-with-64_002dbit-Indexing.html#Compiling-Octave-with-64_002dbit-Indexing
>
> ?
>
> We build Octave for Windows systems with 64-bit BLAS and related libraries, so
> I'm confident that it is possible to build Octave this way. But most Linux
> distributions don't package BLAS and related libraries compiled to use 64-bit
> integers for indexing. So if you want to do that, you probably have to
> correctly configure and build those libraries as well.
>
> I
>
> _______________________________________________________
>
> Reply to this item at:
>
> <https://savannah.gnu.org/bugs/?59475>
>
> _______________________________________________
> Message sent via Savannah
> https://savannah.gnu.org/
>
smime.p7s
Description: S/MIME cryptographic signature
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- Re: [Octave-bug-tracker] [bug #59475] Exceptions Running Octave with 64-bit Indexes,
David Laxer <=