libiberty and standard includes.

[Earnie Boyd]

A modification to libiberty by Zack Weinberg on 5/29 to strsignal.c caused the
build process to abort because the installed
/usr/i686-pc-cygwin/include/string.h file contained a different prototype for
strsignal (it was missing a `const').  I was able to continue the build after
modifiying the installed string.h to match the newlib/libc/include/string.h
file.

However, shouldn't the build of libiberty ignore the standard include directory
and use the newlib version during the build process?

Regards,

=====
---
   Earnie Boyd: < mailto:earnie_boyd@yahoo.com >
            __Cygwin: POSIX on Windows__
Cygwin Newbies: < http://www.freeyellow.com/members5/gw32/index.html >
           __Minimalist GNU for Windows__
  Mingw32 List: < http://www.egroups.com/group/mingw32/ >
    Mingw Home: < http://www.mingw.org/ >

__________________________________________________
Do You Yahoo!?
Send instant messages & get email alerts with Yahoo! Messenger.
http://im.yahoo.com/