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 defined). This fixes it > (without requiring the 'strerror_r' module).
This raises an interesting question. The 'error' module should probably depend on strerror_r, not strerror. > > -# if !HAVE_DECL_STRERROR_R && STRERROR_R_CHAR_P > +# if !HAVE_DECL_STRERROR_R at which point, this is the wrong compile-time check, since use of the strerror_r-posix module would guarantee a declaration, even when !HAVE_DECL_STRERROR_R. -- Eric Blake ebl...@redhat.com +1-801-349-2682 Libvirt virtualization library http://libvirt.org
signature.asc
Description: OpenPGP digital signature
