[Octave-bug-tracker] [bug #53695] tar.m and unpack.m are incompatible with BSD tar

[Andrew Janke]

Follow-up Comment #23, bug #53695 (project octave):

I kinda tested on Windows 10 using Octave 4.4.1 (using the Windows installer
downloaded from https://www.gnu.org/software/octave/download.html) and these
new scripts. Seems to work. "test tar" passes. "test unpack" fails, but I
think that's because I'm mixing stable M-files with a 4.4.1 Octave.


>> test tar
PASSES 6 out of 6 tests
>> test unpack
>> test unpack
***** testif HAVE_ZLIB
 envvar = {"TMPDIR", "TMP"};
 envdir = cellfun (@(x) getenv (x), envvar, "uniformoutput", false);
 unwind_protect
   cellfun (@(x) unsetenv (x), envvar);
[...]
 end_unwind_protect
!!!!! test failed
'__octave_link_file_remove__' undefined near line 139 column 5


Are there something like nightly or snapshot builds of stable available for
Windows? I'm not set up to build Octave on Windows.

I suspect this won't be a problem on Windows, because there, instead of using
a tar program provided by the system, Octave ships with a GNU tar.exe in its
own bin dir, and that bin dir is right near the front of the %PATH% in the
Octave process, so it's unlikely to be shadowed by a tar command from another
source. (And for that matter, I don't know of any source of a BSD tar on
Windows; there's no BSD equivalent of WSL/Cygwin/msys AFAIK.)

    _______________________________________________________

Reply to this item at:

  <https://savannah.gnu.org/bugs/?53695>

_______________________________________________
  Message sent via Savannah
  https://savannah.gnu.org/