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

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

[Octave-bug-tracker] [bug #44998] [MXE] On Windows side, 64-bit OF modul


From: Philip Nienhuis
Subject: [Octave-bug-tracker] [bug #44998] [MXE] On Windows side, 64-bit OF modules can be miscompiled
Date: Sat, 02 May 2015 12:30:24 +0000
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:36.0) Gecko/20100101 Firefox/36.0 SeaMonkey/2.33

URL:
  <http://savannah.gnu.org/bugs/?44998>

                 Summary: [MXE] On Windows side, 64-bit OF modules can be
miscompiled
                 Project: GNU Octave
            Submitted by: philipnienhuis
            Submitted on: Sat 02 May 2015 02:30:20 PM CEST
                Category: Configuration and Build System
                Severity: 3 - Normal
                Priority: 5 - Normal
              Item Group: Crash
                  Status: None
             Assigned to: None
         Originator Name: Philip Nienhuis
        Originator Email: 
             Open/Closed: Open
         Discussion Lock: Any
                 Release: other
        Operating System: Microsoft Windows

    _______________________________________________________

Details:

(Also see short discussion on maintainers ML here:
http://octave.1599824.n4.nabble.com/64-bit-Windows-OF-packages-build-failures-WAS-Cross-compile-io-package-tt4670201.html)

When building Octave-Forge packages for 64-bit Octave on the Windows side, the
resulting .oct files can be "miscompiled" to the extent that they build fine
but make Octave crash when running them.
Examples are csv2cell.cc/cell2csv.cc/csvexplode.cc/csvconcat.cc in the io
package (see bug #44662) and __COM__.cc in the Windows package (see bug
#44180).

It turns out that those 64-bit .oct files cross-built with mxe-octave (using
the --enable-binary-packages and --enable-windows-64 configure options) run
fine, once copied into place manually on the Windows side.

I think it must be a case of miscompilation as those OF modules work fine on
(64-bit) Linux and 32-bit Octave (except, of course, __COM__.oct as that's a
dedicated Windows module).

As JohnD mentions in the thread, Octave is cross-built using a multilib 32/64
bit build system, on Windows the .oct files are built using a 64-bit only
build system.

In a sense this is a regression as .oct files could be built & run fine with
64-bit Octave on 64-bit Windows until some months ago.

As a temporary fix I've attached a changeset for the build_packages.m script
to copy those .oct files over, + the build script itself.

I'll close the bugs #44180 & #44662 with a reference to this report.




    _______________________________________________________

File Attachments:


-------------------------------------------------------
Date: Sat 02 May 2015 02:30:20 PM CEST  Name: build_packages.m  Size: 3kB  
By: philipnienhuis

<http://savannah.gnu.org/bugs/download.php?file_id=33879>
-------------------------------------------------------
Date: Sat 02 May 2015 02:30:20 PM CEST  Name: build_packages_64b.cs  Size: 3kB
  By: philipnienhuis

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

    _______________________________________________________

Reply to this item at:

  <http://savannah.gnu.org/bugs/?44998>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.gnu.org/




reply via email to

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