built-in declaration conflicts on SunOS & VxWorks targets.

[Brad M. Garcia]

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

> The normal way to fix this is to run fixincludes over the header
> files.  That is supposed to take care of issues like this.  Did you do
> that?

Is this something that I need to do separately, or is it part of 
the normal (configure/make all/make install) building process?
If it's a separate step, then no, I didn't do it.

And what exactly does running "fixincludes" do?  Does it create new
header files?  Does it change gcc's internal declarations?

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