Paul Edwards wrote:
> Would you be able to give me the two suggested configure
> commands so that I can find out the answer to the above, one
> way or another?
For step 2 (building the cross-compiler), you'd need something
along the lines of
.../configure --target=i370-mvs --prefix=... --with-sysroot=... \
--enable-languages=c
where prefix points to the directory where the cross-compiler
should be installed, and sysroot points to the directory where
the MVS libraries and header are installed.
Then you need to build and install the cross-compiler (using
make and make install). For the subsequent step, you need to
make the cross-compiler available in the PATH.
For step 3 (cross-building a native compiler), you'd need
something along the lines of
.../configure --build=i686-linux --host=i370-mvs --target=i370-mvs \
--prefix=... --with-build-sysroot=... --enable-languages=c
This configure run will then use the i370-mvs-gcc cross-compiler
you built in step 2 in order to detect MVS host properties.
> Or does the configure process attempt to run the executables
> as well?
No, that wouldn't work (the exectuables are for a different architecture
than the build system ...).
> But it won't be able to correctly determine the stack direction
> if it does that. So that is the sort of thing I would need some
> intrusive code (out of my 20 lines quota!) to force it to 0
> (unknown stack direction).
I don't think GCC needs to know the stack direction of the *host*
system. (It does need to know the stack direction of the *target*
system, but this is not detected by configure, but determined by
target macro settings from the config/i370/*.h files.)
Bye,
Ulrich
--
Dr. Ulrich Weigand
GNU Toolchain for Linux on System z and Cell BE
[email protected]
