Re: directory names with blanks break automake builds

2008-05-19 Thread Peter Simons
Bob Proulx writes: > Unix make can't handle spaces in filenames. It always splits upon > spaces. You are right. Take care, Peter

Re: directory names with blanks break automake builds

2008-05-19 Thread Bob Proulx
Peter Simons wrote: > Bob Proulx writes: > > This is a documented limitation. See the following reference. > > > > > http://www.gnu.org/software/automake/manual/html_node/limitations-on-file-names.html#limitations-on-file-names > > I am sorry, but that page doesn't seem to mention this prob

Re: directory names with blanks break automake builds

2008-05-19 Thread Peter Simons
Ralf Wildenhues writes: >> The problem I'm hitting is that ${srcdir} contains a blank, so the >> path to 'install-sh' contains a blank too: > > I think that's one of the remaining unfixed problems, unfortunately. I see, thank you for the clarification. As far as I'm concerned, this problem is

Re: directory names with blanks break automake builds

2008-05-19 Thread Ralf Wildenhues
* Peter Simons wrote on Sun, May 18, 2008 at 02:36:58PM CEST: > Ralf Wildenhues writes: > > > Well, at least white space in targets and dependencies is forbidden > > with make. > > Whitespace can be quoted with '\'. At least in GNU Make, the following > snippet works just fine: > > | output\

Re: directory names with blanks break automake builds

2008-05-18 Thread Peter Simons
Ralf Wildenhues writes: >> I don't know what limitation you refer to. Can you please explain how >> make's design causes these problems? > > Well, at least white space in targets and dependencies is forbidden > with make. Whitespace can be quoted with '\'. At least in GNU Make, the following

Re: directory names with blanks break automake builds

2008-05-18 Thread Ralf Wildenhues
* Peter Simons wrote on Sun, May 18, 2008 at 01:29:47PM CEST: > Bob Proulx writes: > > > This leads to 'make' not being designed to handle filenames with > > whitespace and of course automake tries to produce portable make > > configurations. > > I don't know what limitation you refer to. Can

Re: directory names with blanks break automake builds

2008-05-18 Thread Ralf Wildenhues
Hi Peter, * Peter Simons wrote on Sat, May 17, 2008 at 06:07:39PM CEST: > I just ran across an interesting problem with automake 1.10. Just unpack > any other build into a directory called, say "/tmp/test automake", and > run it. In my particular case, the makefiles failed to call the local > copy

Re: directory names with blanks break automake builds

2008-05-18 Thread Peter Simons
Bob Proulx writes: >> [Unpack] any other build into a directory called, say "/tmp/test >> automake", and run it. In my particular case, the makefiles failed >> to call the local copy of install-sh because of the blank. > > This is a documented limitation. See the following reference. > >

Re: directory names with blanks break automake builds

2008-05-17 Thread Bob Proulx
Peter Simons wrote: > I just ran across an interesting problem with automake 1.10. Just unpack > any other build into a directory called, say "/tmp/test automake", and > run it. In my particular case, the makefiles failed to call the local > copy of install-sh because of the blank. I checked my con

directory names with blanks break automake builds

2008-05-17 Thread Peter Simons
Hi, I just ran across an interesting problem with automake 1.10. Just unpack any other build into a directory called, say "/tmp/test automake", and run it. In my particular case, the makefiles failed to call the local copy of install-sh because of the blank. I checked my configure.ac script and Ma