This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: i370 port - constructing compile script
- From: "Ulrich Weigand" <uweigand at de dot ibm dot com>
- To: mutazilah at gmail dot com (Paul Edwards)
- Cc: iant at google dot com (Ian Lance Taylor), gcc at gcc dot gnu dot org
- Date: Mon, 19 Oct 2009 16:19:38 +0200 (CEST)
- Subject: Re: i370 port - constructing compile script
Paul Edwards wrote:
> Ok, I used
>
> ../configure --target=i370-mvspdp --prefix=/devel/mvscross --with-sysroot=/devel/mvshead
> --enable-languages=c
>
> plus make and make install
>
> then I went to
>
> mvscross/bin and renamed i370-mvspdp-gcc to i370-mvspdp-xxx
>
> and replaced it with a script that does:
>
> i370-mvspdp-xxx -S $*
Maybe a more generic way to work around the missing assembler and linker
would be to provide dummy scripts i370-mvspdp-as and i370-mvspdp-ld, where
the "assembler" would simply copy the assembler source input as text to the
"object" file output, and the "linker" would collect all input files into
a tar file (or some other archive) as "executable" output ...
This would allow usual build processes (including "make") to proceed as
expected.
> > 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
>
> ./configure --build-i686-linux --host=i370-mvspdp --target=i370-mvspdp --prefix=/devel/mvshost
> --with-build-sysroot=/devel/mvshead --enable-languages=c
>
> I wasn't sure if that --with-build-sysroot was right - pointing to
> the same headers, but couldn't think of anything else to do with it!
That should be fine. (The --with-build-sysroot option may actually not
be required at all when building just a C compiler.)
> Ok, it (3.4.6 I am using) got as far as:
>
> checking size of void *... configure: error: cannot determine a size of void
> *
> make: *** [configure-gcc] Error 1
>
> I haven't had a chance to investigate what it's trying to do there, to
> see if I can devise a workaround.
The compiler error output found in the config.log file should hopefully
point to the problem ...
Bye,
Ulrich
--
Dr. Ulrich Weigand
GNU Toolchain for Linux on System z and Cell BE
Ulrich.Weigand@de.ibm.com