Re: built-in declaration conflicts on SunOS & VxWorks targets.

[Ian Lance Taylor <ian at cygnus dot com>]

   Date: Wed, 18 Feb 1998 10:28:58 -0500 (EST)
   From: "Brad M. Garcia" <bgarcia@fore.com>

   On Wed, 18 Feb 1998, Ian Lance Taylor wrote:

   > It is normally run automatically.  However, fixincludes does need to
   > be able to find your header files.  This is easy on a native
   > system--just look in /usr/include

   It appears to not work, because I have this problem when creating a
   native compiler for a SunOS box.

Can't help you there, except to point you at the files in
gcc-lib/..../include and the fixincludes script itself.

It's conceivable that you've run across a case which fixincludes
should be handling, but isn't.  In any case, when you find a problem
in a header file, you should fix fixincludes, not the builtin
declarations in the compiler, unless of course the builtin
declarations are clearly in error.

   > --but it is not so easy in a
   > cross-compilation environment.  As I recall, if you put your header
   > files in the directory ${exec_prefix}/${target_alias}/sys-include,
   > then fixincludes will run on them.

   So, do I need to manually copy them to here?  Will a soft link do, or
   does it try to change these files instead of creating new ones?

As I recall, it will not try to change those files.

Ian