octave-bug-tracker
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Octave-bug-tracker] [bug #59485] Building standalone executables only w


From: anonymous
Subject: [Octave-bug-tracker] [bug #59485] Building standalone executables only works on 64 bit Windows release not on 32-bit release
Date: Thu, 19 Nov 2020 10:57:07 -0500 (EST)
User-agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/87.0.4280.66 Safari/537.36

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

                 Summary: Building standalone executables only works on 64 bit
Windows release not on 32-bit release
                 Project: GNU Octave
            Submitted by: None
            Submitted on: 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: octave@peter-kempter.de
             Open/Closed: Open
                 Release: 5.2.0
         Discussion Lock: Any
        Operating System: Microsoft Windows

    _______________________________________________________

Details:

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
<https://octave.org/doc/v5.2.0/Standalone-Programs.html>) 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.



    _______________________________________________________

File Attachments:


-------------------------------------------------------
Date: Thu 19 Nov 2020 03:57:05 PM UTC  Name: temp.cpp  Size: 2KiB   By: None

<http://savannah.gnu.org/bugs/download.php?file_id=50305>

    _______________________________________________________

Reply to this item at:

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

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




reply via email to

[Prev in Thread] Current Thread [Next in Thread]