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

[Markus Mützel]

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

                 Summary: "mkoctfile -p" returns wrong LDFLAGS on Windows
                 Project: GNU Octave
            Submitted by: mmuetzel
            Submitted on: Wed 23 Sep 2020 10:35:33 PM CEST
                Category: Configuration and Build System
                Severity: 3 - Normal
                Priority: 5 - Normal
              Item Group: Build Failure
                  Status: None
             Assigned to: None
         Originator Name: 
        Originator Email: 
             Open/Closed: Open
                 Release: 6.0.90
         Discussion Lock: Any
        Operating System: Microsoft Windows

    _______________________________________________________

Details:

With the release candidate Octave 6.0.90, I see the following:

>> 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


These seem to be the linker flags that would be valid on the platform where
Octave was built.

The LFLAGS emit a deprecation warning but seem to be (more) correct for the
platform where Octave is installed and running:

>> mkoctfile -p LFLAGS
warning: LFLAGS is deprecated and will be removed in a future version of
Octave, use LDFLAGS instead
-LC:\PROGRA~1\GNUOCT~1\OCTAVE~1.90\mingw64\lib\octave\6.0.90
-LC:\PROGRA~1\GNUOCT~1\OCTAVE~1.90\mingw64\lib






    _______________________________________________________

Reply to this item at:

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

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