[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Octave-bug-tracker] [bug #57935] mkoctfile: unrecognized argument /path
From: |
Rik |
Subject: |
[Octave-bug-tracker] [bug #57935] mkoctfile: unrecognized argument /path/to/libopenblas.so |
Date: |
Tue, 9 Jun 2020 18:01:36 -0400 (EDT) |
User-agent: |
Mozilla/5.0 (Windows NT 10.0; WOW64; Trident/7.0; rv:11.0) like Gecko |
Update of bug #57935 (project octave):
Status: Confirmed => Need Info
_______________________________________________________
Follow-up Comment #6:
The BLAS detection macro used by configure comes from GNU. It can be found in
m4/ax_blas.m4. The relevant part is
AC_ARG_WITH(blas,
[AS_HELP_STRING([--with-blas=<lib>], [use BLAS library <lib>])])
case $with_blas in
yes | "") ;;
no) ax_blas_ok=disable ;;
-* | */* | *.a | *.so | *.so.* | *.o) BLAS_LIBS="$with_blas" ;;
*) BLAS_LIBS="-l$with_blas" ;;
esac
If you want to give an explicit file to link with, then the macro expects you
to add the "-l" ahead of it to make it a valid linking option. If, instead,
you simply give a name, like "openblas" then the macro adds the necessary
prefix "-l" for you.
You might try running configure with
./configure
--with-blas=-l/usr/local/gcc-9.2.0_binutils-2.32_isl/lib64/libopenblas.so
and see if that generates an installation where mkoctfile works. I'm guessing
from the error message that mkoctfile just puts the value of $BLAS_LIBS in the
compile command and that is why you are seeing
unrecognized argument
/usr/local/gcc-9.2.0_binutils-2.32_isl/lib64/libopenblas.so
_______________________________________________________
Reply to this item at:
<https://savannah.gnu.org/bugs/?57935>
_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/
- [Octave-bug-tracker] [bug #57935] mkoctfile: unrecognized argument /path/to/libopenblas.so,
Rik <=