bugGNU Octave - Bugs: bug #47576, mxe-octave:...

 
 

bug #47576: mxe-octave: octave-4.0.1-installer.exe (32bit) does not install on Windows 10

Submitted by:  Charles O'Riley <nagashi>
Submitted on:  Wed 30 Mar 2016 08:05:23 PM UTC  
 
Category:  Configuration and Build System Severity:  3 - Normal
Priority:  5 - Normal Item Group:  Installation Failure
Status:  Fixed Assigned to:  None
Originator Name:  CHARLES O'RILEY Open/Closed:  Closed
Release:  4.0.1 Operating System:  Microsoft Windows

Add a New Comment (Rich Markup)
   

You are not logged in

Please log in, so followups can be emailed to you.

 

( Jump to the original submission)

Sat 02 Jul 2016 12:14:41 AM UTC, comment #27: 

The current windows installer produced by mxe-octave can detects windows 10 and this post can be closed, I think.

Tatsuro MATSUOKA <tmacchant>
Fri 01 Jul 2016 07:43:23 PM UTC, comment #26: 

Yes - it installs ok of Win10 now

John Donoghue <lostbard>
Project Member
Fri 01 Jul 2016 05:18:46 PM UTC, comment #25: 

@John D.: Is this okay to close now?  Is the dev installer working okay on Windows 10?

Rik <rik5>
Project Administrator
Tue 26 Apr 2016 05:11:14 PM UTC, comment #24: 

Also, for the uninstaller, it looks like all applications I see now appear to no longer show their uninstaller in the start menu.

An uninstall option is available by right clicking on a executable file shortcut, but just brings up the add/remove programs window.

John Donoghue <lostbard>
Project Member
Thu 21 Apr 2016 08:30:35 PM UTC, comment #23: 

WIndows 10 now installed, so hopefully I can take a look at this.

First thing noticed after install, is that on selecting a shortcut, it will prompt for how to run it, giving in option of notepad, windows host etc

Changing the icon to run wscript instead of the .vbs script fixes that, so I will change it

John Donoghue <lostbard>
Project Member
Fri 08 Apr 2016 09:38:52 PM UTC, comment #22: 

@JohnD:
As octave-4.0.1 32bit now installs fine on Win 10, I think this bug report is close to, well, closing (pun intended).

The uninstall link in Win10's start menu (or whatever it looks to be these days) doesn't seem like a showstopper to me.

[OT]
BTW I made a multiboot Win7/Win10 (+ Linux) on my laptop by simply upgrading to Win10 (a 20 minutes job), downgrading to Win 7 immediately (everything still worked, pfew) and later on creating a USB thumb drive installer according to instructions found on the web (Microsoft themselves made those instructions).
I then installed Win10 in a separate partition. In hindsight I should have hidden Win7 while installing Win10 as the latter screws up boot menu's etc. Took me some trouble to disentangle the two; but now lilo boots Win7/Win10/Linux.

I use that otherwise bare Win10 only for testing Octave ....

Philip Nienhuis <philipnienhuis>
Project Member
Sat 02 Apr 2016 06:25:17 PM UTC, comment #21: 

I havent gotten around to using win10 yet.

I did do a quick look for info on nsis shortcuts in win10, but so far, havent seen any issues apart from the ApplicationId setting for Win8 & 10.

John Donoghue <lostbard>
Project Member
Sat 02 Apr 2016 04:48:48 PM UTC, comment #20: 

@JohnD comment #19:
Nothing should have changed within the installer for the shortcut.
That's why I think it is a Windows 10 peculiarity.

Note that Win10's Start Menu is, well, special.

Philip Nienhuis <philipnienhuis>
Project Member
Sat 02 Apr 2016 12:48:20 PM UTC, comment #19: 

I will take a look around on why the uninstaller doesnt get added to the start menu.

Nothing should have changed within the installer for the shortcut.

John Donoghue <lostbard>
Project Member
Fri 01 Apr 2016 09:02:20 PM UTC, comment #18: 

Thanks.

Charles O'Riley <nagashi>
Fri 01 Apr 2016 08:59:53 PM UTC, comment #17: 

The installer on ftp.gnu.org hasn't been updated.  It probably will be updated, but I can't promise when that will happen.

John W. Eaton <jwe>
Project Administrator
Fri 01 Apr 2016 08:41:18 PM UTC, comment #16: 

