|
From: | Markus Mützel |
Subject: | [Octave-bug-tracker] [bug #59923] mkoctfile fails on Windows if installed in a path with spaces on a file system without short file names |
Date: | Fri, 22 Jan 2021 05:19:30 -0500 (EST) |
User-agent: | Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/87.0.4280.141 Safari/537.36 Edg/87.0.664.75 |
Update of bug #59923 (project octave): Status: Need Info => Confirmed Release: 6.1.0 => dev Summary: mkoctfile helloworld.cc fails in 6.1.0 but is fine in 5.1.0 => mkoctfile fails on Windows if installed in a path with spaces on a file system without short file names _______________________________________________________ Follow-up Comment #9: Ok. So the file system on your drive D: doesn't store short file names. Installing Octave at the default destination in C: would probably work for you. If you chose to install on D: (or any other file system that doesn't store short file names), you should select a destination folder that doesn't contain spaces as a work-around. The real fix would be to *not* rely on short file names at all and correctly quote paths that might contain spaces where they are used in Octave. This is a larger project and probably too much for a dot release. As a first step, we should remove the conversion to short paths in the start up script imho because that masks potential issues on developer and tester machines (where conversion to short file names *does* work apparently). But we should wait with that until after Octave 6.2. In the mean time, users on affected machines should chose an installation folder that doesn't contain spaces. Re-targeting to the development branch. I believe there is a similar open bug report somewhere... _______________________________________________________ Reply to this item at: <https://savannah.gnu.org/bugs/?59923> _______________________________________________ Message sent via Savannah https://savannah.gnu.org/
[Prev in Thread] | Current Thread | [Next in Thread] |