octave-bug-tracker
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Octave-bug-tracker] [bug #62090] [octave forge] (io) Installation fails


From: Georg Wiora
Subject: [Octave-bug-tracker] [bug #62090] [octave forge] (io) Installation fails with spaces in path
Date: Wed, 23 Feb 2022 06:54:20 -0500 (EST)

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

I tried to run installation manually with path string correctly set and got
the following output.


C:\Users\USER.CKH\AppData\Local\Temp\octtest\io-2.6.4\src>"\Program Files\GNU
Octave\Octave-6.4.0\usr\bin\make.exe" --trace --no-silent --debug=ALL
GNU Make 4.3
Built for x86_64-pc-msys
Copyright (C) 1988-2020 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
Reading makefiles...
Reading makefile 'Makefile'...
Updating makefiles....
 Considering target file 'Makefile'.
  Looking for an implicit rule for 'Makefile'.

[....output cropped....]

Makefile:6: update target 'csvexplode.oct' due to: csvexplode.cc
mkoctfile csvexplode.cc
Putting child 0x600076140 (csvexplode.oct) PID 387 on the chain.
Live child 0x600076140 (csvexplode.oct) PID 387
g++: error: Files\GNU: No such file or directory
g++: error: Octave\Octave-6.4.0\mingw64\/include: No such file or directory
Reaping losing child 0x600076140 PID 387
make: *** [Makefile:6: csvexplode.oct] Error 1


It seems that "mkoctfile" is is messing with blanks in path names by not
correctly quoting path strings handed to g++.

I can call it directly and get the following result:


C:\Users\USER\AppData\Local\Temp\octtest\io-2.6.4\src> mkoctfile
csvexplode.cc
g++: error: Files\GNU: No such file or directory
g++: error: Octave\Octave-6.4.0\mingw64\/include: No such file or directory


It is obviously breaking the path string at every blank.

I don't know if we can do something here...

    _______________________________________________________

Reply to this item at:

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

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




reply via email to

[Prev in Thread] Current Thread [Next in Thread]