egcs as VxWorks cross-compiler problems

["Brad M. Garcia" <bgarcia at eng dot fore dot com>]

I think I am missing something important when it comes to creating
the cross compiler.  I hope someone can spot it (FYI, I've read the
crossgcc FAQ).

I have successfully built egcs as a cross compiler for an
i686 Linux host and an i960 VxWorks target.  When using my new
compiler on a simple "hello world" testing program, I get a
bunch of warnings like:

/vxworks/5.3.1/target/h/string.h:39: warning: declaration of `int
memcmp(const void *, const void *, unsigned int)'
/vxworks/5.3.1/target/h/string.h:39: warning: conflicts with built-in
declaration `int memcmp(const void *, const void *, long unsigned int)'
/vxworks/5.3.1/target/h/string.h:40: warning: declaration of `void *
memcpy(void *, const void *, unsigned int)'
/vxworks/5.3.1/target/h/string.h:40: warning: conflicts with built-in
declaration `void * memcpy(void *, const void *, long unsigned int)'
/vxworks/5.3.1/target/h/string.h:50: warning: declaration of `unsigned
int strlen(const char *)'
/vxworks/5.3.1/target/h/string.h:50: warning: conflicts with built-in
declaration `long unsigned int strlen(const char *)'

What is this "built-in" stuff?  When configuring egcs, I tried using
the --with-headers=/vxworks/5.3.1/target/h, but that didn't seem to
have any effect.

If I ignore the warnings, the program loads & runs fine.

Brad Garcia
   ___/  __ /  __ /  ___/ "Being the Linux of digital media
  __/   /  /  / _/  __/    would be a very good life."
_/    ____/ _/ _| ____/      - Jean-Louis Gassee, CEO of Be, Inc.