[Octave-bug-tracker] [bug #50005] MXE Octave: using 8.3 file convention?

[Philip Nienhuis]

Follow-up Comment #6, bug #50005 (project octave):

Some experimenting here indicates that this change finally seems to offer a
solution for installing Octave in paths with spaces (e.g., "C:\Program Files"
on Windows).
Yet I think more testing is required to confirm this.

I had to comment out the relevant stanza in makeinst_script.sh and create an
installer after that. 
Installing octave as administrator in C:\Program Files (where the 64-bit
programs are to be installed) worked fine on my Windows 7 box.
Afterwards I installed the OF-octclip package (a binary package) and that went
quite well; but very slow compared to doing the same as ordinary user (and
Octave in a path without spaces) - I suppose it has to do with the
administrator status.

Installing the mapping package (invoking mkoctfile) also goes fine, until the
file copying / doc generating stage where Octave seems to hang forever. But it
finally worked.

    _______________________________________________________

Reply to this item at:

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

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