[Octave-bug-tracker] [bug #62090] [octave forge] (io) Installation fails with spaces in path

[Philip Nienhuis]

Follow-up Comment #5, bug #62090 (project octave):

io's Makefile is just:

all: csvexplode.oct csv2cell.oct csvconcat.oct cell2csv.oct col2num.oct
num2col.oct

MKOCTFILE ?= mkoctfile
  
%.oct: %.cc
        $(MKOCTFILE) $<

clean:
        rm -f *.o octave-core core *.oct *.mex *~


@Markus:
Weren't LFNs morphed no more into 8.3 style file names in mxe-octave a while
ago? or was that for Octave-7.x? ISTR something like that.

@OP:
I usually install Octave into s/th along the lines of
C:\Programs\Octave\Octave-<version>-<date>
precisely to avoid space-in-filename issues. There are many other OSS programs
that don't like spaces in their installation paths either, Octave is by no
means unique.

But: I just installed Octave=6.4.0 into
C:\Programs\GNU Octave\Octave-6.4.0
(note: space in dir name!) and installed io:

pkg unload -nodeps io       ## Just to be sure that loaded binary
clear -f                    ## functions don't hold their
                            ## function files on disk hostage
pkg uninstall -global io    ## Uninstall just to be sure
pkg install -verbose -forge -global io  ## Install in global
                            ## store, i.e. dir name with a space


w/o any issues. So I wonder what's special about your Octave installation.
Furthermore, 'C:\Program Files' and 'C:\Program Files (x86)' are protected by
Windows, you just cannot install or copy anything there w/o admin credentials.

    _______________________________________________________

Reply to this item at:

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

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