RE: warnings about auto importing sys_errlist / sys_nerr on Cygwin

[Jay <jay dot krell at cornell dot edu>]

Wait..sorry, I need to look again, double check config.h,
preprocess, disassemble..

errno_max always references sys_nerr, part of the problem,
but I don't see where the sys_errlist reference is.

More later, much later.

How about, another approach, use autoconf to look for a header
that declares sys_nerr and sys_errlist? 

like: 

for header in (errno.h stdlib.h stdio.h string.h ?)
   try to compile: 
      #include header
      void F() { const void* a = &sys_nerr; a = &sys_errlist; }
   if compiles ok, use header 
   else use the existing code/declarations? 
 
 - Jay


> To: jay.krell@cornell.edu
> CC: gcc-patches@gcc.gnu.org
> Subject: Re: warnings about auto importing sys_errlist / sys_nerr on Cygwin
> From: iant@google.com
> Date: Tue, 2 Sep 2008 15:39:14 -0700
>
> Jay  writes:
>
>> Could be every has sys_errlist, and everyone declares it in a reasonably common place.
>> ??
>
> I'm sure that's not true. But it's possible that we can say that the
> code which uses libiberty should never refer to sys_errlist, and then
> only use sys_errlist for systems which don't have strerror.
>
> Ian