Re: Bug in gnulib-tools prevents bison from bootstrapping

2007-06-23 Thread Bruno Haible
Eric Blake wrote: > Since forking external programs matters most on cygwin and mingw ... Also on AIX, HP-UX, IRIX, OSF/1, Solaris, one can avoid spawning 'cat': by using the 'print -r' trick from libtool.m4. 2007-06-23 Bruno Haible <[EMAIL PROTECTED]> * gnulib-tool (echo): Add a speed

Re: Bug in gnulib-tools prevents bison from bootstrapping

2007-06-23 Thread Bruno Haible
Paul Eggert wrote: > I think printf is portable nowadays, at least to the platforms that > gnulib-tool is likely to run on. Indeed, 'printf' is useful to use when we find that it is a shell built-in, namely on bash >= 2.0. (See the patch in the other mail.) But other than that? 'printf' is portab

Re: Bug in gnulib-tools prevents bison from bootstrapping

2007-06-23 Thread Bruno Haible
Eric Blake wrote: > POSIX requires that echo interpret backslash sequences. POSIX:2001 Technical Corrigendum 1 [1] mentions that BSD echo is POSIX compliant. Eric Blake and Paul Eggert wrote: > POSIX even admits this, and recommends the use of printf instead. > ... > One advantage of using printf

Re: Bug in gnulib-tools prevents bison from bootstrapping

2007-06-23 Thread Hans Aberg
On 23 Jun 2007, at 06:25, Eric Blake wrote: If you reconfigured autoconf after installing a newer GNU m4, and autoconf did not find the right m4, then that is a bug in autoconf, and should be dealt with there. Right. Since it was experienced by the developers on the Bug-Bison list, I hop

Re: Bug in gnulib-tools prevents bison from bootstrapping

2007-06-23 Thread Bruno Haible
Hello, Fernando Ferreira wrote: > I found out that gnulib-tools, > invoked by bootstrap to generate the gnulib-comp.m4 file, had a little > but vital bug that inserted these extraneous characters instead of the > desired behavior. The faulty lines are these, lines 2170 to 2180 on > gnulib/gnul

Re: Bug in gnulib-tools prevents bison from bootstrapping

2007-06-23 Thread Paul Eggert
Bruno Haible <[EMAIL PROTECTED]> writes: > libtool.m4 also tries other workarounds: searching for an 'echo' program > in $PATH:/usr/ucb (but how is this better than 'cat'?) or using a built-in > 'print -r' command (which shells except ksh have this?) or using 'printf' > (is that portable nowadays?

Re: Bug in gnulib-tools prevents bison from bootstrapping

2007-06-23 Thread Paul Eggert
Eric Blake <[EMAIL PROTECTED]> writes: > POSIX requires that echo interpret backslash sequences. Actually, POSIX says that the behavior of 'echo' is implementation-defined if any of the arguments contain backslash, or if echo's first operand is -n. If the implementation supports the XSI extensio