RE: Configuring in directories with spaces fails in ghc6.4
On 22 February 2005 12:05, Anders Höckersten wrote:
It seems the ghc 6.4 release candidates' configure scripts fail if you run them in a directory structure containing a space. In my case, being in /home/chucky/My Downloads fails with: configure: creating ./config.status config.status: creating ghc.spec config.status: creating VERSION config.status: creating docs/users_guide/ug-book.xml config.status: creating mk/config.mk config.status: creating mk/version.mk ./configure: line 20341: cd: /home/chucky/My: No such file or directory
Quite possibly. No doubt we'd have to add a million quotes to the build system to fix this; it's not going to happen any time soon. "don't do that" Cheers, Simon
"Simon Marlow"
It seems the ghc 6.4 release candidates' configure scripts fail if you run them in a directory structure containing a space.
Quite possibly. No doubt we'd have to add a million quotes to the build system to fix this; it's not going to happen any time soon.
Yes. Someone recently reported the same problem with nhc98's configure script, and I actually tried adding the quotes. It is nightmarish - you'll quickly discover a need for quotes inside quotes and worse, depending on how many levels of shells/tools/Makefiles a variable gets passed through. In the end, it was far simpler to abandon the idea. However, it could be worthwhile halting with an error message. case `pwd` in *' '*) echo "Error: nhc98 will not build in a directory with spaces anywhere" echo " in the full pathname." echo "Suggestion: move the build tree somewhere else." exit 1 ;; esac Regards, Malcolm
participants (2)
-
Malcolm Wallace -
Simon Marlow