GCC-2.95.2 on HP-UX 11 : Warnings from <string.h>

["Masterson, David" <David dot Masterson at kla-tencor dot com>]

For the following piece of code:

//------
#include <string.h>
int main() {}
//------

I get the following warnings from a simple gcc compile (gcc -c testit2.c):

In file included from testit2.c:1:
/usr/local/lib/gcc-lib/hppa2.0w-hp-hpux11.00/2.95.2/include/string.h:29:
warning: conflicting types for built-in function `memcmp'
/usr/local/lib/gcc-lib/hppa2.0w-hp-hpux11.00/2.95.2/include/string.h:85:
warning: conflicting types for built-in function `memcpy'
/usr/local/lib/gcc-lib/hppa2.0w-hp-hpux11.00/2.95.2/include/string.h:87:
warning: conflicting types for built-in function `memset'

After installing binutils and GCC-2.81, I built this version of GCC from
sources using the following commands:

mkdir gcc-2.95.2-objs
cd gcc-2.95.2-objs
../gcc-2.95.2/configure --enable-shared --with-gnu-as --without-gnu-ld
--enable-cpp
make bootstrap
make install

I now see that the above warnings showed up in a lot of places during the
build of GCC.  Thus far, all programs seem to work, but I'd like to
determine the best way to get rid of these warnings.  Apparently, GCC is not
processing the string.h file from HP-UX 11 correctly when it does the
include file fixups during the bootstrap process.  I've attached a copy of
the string.h mentioned above to this message.

Has anyone run into this issue yet?  What's the best way to handle this?  Do
I need to pass another "-D" argument to the command line or should I just
modify the string.h file?  Where are the built-in function definitions that
the warnings refer to?

--
David Masterson
*	KLA-Tencor Corp.
*	David.Masterson@kla-tencor.com

 <<string.h>>

string.h