|
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: | Mon, 25 Jan 2021 13:10:13 -0500 (EST) |
User-agent: | Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/88.0.4324.96 Safari/537.36 Edg/88.0.705.50 |
Update of bug #59923 (project octave): Status: Confirmed => In Progress _______________________________________________________ Follow-up Comment #15: The patch from comment #14 works for me. But I'm having second thoughts whether it is ok to replace the double quotes in the `echo` part of the commands in subs-config-vals.in.sh by single quotes. Is it possible that these strings will contain variables that need to be expanded? They are "plain" text for me at least. I limited the number of strings that are modified to the ones which are used in mkoctfile and which are modified already anyway. I also added a FIXME note about this. I pushed that part to default here: https://hg.savannah.gnu.org/hgweb/octave/rev/78c660a8ba84 I'll probably push the patch in comment #14 to MXE Octave tomorrow or the day after if the buildbots are ok with the first change and no one opposes. It might make sense to use the attached patch after that to have long file names in default Octave on Windows for developers and testers. (file #50784) _______________________________________________________ Additional Item Attachment: File name: bug59923_mxe-octave_default_no_shortpath.patch Size:2 KB <https://file.savannah.gnu.org/file/bug59923_mxe-octave_default_no_shortpath.patch?file_id=50784> _______________________________________________________ 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] |