This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: documentation for cross compiling.
On Tue, Jul 03, 2001 at 07:26:57PM +0900, NIIBE Yutaka wrote:
> Hi HJ,
> > + case "${target}" in
> > + *linux*)
> > + # Linux targets have the C library header files.
> > + ;;
> > + *)
> > + inhibit_libc=-Dinhibit_libc
> > + ;;
> > + esac
> > else
> > if [test x$with_newlib = xyes]; then
> > inhibit_libc=-Dinhibit_libc
>
> This change is questionable. There's a situation where we don't have
> C library (yet). I mean, when we start development of porting, we
> don't have C library.
I have done that many times. It only happens once per port.
>
> Actually, I have such a kind of experience for our GNU/Linux support
> of SuperH. The bootstrap goes like this.
>
(0) Install the header files from the x86 port.
> (1) (Partial) build of GCC (with no C library), install.
> Language is C only.
It doesn't matter if the header files exist or not. You will get
just enough gcc to build glibc.
> (2) Build GNU C library, install.
> (3) (Full) build of GCC. We can support C++ language
That change to
(3) (Full) Reconfigure/rebuild of GCC. We can support C++ language
> (runtime) or others this time.
I usually have
(4) Install gcc
(5) Rebuild GNU C library, install.
(6) (Full) Reconfigure/rebuild of GCC. We can support C++ language
(runtime) or others this time.
H.J.