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

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

[Octave-bug-tracker] [bug #57370] (mxe-octave) run issues after binutils


From: John Donoghue
Subject: [Octave-bug-tracker] [bug #57370] (mxe-octave) run issues after binutils update
Date: Fri, 6 Dec 2019 08:19:24 -0500 (EST)
User-agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/64.0.3282.140 Safari/537.36 Edge/18.17763

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

                 Summary: (mxe-octave) run issues after binutils update
                 Project: GNU Octave
            Submitted by: lostbard
            Submitted on: Fri 06 Dec 2019 01:19:22 PM UTC
                Category: None
                Severity: 3 - Normal
                Priority: 5 - Normal
              Item Group: Unexpected Error
                  Status: None
             Assigned to: None
         Originator Name: JohnD
        Originator Email: 
             Open/Closed: Open
         Discussion Lock: Any
                 Release: dev
        Operating System: Microsoft Windows

    _______________________________________________________

Details:


After the update to use binutils 2.33.1

https://hg.octave.org/mxe-octave/rev/36a76b7be686

I did a clean compile of mxe-octave and installed it.

If I go to run the test suite in octave, or open a shell window, or run pkg
install, I get a error message window popup:


msys-2.0.dll is either not designed to run on windows or it contains and
error. Try installing the program again using the original installation media
or contact your system administrator or software vendor for support. Error
status 0xc000007b.


If I install a version compiled from the commit just before the binutils
update, all works ok.

We don't compile msys-2.0.dll, so it hasn't changed between commits, so
something else has changed that invalidates loading of the dll.


Not sure if anyone else using a recent build of mxe sees the same issue on
windows, or if its just me.


The easy fix is go back to the previous version, unless there was a specific
reason that we needed the updated version ?




    _______________________________________________________

Reply to this item at:

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

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




reply via email to

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