bugGNU Octave - Bugs: bug #59485, Building standalone executables...

 
 

bug #59485: Building standalone executables only works on 64 bit Windows release not on 32-bit release

Submitter:  None
Submitted:  Thu 19 Nov 2020 03:57:05 PM UTC
   
 
Category:  Libraries Severity:  3 - Normal
Priority:  5 - Normal Item Group:  Unexpected Error or Warning
Status:  None Assigned to:  None
Originator Name:  Peter Kempter Originator Email:  -email is unavailable-
Open/Closed:  * Closed Release:  * dev
Operating System:  * Microsoft Windows Fixed Release:  None
Planned Release:  None
* Mandatory Fields

Add a New Comment Rich Markup
   

Thu 26 Nov 2020 01:11:42 PM UTC, comment #5: 

OK. Closing this report tentatively as fixed.
If it turns out that something still needs to be changed for Octave 6 or later, we can always re-open this report or open a new one.

Markus Mützel <mmuetzel>
Group administrator
Thu 26 Nov 2020 12:43:13 PM UTC, comment #4: 

Using MSYS2 shell works. Setting the Variables according to cmdshell.bat in the CMD doesn't fix the problem.

I gonna use the nightly for now until Octave 6 get's released.

Thanks for your help!


Peter Kempter <ket3r>
Mon 23 Nov 2020 11:35:14 AM UTC, comment #3: 

While it might be interesting to find why that isn't working as expected, development of Octave 5 has stopped at the meantime.
Any possible change would go on Octave 6 or later (where this seems to be fixed already).

Fwiw, can you test if you see the same if you use the MSYS2 shell that you can start with "cmdshell.bat" in the folder where Octave is installed?

That file contains the following line for me (maybe related):

set PATH=%OCTAVE_HOME%qt5\bin;%OCTAVE_HOME%bin;%OCTAVE_HOME%python;%PATH%


Markus Mützel <mmuetzel>
Group administrator
Mon 23 Nov 2020 10:27:15 AM UTC, comment #2: 

Thanks for the quick answer. I can confirm that the bug is fixed in the nightly octave-2020-11-15-00-16-w32.

Using octave-5.2.0_1 I still observe the error. I tried this three variations and I don't understand why only the 3rd works:

    1. Start CMD
    2. add mingw32/bin to path
    3. start executable (in tmp folder) -> fail (error message as in initial bug report)


    1. Start CMD
    2. navigate to mingw32/bin,
    3. start executable which is located in tmp folder-> fail (same error as inital bug report)


    1. Start CMD
    2. navigate to mingw32/bin
    3. copy executable to mingw32/bin, start executable -> success


When I use octave-2020-11-15-00-16-w32 all 3 variations work.

Peter Kempter <ket3r>
Thu 19 Nov 2020 05:51:44 PM UTC, comment #1: 

I tried to reproduce with a nightly from Kai's buildbots (octave-2020-11-15-00-16-w32.7z):
https://buildbot.octave.space/#/download

The 32bit standalone executed as expected (on a 64bit Windows). This might have been fixed in the meantime...

Markus Mützel <mmuetzel>
Group administrator
Thu 19 Nov 2020 03:57:05 PM UTC, original submission:  

Building an executable with the Octave 32-Bit Windows release does not work for me. However, using the 64-Bit Windows release works.

Error Message

When I launch the 32-bit exe I get the following error message:

Der Prozedureinsprungpunkt "glBegin@4" wurde in der DLL "C:\Octave\Octave-5.2.0\mingw32\bin\libgl2ps.dll" nicht gefunden.

Which is German (I don't know why this message is in German) for:

The procedure entrypoint "glBegin@4" was not found in "C:\Octave\Octave-5.2.0\mingw32\bin\libgl2ps.dll".

The 64-bit exe doesn't produce a error message.

How to Reproduce


Compile attached test.cpp (taken from the documentation) with the following command in octave-cli:

mkoctfile --link-stand-alone test.cpp


Launch the produced a.exe with the CMD as follows:
When using the 32-bit installation:

set PATH=C:\Octave\Octave-5.2.0\mingw32\bin;%PATH%
a.exe

When using the 64-bit installation:

set PATH=C:\Octave\Octave-5.2.0\mingw64\bin;%PATH%
a.exe


Expected Behavior


The 64-bit variant works as expected and the program outputs the following to the commandline:

GCD of [10, 15] is 5


I would expected that the built standalone executable of the 32-bit release behaves in the same way as the built standalone executable of the 64-bit release does.

Anonymous

 

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

Attach Files:
   
   
Comment:
   

Attached Files
file #50305:  temp.cpp added by None (2KiB - text/plain)

 

Depends on the following items: None found

Items that depend on this one: None found

 

Carbon-Copy List
  • -email is unavailable- added by ket3r (Posted a comment)
  • -email is unavailable- added by mmuetzel (Posted a comment)
  • -email is unavailable- added by None (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-11-26 mmuetzel Open/ClosedOpen Closed
        Release5.2.0 dev
    2020-11-19 None Attached File- Added temp.cpp, #50305

    Back to the top

    Powered by Savane 3.13-758e.
    Corresponding source code