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: Building glibc for a mult-lib --target=m68k-linux

On Fri, Aug 23, 2002 at 11:42:59AM -0400, Peter Barada wrote:
> >this is not only a gcc isssue. For m68k-linux and v4e you will not
> >only need a distinct set of libraries, but most likely also all application
> >binaries? The easiest thing to do is to configure and build glibc for
> >both targets separately.
> Yes, that is the realization that I'm coming to.  I'm not sure if I
> want to attempt playing with CFLAGS= on the glibc configure line(I
> already found out that CFLAGS has to include at least -O or glibc
> won't configure correctly), or hatchet up gcc/config/m68k/linux.h to
> make v4e the default.  

this is hairy. Seems easiest solution is to have a few shell scripts that 
invoke the real compiler with the right '-m' switch. For some programms
it does also work to say CC="m68k-linux-gcc -m68040" but it can break
badly with libtool which apparently can't cope with that.

> This will build variants for m68020 m68020/m68881 m68040 m68060
I think its not worth to do extra 68040 configuration, for libgcc,
libstdc and java it should be sufficiently similar to 68020/68881.


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