Re: error: avoid gcc warning

2011-06-20 Thread Eric Blake
On 06/18/2011 04:08 PM, Bruno Haible wrote: > Eric Blake wrote on 2011-06-07: >>> It's because /usr/include/string.h on this system does not always declare >>> strerror_r (only if _REENTRANT or _THREAD_SAFE is defined). This fixes it >>> (without requiring the 'strerror_r' module). >> >> This raise

Re: error: avoid gcc warning

2011-06-18 Thread Bruno Haible
Eric Blake wrote on 2011-06-07: > > It's because /usr/include/string.h on this system does not always declare > > strerror_r (only if _REENTRANT or _THREAD_SAFE is defined). This fixes it > > (without requiring the 'strerror_r' module). > > This raises an interesting question.  The 'error' module

Re: error: avoid gcc warning

2011-06-06 Thread Eric Blake
On 06/05/2011 07:00 AM, Bruno Haible wrote: > On OSF/1 5.1 with gcc, I'm seeing this warning: > > error.c:170: warning: implicit declaration of function 'strerror_r' > > It's because /usr/include/string.h on this system does not always declare > strerror_r (only if _REENTRANT or _THREAD_SAFE is

error: avoid gcc warning

2011-06-05 Thread Bruno Haible
ithout requiring the 'strerror_r' module). 2011-06-05 Bruno Haible error: Avoid gcc warning. * lib/error.c (strerror_r): Declare also when its return type is 'int'. --- lib/error.c.origSun Jun 5 14:50:15 2011 +++ lib/error.c Sun Jun 5 14:49:59 2011 @@ -97