Re: Mangled argument vector choking on spaces?

2014-12-30 Thread Bob Friesenhahn
On Mon, 29 Dec 2014, Kip Warner wrote: Unfortunately I need spaces on GNU systems and possibly elsewhere. I'm sure there is a way to do this and it's simply a matter of coalescing parts of the argument vector. From what I can see configure has the correct arguments, but some were accidentally

Re: Mangled argument vector choking on spaces?

2014-12-30 Thread Kip Warner
On Tue, 2014-12-30 at 08:53 -0600, Bob Friesenhahn wrote: On Mon, 29 Dec 2014, Kip Warner wrote: Unfortunately I need spaces on GNU systems and possibly elsewhere. I'm sure there is a way to do this and it's simply a matter of coalescing parts of the argument vector. From what I can see

Re: Mangled argument vector choking on spaces?

2014-12-30 Thread David A. Wheeler
On Mon, 29 Dec 2014 16:27:51 -0800, Kip Warner said: My configure.ac updates CXXFLAGS periodically during execution, such as via pkg-config. Some of the include paths returned from pkg-config's --cflags contain spaces which I require. ... Bob Friesenhahn said: The solution is to assure that

Re: Mangled argument vector choking on spaces?

2014-12-30 Thread Bob Friesenhahn
On Tue, 30 Dec 2014, David A. Wheeler wrote: This is a slightly tricky problem; comments welcome. It'd be nice to see a simple and relatively clean solution to the problem. I think use double-quotes when pathnames contain spaces is a plausible answer. The POSIX-style shell tosses the

Re: Mangled argument vector choking on spaces?

2014-12-30 Thread Paul Eggert
David A. Wheeler wrote: The idea would be that generated Makefiles (for example) could look like this: SBCL =/cygdrive/c/Program Files/Steel Bank Common Lisp/1.2.6/sbcl EGREP = /usr/bin/grep -E That wouldn't work for commands that do stuff like this: $(MAKE) SBCL=$(SBCL) which is a common