bugGNU Octave - Bugs: bug #57414, mkoctfile does not build...

 
 

bug #57414: mkoctfile does not build executable under Win7

Submitter:  Arne Geppert <helios>
Submitted:  Sun 15 Dec 2019 12:28:46 PM UTC
   
 
Category:  Octave Function Severity:  3 - Normal
Priority:  5 - Normal Item Group:  Build Failure
Status:  Works For Me Assigned to:  None
Originator Name:  Open/Closed:  * Closed
Release:  * 5.1.0 Operating System:  * Microsoft Windows
Fixed Release:  None Planned Release:  None
* Mandatory Fields

Add a New Comment Rich Markup
   

Jump to the original submission

Wed 26 Feb 2020 06:22:02 AM UTC, comment #10: 

Hi Mike,
thanks fo your support. It seems that nobody else went into the same problem. So for me it is fine when it is closed as "unreproducible configuration".
Upgrading to a new Win10 or installing Win7 from scratch should fix the problem.
Thanks a lot for the wonderfull free and open souce Octave Software!
Kind regards
Arne

Arne Geppert <helios>
Tue 25 Feb 2020 04:59:07 PM UTC, comment #9: 


> Please let me know, if I should check any parameter/OS settings to find the root cause.


If it's still a problem for you, and you know what you want to check, and it's worth the time and effort for you to keep investigating, by all means go ahead.

Remember, bug reports are an opportunity for you to help us improve Octave if possible. But if you've moved on and the affected partition doesn't matter to you anymore, then we should close this as an unreproducible configuration.

Mike Miller <mtmiller>
Group Member
Mon 24 Feb 2020 04:48:51 PM UTC, comment #8: 

Hello Mike,
I checked with Octave 5.2.0 and Win7. The problem still exists on my Win7 partition
Some weeks ago I upgraded on a different partition but the same machine to Win10. No troubles there! Octave 5.1.0 and 5.2.0 work fine compiling and executing the "mkoctfile" examples (Octave (5.1.0) documentation (A.3 Standalone Programs)).

So for me it seems, the troubles are system specific on my single Win7 partition. Please let me know, if I should check any parameter/OS settings to find the root cause. Up to now my special Win7 partition still exists and it is running very well
only this Octave issue has forced me to upgrade to Win10 to work on my diploma thesis:-)

Thanks and regards
Arne



Arne Geppert <helios>
Fri 21 Feb 2020 10:52:35 PM UTC, comment #7: 

Is there a bug described here or is it a problem with only one specific system? Is it still reproducible on the same system with Octave 5.2.0?

I can't even tell from the discussion what the actual problem being described is. I see in the first comment that the compiler is called but does not result in an executable file. Then in more recent comments a different error has something to do with the quoting of command strings.

Mike Miller <mtmiller>
Group Member
Sun 15 Dec 2019 06:57:07 PM UTC, comment #6: 

Hi Markus,
I stopped all relevant (antivirus) processes.
Unfortunately the problem still exists:-(
Anything more I can check?
Thanks and regards
Arne

Arne Geppert <helios>
Sun 15 Dec 2019 05:27:43 PM UTC, comment #5: 

Octave uses _wpopen to spawn the child process. That is part of the C runtime library.
I'm not sure why that fails.
Does deactivating your antivirus program make a difference?

Markus Mützel <mmuetzel>
Group administrator
Sun 15 Dec 2019 03:54:45 PM UTC, comment #4: 

Hi Markus,

"mkoctfile -p CXXFLAGS" fom Win7 command line shows up "-g -O2"

Whithin a Octave session I got the followong error:
octave:1> mkoctfile -p CXXFLAGS
error: system: unable to start subprocess for '""C:\Octave\OCTAVE~1.0\mingw64\bin\mkoctfile-5.1.0.exe" "-p" "CXXFLAGS""'
error: called from
    mkoctfile at line 216 column 14

Its the same with the call of
"mkoctfile -v --link-stand-alone standalone.cc -o standalone"
within a Octave session. Then I got:

octave:1> mkoctfile -v --link-stand-alone standalone.cc -o standalone
error: system: unable to start subprocess for '""C:\Octave\OCTAVE~1.0\mingw64\bin\mkoctfile-5.1.0.exe" "-v" "--link-stand-alone" "standalone.cc" "-o" "standalone""'
error: called from
    mkoctfile at line 216 column 14

Both errors do not show up on my Win10 machine.
I tried also with Octave 4.4.1 on Win7. Same errors.
It seems that something is broken on my Win7 machine, but I cant find what is causing the error (my Win7 machine is the one I use for "production" purpose. All other machines are for testing only:-(  )
Thanks again for your help and reply.
Kind regards
Arne

Arne Geppert <helios>
Sun 15 Dec 2019 03:10:05 PM UTC, comment #3: 

Sorry, I misread your comment #0. I was thinking, you are using mkoctfile from inside Octave.
I am assuming that you are using a shell started with "cmdshell.bat" (from inside the Octave installation folder).

What do you see for the following?

CXXFLAGS="$(mkoctfile -p CXXFLAGS) -v" mkoctfile -v --link-stand-alone standalone.cc -o standalone


Markus Mützel <mmuetzel>
Group administrator
Sun 15 Dec 2019 01:39:35 PM UTC, comment #2: 

Hi Markus,
thank you for the fast response.
Unfortunately creating the temporary directory and setting the environment as proposed inside Octave and on the command line did not change the behavior.
Any more ideas?
Thanks and regard
Arne

Arne Geppert <helios>
Sun 15 Dec 2019 12:41:03 PM UTC, comment #1: 

IIRC, there have been reports that files in the default temporary directory couldn't be executable.
Does setting the temporary directory to some other directory help?

mkdir ('C:\Octave\Temp');
setenv ("TMPDIR", 'C:\Octave\Temp');


Markus Mützel <mmuetzel>
Group administrator
Sun 15 Dec 2019 12:28:46 PM UTC, original submission:  

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


Arne Geppert <helios>

 

(Note: upload size limit is set to 16384 kB, after insertion of the required escape characters.)

Attach Files:
   
   
Comment:
   

No files currently attached

 

Depends on the following items: None found

Items that depend on this one: None found

 

Carbon-Copy List
  • -email is unavailable- added by mmuetzel (Posted a comment)
  • -email is unavailable- added by helios (Submitted the item)
  •  

    There are 0 votes so far. Votes easily highlight which items people would like to see resolved in priority, independently of the priority of the item set by tracker managers.

    Only group members can vote.

     

    Follow 3 latest changes.

    Date Changed by Updated Field Previous Value => Replaced by
    2020-02-26 mtmiller Open/ClosedOpen Closed
    2020-02-21 mtmiller StatusNeed Info Works For Me
    2019-12-15 mmuetzel StatusNone Need Info

    Back to the top

    Powered by Savane 3.13-4448.
    Corresponding source code