This is the mail archive of the mailing list for the GCC project.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

RE: why m68k-linux target is not building?

> -----Original Message-----
> From: gcc-owner On Behalf Of Andreas Schwab
> Sent: 17 May 2004 16:06

> <arcjai> writes:
> > Does that mean i need to have libc.a before i can
> > build a new version of gcc for m68k-linux?
> It makes life much easier. :-)
> > Or
> > 1. Get a m68k-linux-gcc binary
> > 2. Create libc.a using this compiler
> > 3. Then build new gcc version for m68k-linux.
> > 4. Create libc.a again using newly built compiler.
> That's the more difficult path.

  Does the old crossgcc minimal-compiler-prebuild trick still work?

1.  Configure m68k-linux-gcc using "--enable-languages=c --with-newlib
--without-headers", then build it using "make all-gcc install-gcc"

  This gets you a minimal version of m68k-linux-gcc that comes with no
standard includes, no crt startup code and no standard library.  But you
have a working cc1.exe, which is what you need for step two....

2.  Use this compiler to build the library from source.  Then install it to
the standard cross location or to some convenient place of your choice.

3.  Reconfigure m68k-linux-gcc without using any of the above options, and
possibly using
"--with-headers=/path/to/just-built-and-installed-libc-headers" if they're
in a nonstandard place.

4.  "make all install" then gives you your full crosscompiler-plus-stdlib

Can't think of a witty .sigline today....

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]