[Octave-bug-tracker] [bug #57414] mkoctfile does not build executable under Win7

[Arne Geppert]

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

                 Summary: mkoctfile does not build executable under Win7
                 Project: GNU Octave
            Submitted by: helios
            Submitted on: Sun 15 Dec 2019 12:28:46 PM UTC
                Category: Octave Function
                Severity: 3 - Normal
                Priority: 5 - Normal
              Item Group: Build Failure
                  Status: None
             Assigned to: None
         Originator Name: 
        Originator Email: 
             Open/Closed: Open
         Discussion Lock: Any
                 Release: 5.1.0
        Operating System: Microsoft Windows

    _______________________________________________________

Details:

Hi there,

I ran into troubles using "mkoctfile" under Win7 and Octave 5.1.0 with the
examples (e.g. standalone.cc) given in the Octave (5.1.0) documentation (A.3
Standalone Programs). 
Calling 
mkoctfile --link-stand-alone standalone.cc -o standalone
from Win7 command line using the -v (verbose) flag I can see a randomized
temporary file (here "oct-gZfZgH.o") ist generated. But no Win7 executable:

g++ -c -I/release/mxe-octave-w64/usr/x86_64-w64-mingw32/include 
-IC:\Octave\Oct
ave-5.1.0.0\mingw64\include\octave-5.1.0\octave\..
-IC:\Octave\Octave-5.1.0.0\mi
ngw64\include\octave-5.1.0\octave -IC:\Octave\Octave-5.1.0.0\mingw64\include  
-
fopenmp -g -O2    standalone.cc -o
C:\Users\Arne\AppData\Local\Temp/oct-gZfZgH.o

Using Win10 or Debian 19 (Buster) works fine. But I cant get it run under Win7
and I dont understand what the problem is.

Using 2 separate compiler calls and renaming the randomized temporary file to
"oct-tmp.o" will generate the disiered Win7 executable but this is very
time-consuming and not the way it should be done:
g++ -c -I/release/mxe-octave-w64/usr/x86_64-w64-mingw32/include
-IC:\Octave\Octave-5.1.0.0\mingw64\include\octave-5.1.0\octave\..
-IC:\Octave\Octave-5.1.0.0\mingw64\include\octave-5.1.0\octave
-IC:\Octave\Octave-5.1.0.0\mingw64\include   -fopenmp -g -O2    standalone.cc
-o C:\Users\arne\AppData\Local\Temp/oct-tmp.o
g++    -I/release/mxe-octave-w64/usr/x86_64-w64-mingw32/include
-IC:\Octave\Octave-5.1.0.0\mingw64\include\octave-5.1.0\octave\..
-IC:\Octave\Octave-5.1.0.0\mingw64\include\octave-5.1.0\octave
-IC:\Octave\Octave-5.1.0.0\mingw64\include   -fopenmp -g -O2   
-Wl,-rpath-link,/release/mxe-octave-w64/usr/x86_64-w64-mingw32/lib
-L/release/mxe-octave-w64/usr/x86_64-w64-mingw32/lib
-L/release/mxe-octave-w64/usr/x86_64-w64-mingw32/qt5/lib
-Wl,--export-all-symbols  -o standalone 
C:\Users\Arne\AppData\Local\Temp/oct-tmp.o 
-LC:\Octave\Octave-5.1.0.0\mingw64\lib\octave\5.1.0
-LC:\Octave\Octave-5.1.0.0\mingw64\lib
-LC:\Octave\Octave-5.1.0.0\mingw64\lib\octave\5.1.0 -loctinterp -loctave 

Does anyone knows the reason for this behavior and knows how to fix it under
Win7?
Any hint is more than wellcome.
Thanks in advance and regards
Arne 






    _______________________________________________________

Reply to this item at:

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

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