OMNeT++/OMNEST Bug Tracker - OMNeT++
View Issue Details
0000938OMNeT++Installer / Productizingpublic2015-10-23 21:312016-02-04 12:56
whatever2 
rhornig 
normalmajoralways
resolvedwon't fix 
LinuxElementary OS/ Ubuntu3.16.0-51-generi
4.6 
5.0 
0000938: configure script cannot execute successfully when parent directory name contains white space.
"configure" script cannot execute successfully, if parent directory name contains white space(s). As you can see this might have serious implications:
"
...
./configure: line 7813: test: too many arguments
chmod: cannot access '/home/user/foobar/dir': No such file or directory
chmod: cannot access 'has': No such file or directory
chmod: cannot access 'blanks/omnetpp-4.6/bin/__probe__': No such file or directory
...
rm: cannot remove '/home/user/foobar/dir': No such file or directory
rm: cannot remove 'has': No such file or directory
rm: cannot remove 'blanks/omnetpp-4.6/bin/__probe__': No such file or directory
"
Extract omnetpp-4.6 to directory "~/dir has blanks/". Then execute:
$ cd "~/dir has blanks/"
$ . setenv
$ ./configure
From a quick look into the "configure" script, I think this might be caused by some missing quotation mark all over the place. E.g.
(line 7819) chmod +x $omnetpp_bin_dir/$probefile

Fixing THIS LINE...
(line 7819) chmod +x "$omnetpp_bin_dir/$probefile"

...corrects THAT PART of the issue. From what I've seen there needs to be a serious overhaul of that script in terms of correctly quoted variables.
No tags attached.
Issue History
2015-10-23 21:31whatever2New Issue
2015-10-26 11:36whatever2Note Added: 0001151
2016-02-04 12:56rhornigNote Added: 0001162
2016-02-04 12:56rhornigStatusnew => resolved
2016-02-04 12:56rhornigFixed in Version => 5.0
2016-02-04 12:56rhornigResolutionopen => won't fix
2016-02-04 12:56rhornigAssigned To => rhornig

Notes
(0001151)
whatever2   
2015-10-26 11:36   
Sorry, messed up the platform, os, ... part. Platform is x86_64 and Elementary Os is based on Ubuntu 14.04 LTS.
(0001162)
rhornig   
2016-02-04 12:56   
Unfortunately, this is a known (and documented) limitation of the build system we are using. This *may* fixed once/if we move to cmake build.