Re: fixinc w/ SYSTEM_INCLUDE_DIR set?

[Robert Lipe <robertl at dgii dot com>]

> > The reason I have to do this for a specific target (that I still haven't
> > submitted for approval/checking) that offers an "alternate universe" of
> > starttups, teardowns, libraries, and headers.   Having SYSTEM_HEADER_DIR
> > set allows things like fixincludes to DTRT.
> 
> This sounds like you want to "cross-compile" to yourself.
> Seems like arranging for CROSS_COMPILE to be set would 
> solve most of your problems?

Interesting idea.  I actually go to some effort to be sure that
CROSS_COMPILE *isn't* set becuase I then get into trouble in the libgcc
brothers and dejagnu starts trying to do the remote thing and all sorts
of undesirable stuff gets turned on.

The "alternate universe" binaries will run on the host, so I think
treating it as native really is a good thing.  The whole thing
bootstraps and mostly passes the testsuite, so I think most of the
strategic fibbing is pretty close to what we want.

The target in question is the Universal Development Kit from SCO.  Once
this kit and any necessary runtimes are installed it's possible to use
this kit to build binaries that run on SCO OpenServer, SCO Unixware 2,
and SCO Unixware 7.  What I've done is to rewire EGCS to talk to that
set of tools.  

So it's really only sort-of a cross compiler. :-)

RJL