[Octave-bug-tracker] [bug #59173] "mkoctfile -p" returns wrong LDFLAGS on Windows

[Markus Mützel]

Follow-up Comment #20, bug #59173 (project octave):

At the moment, LDFLAGS is the following for Windows cross-builds (see comment
#0):

>> mkoctfile -p LDFLAGS
-Wl,-rpath-link,/scratch/build/release/mxe-octave-w64/usr/x86_64-w64-mingw32/lib
-L/scratch/build/release/mxe-octave-w64/usr/x86_64-w64-mingw32/lib
-L/scratch/build/release/mxe-octave-w64/usr/x86_64-w64-mingw32/qt5/lib
-Wl,--export-all-symbols


If we make it such that LDFLAGS is what LFLAGS previously was (see comment
#11), it will be (comment #0):

>> mkoctfile -p LDFLAGS
-LC:\PROGRA~1\GNUOCT~1\OCTAVE~1.90\mingw64\lib\octave\6.0.90
-LC:\PROGRA~1\GNUOCT~1\OCTAVE~1.90\mingw64\lib


If packages got `-Wl,--export-all-symbols` from LDFLAGS (which I don't know if
it is the case), that flag might get lost by that change.

    _______________________________________________________

Reply to this item at:

  <https://savannah.gnu.org/bugs/?59173>

_______________________________________________
  Message sent via Savannah
  https://savannah.gnu.org/