Sun 22 May 2016 04:33:14 PM UTC, comment #5:
(Sorry for responding late, I was away last week)
Cleaning up old Octave remnants in mxe-octave build trees goes as follows (actually a "make uninstall"):
in <mxe-octave>/usr/x86_64-w64-mingw32/
delete the octave-<version> subdirectories in:
\share\octave\<version>
\lib\octave\<version>
\libexec\octave\<version>
and in <mxe-octave>\bin, delete:
liboct*.dll
mkoctf*.exe
octave*.exe
It can get trickier if dependencies have to be updated. Usually it is better to start a new mxe-octave build from scratch.
Hint:
Keep a separate pkg/ subdir somewhere and make a symlink in the new <mxe-octave> directory to it, that saves a lot of download time and bandwidth/allowance.
|
Tue 17 May 2016 08:41:50 PM UTC, comment #3:
I don't know, I would guess by deleting everything under the mxe-octave directory that contains a "4.1". That may be overkill, you may want to ask on the maintainers list, maybe John D or Philip have a best practice for cleaning and building Octave again.
So if you just delete this one textscan.cc-tst file from the installed Octave on Windows, do other textscan tests pass? I think the tests are now in the file file-io.cc-tst.
|
Tue 17 May 2016 06:47:38 PM UTC, original submission:
using MXE-Octave dev (changeset http://hg.savannah.gnu.org/hgweb/octave/rev/19e8eddd4773)
This test does not fail in Linux (Ubuntu).
|