Re: i370 port - constructing compile script

["Ulrich Weigand" <uweigand@de.ibm.com>]

Paul Edwards wrote:

> Ok, perhaps this error was because when I hit errors in intl,
> which I've never used before, I just went to the gcc directory and
> did a make.
> 
> Regardless, I added a stack of touch xxx.o in the intl directory
> after the failure of the first make, which allowed me to do a second
> make, and then it was satisfied with the intl directory and moved
> on to the gcc directory, where it did in fact invoke the correct
> gcc rather than the cross-compiler.

If you use --disable-nls on the configure line, the intl directory
should be skipped ...

> The next thing I hit was that genmodes didn't compile because
> there were conflicts between the strsignal function in the
> Linux include files and the system.h.  Looking at the system.h,
> it was including things in because it thought that the prototypes
> didn't exist.  Which would have been true for the cross-compiler,
> but isn't true for a native gcc.  How are those two different things
> meant to be reconciled?

Before including "system.h", generator files include "bconfig.h"
where core compiler files include "config.h".  The former then
in turn includes "auto-build.h", while the latter includes
"auto-host.h".  These contain the configure results for the
--build= and --host= systems, respectively.

All this should work automatically if you use the proper
configure options, so something odd must be going on ...

Are you running the top-level configure?  (If you run a
subdirectory configure, e.g. the one in gcc/, directly,
things may not work correctly.)

Bye,
Ulrich

-- 
  Dr. Ulrich Weigand
  GNU Toolchain for Linux on System z and Cell BE
  Ulrich.Weigand@de.ibm.com