Re: vfprintf, scanf portability

2011-03-15 Thread Ralf Wildenhues
* Bruno Haible wrote on Tue, Mar 15, 2011 at 09:16:53PM CET: > Paul Eggert wrote: > > http://buildlogs.pld-linux.org/index.php?dist=th&arch=athlon&ok=1&name=gcc&id=78974776-f08b-4b31-a977-863793c73c22&action=text > > This log is inconsistent: In line 872 it shows > > checking for strrchr... che

Re: vfprintf, scanf portability

2011-03-15 Thread Bruno Haible
Paul Eggert wrote: > >      Be aware that @code{vfprintf} is not always available. Already 5 years ago, all gnulib target platforms had vfprintf: $ ./show-portability vfprintf libcaix-4.3.2 libcaix-5.1.0 libcaix-5.2.0 libcaix-5.3.0a

Re: vfprintf, scanf portability

2011-03-15 Thread Paul Eggert
On 03/15/2011 11:34 AM, Karl Berry wrote: The GNU coding standards have had these two items since the beginning. First: Don't use the return value of @code{sprintf}. It returns the number of characters written on some systems, but not on all systems. This refers to very old implemen

Re: vfprintf, scanf portability

2011-03-15 Thread Eric Blake
On 03/15/2011 12:34 PM, Karl Berry wrote: > The GNU coding standards have had these two items since the beginning. > > First: > Don't use the return value of @code{sprintf}. It returns the number of > characters written on some systems, but not on all systems. > > I don't see this mentio

vfprintf, scanf portability

2011-03-15 Thread Karl Berry
The GNU coding standards have had these two items since the beginning. First: Don't use the return value of @code{sprintf}. It returns the number of characters written on some systems, but not on all systems. I don't see this mentioned in the Gnulib entry for sprintf at http://www.gnu.

RE: test-binary-io unit test failure under MingW + fix patches

2011-03-15 Thread dave
Bruno,I wanted to follow-up with you with the latest information.  I used the --create-testdir option per your last mail and the test-binary-io unit test passes for me as well.  However, when I create a new project manually (using the same directory as I used with the --dir option alongside --creat

Re: sigprocmask.c appears to be incompatible w/ system headers

2011-03-15 Thread Bruno Haible
Godfrey, Keith wrote: > Program received signal SIGSEGV, Segmentation fault. > 0x2b630905ede8 in sigemptyset () >     from > /global/home/keith/software/octave-3.4.0/src/.libs/liboctinterp-3.4.0.so > 2: x/10i $pc > 0x2b630905ede8 :    callq  0x2b636c0ef3da > 0x2b630905eded :    sub    (%rax),%

Re: sigprocmask.c appears to be incompatible w/ system headers

2011-03-15 Thread Godfrey, Keith
Hi Bruno, Thank you for quick the response. There is no sigprocmask.lo in this list. This is normal; gnulib's sigprocmask.c is not compiled on glibc systems. You can see from the gnulib documentation that this source file is