Re: special characters in filenames in error messages

2008-12-03 Thread Paolo Bonzini
Karl Berry wrote: > > I don't see why \n should be special? > > For the same reason why we should escape :, i.e. to ensure that each > line can be interpreted as FILE:LINE:MESSAGE. > > Obviously we have to escape newline characters. In the original > proposal, they would be escaped a

Re: Bus error

2008-12-03 Thread Eric Blake
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 [please don't top-post] According to Thomas J. Duck on 12/3/2008 7:29 PM: > Hi Eric, > > Thanks for your email -- the quickest response to a bug report ever! > > 'locate libsigsegv' turns up nothing. It doesn't turn up anything for me, ei

Re: Bus error

2008-12-03 Thread Thomas J. Duck
Hi Eric, Thanks for your email -- the quickest response to a bug report ever! 'locate libsigsegv' turns up nothing. If you have other tests that you would like me to run, please let me know. I'm happy to help where I can. Cheers, Tom -- On 3-Dec-08, at 10:08 PM, Eric Bl

Re: Bus error

2008-12-03 Thread Eric Blake
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 [adding bug-gnulib, as the owner of the c-stack module] According to Thomas J. Duck on 12/3/2008 6:49 PM: > Hello Thomas, > > I have installed m4-1.4.12 on my Mac OS X 10.4 system. 'Make > check' results in the error below. If there is any

Re: _AC_LANG_OPENMP and m4_copy

2008-12-03 Thread Bruno Haible
Hello Ralf, Thanks for the report and fix. Eric Blake wrote: > Looks fine to me, but let Bruno chime in before committing. I agree with > your approach of fixing gnulib to avoid the problem by not competing when > a new-enough autoconf provides the macro I agree with this approach. But the patc

Re: special characters in filenames in error messages

2008-12-03 Thread Karl Berry
it is *required* only if the filename - contains a ':' or newline, or - starts with a '"'. Is that the intent? Yes. - For parsing: - If the first character is a '"', then the escaped syntax is in use. The filename is enclosed in "..."; inside,

Re: _AC_LANG_OPENMP and m4_copy

2008-12-03 Thread Eric Blake
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 According to Ralf Wildenhues on 12/3/2008 1:01 PM: > When I try to `./autogen.sh --quick' CVS gettext, using git Autoconf, > things fall over like this (several instances): > > | gnulib-m4/openmp.m4:29: error: m4_copy: won't overwrite defined macro:

_AC_LANG_OPENMP and m4_copy

2008-12-03 Thread Ralf Wildenhues
When I try to `./autogen.sh --quick' CVS gettext, using git Autoconf, things fall over like this (several instances): | gnulib-m4/openmp.m4:29: error: m4_copy: won't overwrite defined macro: _AC_LANG_OPENMP(C++) | gnulib-m4/openmp.m4:29: the top level | autom4te: /usr/bin/m4 failed with exit stat

Re: special characters in filenames in error messages

2008-12-03 Thread Bruno Haible
Hello Karl, > new proposal is to use octal escapes \ooo (and > nothing else). Specifically: > > 1) if the first character of the source is a ", the source name extends >to the next ". (Including :'s, for example.) > 2) within that "...", \ooo is recognized. For instance, \042=" and \134=\,

Re: special characters in filenames in error messages

2008-12-03 Thread Bruno Haible
Hello Karl, > new proposal is to use octal escapes \ooo (and > nothing else). Specifically: > > 1) if the first character of the source is a ", the source name extends >to the next ". (Including :'s, for example.) > 2) within that "...", \ooo is recognized. For instance, \042=" and \134=\,