Wed 10 Aug 2016 09:07:59 PM UTC, comment #11:
Problem solved after downgrading to 4.0.1.
|
Wed 10 Aug 2016 07:54:25 PM UTC, comment #10:
Thank you, Mike, that appears to be my situation. Since I can't even do a 'pkg install -forge ...' I seem to be in a bit of a mess. I'll try downgrading to 4.0.1 as a workaround.
|
Wed 10 Aug 2016 07:47:18 PM UTC, comment #9:
On a whim I did a
$ ln -s mkoctfile-4.0.1.exe mkoctfile-4.0.3.exe
and that took care of the missing mkoctfile error. But then I got:
>> pkg install -forge io
/home/jbailey/octave/io-2.4.2/x86_64-unknown-cygwin-api-v50+/cell2csv.oct: failed to load: No such process
error: called from 'doc_cache_create>create_cache' in file /usr/share/octave/4.0.3/m/help/doc_cache_create.m near line 106, column 18
Yikes.
|
Wed 10 Aug 2016 07:17:54 PM UTC, comment #8:
Jeff - so that's a yes that you installed the "octave-io" package (or however it is named) using the cygwin package manager, as opposed to the pkg command in Octave? If so, then this can be closed as a duplicate of bug #48601, because you are installing the pre-built packages that are the reason for that bug report.
|
Wed 10 Aug 2016 07:17:38 PM UTC, comment #7:
...and mkoctfile is where it's supposed to be:
$ ls -l /usr/share/octave/4.0.3/m/miscellaneous/mkoct*
-rw-r--r-- 1 jbailey Domain Users 5373 Jul 11 08:06 /usr/share/octave/4.0.3/m/miscellaneous/mkoctfile.m
$ ls -l /usr/bin/mkoct*
lrwxrwxrwx 1 jbailey Administrators 19 Aug 10 10:41 /usr/bin/mkoctfile -> mkoctfile-4.0.1.exe
-rwxr-xr-x 1 jbailey Administrators 89107 Jun 28 14:49 /usr/bin/mkoctfile-4.0.1.exe
|
Wed 10 Aug 2016 07:14:11 PM UTC, comment #6:
I installed them all at the same time, so I suppose io could have been broken as installed. I'm trying Philip's suggestion but I'm getting:
>> pkg install -forge io
pkg: unable to find the mkoctfile command, Octave installation is incomplete
error: called from '__gripe_missing_component__' in file /usr/share/octave/4.0.3/m/help/__gripe_missing_component__.m near line 53, column 3
|
Wed 10 Aug 2016 06:47:28 PM UTC, comment #5:
FYI, this may be bug #48601 if the io package was installed using cygwin's packaging system. That bug reports that packages built against 4.0.1 no longer work when Octave is upgraded to 4.0.3.
Anon - was the io package also installed via cygwin, or via "pkg install -forge" after Octave 4.0.3 was installed/upgraded?
|
Wed 10 Aug 2016 06:45:33 PM UTC, comment #4:
(Title adapted to mention cygwin)
|
Wed 10 Aug 2016 06:43:17 PM UTC, comment #3:
Oh I see, yes cygwin isn't in the dropdown list; rather mention it in the actual bug report text and specify Windows as OS, please.
I have never tried Octave on cygwin but AFAIK installing the io package should Just Work there,
If not I'd rather suspect a pkg.m bug specific for cygwin.
Hopefully a cygwin + Octave developer will jump to the rescue.
Have you tried my suggeztion in comment #1?
|
Wed 10 Aug 2016 05:29:02 PM UTC, comment #2:
Sorry, OS is Windows 7. Octave installed through Cygwin.
|
Wed 10 Aug 2016 12:34:32 PM UTC, comment #1:
Looks like an incompletely installed or otherwise borked io package.
parse_sp_range.m merely tries to invoke a function in a binary module, to no avail in your case. That it is lacking is a very telling eror message.
io-2.4.2 was released some weeks ago, please try:
pkg install -forge io
to get it and try your command again, and report back.
BTW, which operating system? "Other" isn't very informative :-)
(Title adapted)
|
Tue 09 Aug 2016 05:59:41 PM UTC, original submission:
When trying to write my array 'CV_Results' to the file 'CV_Results.xls' I get the following:
Octave 4.0.3 on Cygwin
|