bugGNU Octave - Bugs: bug #54199, Win32 MXE error "The...

 
 

bug #54199: Win32 MXE error "The procedure entry point CancelIoEx could not be located in kernel32.dll"

Submitter:  Rik <rik5>
Submitted:  Thu 28 Jun 2018 04:30:28 AM UTC
   
 
Category:  Configuration and Build System Severity:  3 - Normal
Priority:  5 - Normal Item Group:  Regression
Status:  Wont Fix Assigned to:  None
Originator Name:  Open/Closed:  * Closed
Release:  * dev Operating System:  * Microsoft Windows
Fixed Release:  None Planned Release:  None
* Mandatory Fields

Add a New Comment Rich Markup
   

Jump to the original submission

Fri 29 Jun 2018 04:10:04 PM UTC, comment #10: 

For myself, I backed out the cset which updatded MXE-octave to 5.11.  I then converted the backed out changeset to a patch in the Mercurial Queue system.  Now I can use 'hg qpush' to quickly back out this one change, but still keep up to date with the rest of MXE-octave.  This won't be possble forever, but it works enough for the moment.

 Rik <rik5>
Group administrator
Fri 29 Jun 2018 01:24:46 AM UTC, comment #9: 

I've verified that it was the update of MXE Octave to use Qt 5.11 that caused the problem.  Since this is likely to be an issue for a very small number of users I'll just close this report as "Won't Fix".

 Rik <rik5>
Group administrator
Thu 28 Jun 2018 10:51:03 PM UTC, comment #8: 

Octave seems to run fine in a Win10 64-bit VirtualBox VM, see attached pic. So perhaps this can be used to test windows builds.
Legal: the license for the VMs, above the licenses for the "original" licenses, mentions that it supersedes the latter be it that you may only use them for testing. As that is what we do I suppose we're safe.



Philip Nienhuis <philipnienhuis>
Group Member
Thu 28 Jun 2018 09:19:49 PM UTC, comment #7: 

Well that was quicker than I figured, already the first PC magazine on my "to read" literature pile had the related article.

It seems there are Win7, Win8 and Win10 images.
Look here:
https://developer.microsoft.com/en-us/microsoft-edge/tools/vms/

Virtual box and parallels (for Mac) are supported. Time limit is 90 days, but if you make a snapshot as first action you can circumvent it a little.
No guarantees that octave will run .... but worth a try.

Philip Nienhuis <philipnienhuis>
Group Member
Thu 28 Jun 2018 09:05:14 PM UTC, comment #6: 

@Rik:
Microsoft supplies trial setups of Win10 ready to run right way in Virtual Box. They're merely meant for web developers and are time-bombed for ~6 months (IIRC); I once tried to run Octave in it but IIRC it wasn't a great success, but that may well be due to local stuff on my boxes.
I'll try to dig up the URL. I'll be away for 2 weeks from next Saturday, hopefully I can find it before then.

 Philip Nienhuis <philipnienhuis>
Group Member
Thu 28 Jun 2018 08:32:26 PM UTC, comment #5: 

IMHO, we should not go back to Qt 5.7, it is no longer supported by Qt upstream.

Qt 5.11 is the current deveopment release of Qt, and 5.9 is the current LTS release (long-term support until 2020). We could stay with 5.11 or go back to 5.9. If that means no more XP and Vista support, so be it.

If we stay with 5.11, we should upgrade to 5.12 when it comes out later this year, which will be the next LTS.

 Mike Miller <mtmiller>
Group Member
Thu 28 Jun 2018 08:09:22 PM UTC, comment #4: 

I just verified that I can build by going back 7 days in MXE-Octave to


parent: 4733:1ecb1e67eaa1
 * src/src-msys-dos2unix.mk: update checksum
branch: default


This is before the Qt5.11 upgrade.

Windows XP is really old, and so maybe we drop it.  I don't have any other version of Windows that I can use in a VM.  This just means that I would stop any MXE-Octave development activities (they are occasional anyways).

Rik <rik5>
Group administrator
Thu 28 Jun 2018 07:18:14 PM UTC, comment #3: 

