This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: documentation for cross compiling.
- To: "H . J . Lu" <hjl at lucon dot org>
- Subject: Re: documentation for cross compiling.
- From: "M. R. Brown" <mrbrown at 0xd6 dot org>
- Date: Tue, 3 Jul 2001 18:30:33 -0500
- Cc: NIIBE Yutaka <gniibe at m17n dot org>, gcc at gcc dot gnu dot org
* H . J . Lu <hjl@lucon.org> on Tue, Jul 03, 2001:
>
> I don't think it is necessary. Bootstrap glibc/gcc for the very first
> time is always a special case. I don't think you can automate it.
Hmm, we're still talking about cross-compilers right? If so, then a
minimal C compiler can be "bootstrapped" by:
# ../configure ... --with-newlib --without-headers
# make all-gcc
# make install-gcc
That can be automated.
> After that, you just need the appropriate glibc header files and
> binary files to get a correct cross compiler, including C and C++.
You're right, after you create the C compiler, you can build glibc; the
only problem I have is with gcc-3.0 where some part of glibc links with
(the nonexistent) libgcc_s, but it could be because the specs I'm using
(Kaz Kojima's patches) for SuperH (I don't know if this is a problem on
other archs). I solve that with a symlink to the static libgcc.
I can only build libgcc_s after I have the glibc headers, e.g. the second
(full) build of gcc.
M. R.