[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Octave-bug-tracker] [bug #55447] mkoctfile: wrong LFLAGS warning, reset

From: Orion Poplawski
Subject: [Octave-bug-tracker] [bug #55447] mkoctfile: wrong LFLAGS warning, resets LDFLAGS
Date: Sun, 10 Mar 2019 14:33:44 -0400 (EDT)
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Firefox/60.0

Follow-up Comment #17, bug #55447 (project octave):

I hope I'm not muddying things by posting here instead of creating a new bug,
but while update the Fedora octave package to 5.1 I'm hitting the following
issue.  With octave 4.4:

# mkoctfile -p LFLAGS
-L/usr/lib64/octave/4.4.1 -L/usr/lib64
# mkoctfile -p LDFLAGS
-Wl,-z,relro -Wl,--as-needed  -Wl,-z,now

The libraries are installed in /usr/lib64/octave/4.4.1 which seems to be the
default.  -L/usr/lib64 is superfluous but meh.

With octave 5.1.0:

# mkoctfile -p LFLAGS
warning: LFLAGS is deprecated and will be removed in a future version of
Octave, use LDFLAGS instead
# mkoctfile -p LDFLAGS
-Wl,-z,relro -Wl,--as-needed  -Wl,-z,now

We are not setting LFLAGS anywhere in our build.  The only mention of LFLAGS
in the build logs is:

checking whether yytext is a pointer... no
defining LFLAGS to be -I
checking for bison... bison -y

The missing -L/usr/lib64/octave/5.1.0 from LFLAGS is breaking the building of
swig which uses mkoctfile -p LFLAGS to get the location of the libraries.  And
if LDLAGS is to replace LFLAGS, shouldn't LDFLAGS return the -L options?


Reply to this item at:


  Message sent via Savannah

reply via email to

[Prev in Thread] Current Thread [Next in Thread]