Re: libiberty requirements and ISO C90

2005-05-17 Thread Ian Lance Taylor
Mark Kettenis <[EMAIL PROTECTED]> writes: >From: Ian Lance Taylor >Date: 15 May 2005 23:20:14 -0400 > > >Well, we require an ISO C90 compiler; do we require ISO C90 libraries? >If we require the libraries, then we can remove a number of files from >libiberty, at least atexit

Re: libiberty requirements and ISO C90

2005-05-17 Thread Mark Kettenis
From: Ian Lance Taylor Date: 15 May 2005 23:20:14 -0400 Well, we require an ISO C90 compiler; do we require ISO C90 libraries? If we require the libraries, then we can remove a number of files from libiberty, at least atexit.c, memchr.c, memcmp.c, memcpy.c, memmove.c, memset.c,

Re: libiberty requirements and ISO C90

2005-05-16 Thread Gabriel Dos Reis
Ian Lance Taylor writes: [...] | I think the more conservative approach would be to simply add strerror | to AC_CHECK_DECLS, include in xstrerror.c (protected by | HAVE_STRING_H), and protect the strerror declaration with | #if !HAVE_DECL_STRERROR Thanks, that indeed makes sense. Patch pe

Re: libiberty requirements and ISO C90

2005-05-15 Thread Ian Lance Taylor
Gabriel Dos Reis <[EMAIL PROTECTED]> writes: > The file libiberty/xstrerror.c contains the following fragment > > #ifdef VMS > #include > #if !defined (__STRICT_ANSI__) && !defined (__HIDE_FORBIDDEN_NAMES) > extern char *strerror (int,...); > #define DONT_DECLARE_STRERROR >