Based on your last email, I went to ftp.gnu.org and downloaded the installer for windows.  At the beginning of the installation process, I have attached the error received below in a PDF file.  Let me know if I'm pulling the installation file from the wrong place.  Thanks.

(file #36824)

Charles O'Riley <nagashi>
Fri 01 Apr 2016 08:32:50 PM UTC, comment #15: 

More good news:
With that new build gzip/zip work fine.

When running _run_test_suite_.m, the number of FAILs changes erratically from run to run. I had a run with 0, 1 (ichol) and 2 (inputname) FAILs.

Philip Nienhuis <philipnienhuis>
Project Member
Fri 01 Apr 2016 08:12:17 PM UTC, comment #14: 

BTW the installer doesn't add the uninstaller shortcut to the Start Menu. All the others are there.
But this might a Win10 "feature" I'm afraid.

The installer correctly finds Win10 with a suitable message. Neat!

What to do with this bug report now? Put a new installer on ftp.gnu.org?

Philip Nienhuis <philipnienhuis>
Project Member
Fri 01 Apr 2016 07:24:20 PM UTC, comment #13: 

(@JohnD: 2nd patch came too late for test build that I could continue & finish this morning. I'll try later)

OK, good news:
octave-4.0.1 32 bit now installs fine and runs mostly fine on Windows 10.
_run_test_suite_.m:
Summary:

  PASS     13014
  FAIL         4
  XFAIL       30
  SKIPPED     54

although a second run had only 2 FAILs.
The FAILs are with a.o., movefile, copyfile and unpack and seem serious:

*** Couldn't reserve space for cygwin's heap, Win32 error 0

Invoking zip and gzip leads to a crash (of those programs, not Octave). A.o., OF io's OCT interface is affected here.

relevant parts of fntests.log attached.

(file #36823)

Philip Nienhuis <philipnienhuis>
Project Member
Fri 01 Apr 2016 02:46:15 PM UTC, comment #12: 

I have also pushed a change to the installer to check for win10 and warn - let me know if it works ok.

John Donoghue <lostbard>
Project Member
Thu 31 Mar 2016 09:47:51 PM UTC, comment #11: 

octave.sf.net seems down; next chance tomorrow.

Philip Nienhuis <philipnienhuis>
Project Member
Thu 31 Mar 2016 06:15:52 PM UTC, comment #10: 

I'll try your patch later. I have no 32-bit mxe-octave build tree so must start from scratch

Philip Nienhuis <philipnienhuis>
Project Member
Thu 31 Mar 2016 06:14:50 PM UTC, comment #9: 

6.3

As suggested, just a "warning" or informative message that Octave hasn't received much testing so users are encouraged to try it out?

Philip Nienhuis <philipnienhuis>
Project Member
Thu 31 Mar 2016 04:56:13 PM UTC, comment #8: 

Also can someone check for WIn8 and Win10, what the registry value is for the following:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\CurrentVersion

On my WIi7 machine it is 6.1
The nsis installer check for WIn8 is 6.2, with anything else starting with 6, not previously detected also being dubbed Win8.

Even though it checks win8, it doesn't do anything with shortcuts anymore, as the line edit was resolved in https://savannah.gnu.org/bugs/?37623

So perhaps change it to just warn now if Win10 ?

John Donoghue <lostbard>
Project Member
Thu 31 Mar 2016 04:40:45 PM UTC, comment #7: 

The nsis installer gets built as a 32bit app in both w32 and 264, the main difference being that in 64 bit, it is compiled with a multimode gcc that supports both 32 and 64 bit compiling.

I pushed an update to nsis to a current version - it compiles and runs ok for me in 32 and 64 bit mode, but I don't have Win10, so if someone else can try it to see if it fixes the issue?

John Donoghue <lostbard>
Project Member
Thu 31 Mar 2016 04:25:20 PM UTC, comment #6: 
John Donoghue <lostbard>
Project Member
Thu 31 Mar 2016 03:26:48 PM UTC, comment #5: 

Marked bug #47574 as a duplicate of this, although this one is "younger". This report has had a bit more investigation

Philip Nienhuis <philipnienhuis>
Project Member
Thu 31 Mar 2016 11:58:18 AM UTC, comment #4: 

Wasn't the win8 detection meant for the --without-line-editing (or so) command line parameter?

AFAICS Octave runs fine on Windows 10 and in the brief period I had Windows 8 at work (now back at 7) it ran fine there as well. But note that I only run "home-made" 64-bit builds (--enable-windows-64).

If we have enough confidence the warning may not be required anymore, at least not for Win 8. As to Win10 I feel we need more testing.
One thing I haven't had time for is to test all of the installed OF packages. Didn't you make a script to do that?

Philip Nienhuis <philipnienhuis>
Project Member
Thu 31 Mar 2016 11:52:47 AM UTC, comment #3: 

The 32bit installer from ftp.gnu.org crashes.
Tatsuro's installer for 64bit runs better.

But I do not know if they have the exact same mxe-octave setup, apart from 32/64 bit.

Philip Nienhuis <philipnienhuis>
Project Member
Wed 30 Mar 2016 11:40:57 PM UTC, comment #2: 

So the installer crashes?

If so, I have an updated version of nsis I compiled today, that may have fixed any issue with that.

Do we even need to show the windows 8 warning anymore?

John Donoghue <lostbard>
Project Member
Wed 30 Mar 2016 09:58:26 PM UTC, comment #1: 

Confirmed, the 32-bit version:
- won't install in Windows 10 (I get an error message stating something went wrong at 0xc00005)
- erroneously states it found itself running in Windows 8 (should have been Windows 8+) - this is just a cosmetic thingy.

There is a 64-bit Octave-4.1.0 version here:
http://www.tatsuromatsuoka.com/octave/Eng/Win/
that does install correctly.

After installation you need to build the octave-forge add-on packages yourself. In Octave:

more off
cd ([OCTAVE_HOME filesep "src"])
build_packages

and get yourself some coffee, as this can take a while (~15 minutes on my core-i5 laptop).

Before using an octave-forge package you have to load it using:
pkg load <package-name>

As far as I have tried this 64-bit version works fine in Win10.
_run_test_suite_ tells:

PASS 13020
FAIL     2
XFAIL   26
SKIPPED 54
(and no error/crash popup afterwards)

(title adapted)

Philip Nienhuis <philipnienhuis>
Project Member
Wed 30 Mar 2016 08:05:23 PM UTC, original submission:  
Charles O'Riley <nagashi>

 

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

Attach Files:
   
   
Comment:
   

Attached Files
file #36824:  GNU Octave error.pdf added by nagashi (6KiB - application/pdf - GNU Octave error on Windows 10 installation)

 

Carbon-Copy List
  • -email is unavailable- added by tmacchant (Posted a comment)
  • -email is unavailable- added by rik5 (Posted a comment)
  • -email is unavailable- added by jwe (Posted a comment)
  • -email is unavailable- added by mtmiller (Updated the item)
  • -email is unavailable- added by lostbard (Posted a comment)
  • -email is unavailable- added by nagashi (Submitted the item)
  • -email is unavailable- added by nagashi
  •  

    Do you think this task is very important?
    If so, you can add your encouragement to it.
    This task has 0 encouragements so far.

    Only project members can vote.

     

     

     

    Follow 11 latest changes.

    Date Changed by Updated Field Previous Value => Replaced by
    2016-07-02 rik5 StatusReady For Test => Fixed
        Open/ClosedOpen => Closed
    2016-04-29 mtmiller Summaryoctave-4.0.1-installer.exe (32bit) does not install on Windows 10 => mxe-octave: octave-4.0.1-installer.exe (32bit) does not install on Windows 10
    2016-04-08 philipnienhuis StatusConfirmed => Ready For Test
    2016-04-01 nagashi Attached File- => Added GNU Octave error.pdf, #36824
    2016-04-01 philipnienhuis Attached File- => Added win10_oct32_fntests_excerpt.log, #36823
    2016-03-31 mtmiller CategoryNone => Configuration and Build System
    2016-03-30 lostbard Dependencies- => bugs #47574 is dependent
    2016-03-30 philipnienhuis StatusNone => Confirmed
        SummaryMy environment is Windows 10: I received an error message during installation that stated that my OS was Windows 8. => octave-4.0.1-installer.exe (32bit) does not install on Windows 10
    2016-03-30 nagashi Carbon-Copy- => Added ceoriley@gmail.com

    Back to the top


    Powered by Savane 3.5