It looks like Qt 5.8 and newer no longer support Windows XP. [1] Neither is Windows Vista [2]

I don't know whether there was a specific reason why Qt was upgraded from version 5.7.1 to version 5.11 here:
http://hg.octave.org/mxe-octave/rev/4cea16af20b4

Windows XP is more than 4 years after EOL and Windows Vista is more than 1 year after EOL.
Do we still want to support those OS?

[1]: https://bugreports.qt.io/browse/QTBUG-58407
[2]: https://wiki.qt.io/PlatformSupport

Markus Mützel <mmuetzel>
Group administrator
Thu 28 Jun 2018 07:12:13 PM UTC, comment #2: 

After doing some searching, it appears that this function is not available in XP.  Also, I think you mean CancelIoEx?

https://docs.microsoft.com/en-us/windows/desktop/FileIO/cancelioex-func

I don't think we use it directly, but it appears to be used in Qt, both in the 5.11 version we are now using in mxe-octave and also the 5.7 version we were using before that.

The switch to 5.11 was done a week ago, so maybe that is what caused the problem?  If so, why wasn't this a problem with 5.7?  Although there seem to have been some changes in the code that uses this function, it was still used in Qt 5.7, so I don't know why it wasn't a problem earlier.

I don't see any obvious recent changes to Octave that would be responsible for us now requiring this function.

John W. Eaton <jwe>
Group administrator
Thu 28 Jun 2018 05:13:54 PM UTC, comment #1: 

I took the Octave code back a week to 6/21/18 and this cset


parent: 25490:9feda91c8592
 maint: Merge stable to default.
branch: default


but it still fails.  I will now try reverting the MXE build environment back a week and see if that works.

Rik <rik5>
Group administrator
Thu 28 Jun 2018 04:30:28 AM UTC, original submission:  

This is a new error I've never seen.  The build system for my windows XP VM was working a few days ago.  I don't know if this is due to a change in the octave source code or the MXE build system.  I've attached a screen capture of the error which happens with GUI or CLI versions.

I'm configuring MXE-octave with


./configure --with-ccache --disable-jit --disable-java --disable-windows-64 --disable-system-opengl --enable-qt5 --enable-octave=default |& tee myconfig.log


Octave source code hg id


changeset:   25513:7fb40efda31f
bookmark:    @
tag:         tip
user:        Markus Mützel <markus.muetzel@gmx.de>
date:        Wed Jun 27 21:01:58 2018 +0200
summary:     Use wide character Windows API for operations on folders (bug #49118).



 Rik <rik5>
Group administrator

 

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

Attach Files:
   
   
Comment:
   

Attached Files
file #44455:  VB_Win10_Oct440.PNG added by philipnienhuis (222KiB - image/png)
file #44450:  w32_fail.png added by rik5 (201KiB - image/png)

 

Depends on the following items: None found

Items that depend on this one: None found

 

Carbon-Copy List
  • -email is unavailable- added by mtmiller (Posted a comment)
  • -email is unavailable- added by rik5
  • -email is unavailable- added by mmuetzel (Posted a comment)
  • -email is unavailable- added by jwe (Posted a comment)
  • -email is unavailable- added by rik5 (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 5 latest changes.

    Date Changed by Updated Field Previous Value => Replaced by
    2018-06-29 rik5 StatusNone Wont Fix
        Open/ClosedOpen Closed
    2018-06-28 philipnienhuis Attached File- Added VB_Win10_Oct440.PNG, #44455
    2018-06-28 rik5 Carbon-Copy- Added lostbard
    2018-06-28 rik5 Attached File- Added w32_fail.png, #44450

    Back to the top

    Copyright © 2024 Free Software Foundation, Inc.
    Verbatim copying and distribution of this entire article is permitted in any medium, provided this notice is preserved.
    The Levitating, Meditating, Flute-playing Gnu logo is a GNU GPL'ed image provided by the Nevrax Design Team.
    Page source code

    Powered by Savane 3.13-72d9.
    Corresponding source code