This is the mail archive of the
mailing list for the GCC project.
Re: Building glibc for a mult-lib --target=m68k-linux
- From: Peter Barada <pbarada at mail dot wm dot sps dot mot dot com>
- To: howarth at bromo dot med dot uc dot edu
- Cc: gcc at gcc dot gnu dot org, Peter dot Barada at motorola dot com
- Date: Thu, 22 Aug 2002 15:23:40 -0400
- Subject: Re: Building glibc for a mult-lib --target=m68k-linux
- References: <200208221917.PAA40818@bromo.msbb.uc.edu>
> Which version of gcc are you using to build glibc? Keep in
>mind that with gcc >= 3.1, symbols in libgcc went .hidden. This
>may cause you breakage of old binaries when you install the
>gcc >= 3.1 built glibc. If you are staying at gcc < 3.1 it
>is not an issue. Someone on the m68k arch will need to
>determine if there is a problem with the libgcc symbols on your
>arch and if a sysdeps/m68k/libgcc-compat.c needs to be created.
>Jakub's description of this process is appended below. If you
>explore this issue on m68k, please share your findings...
Well, this is not the problem I'm trying to solve. In fact it won't
be a problem for me since the compiler properly places libgcc.a in the
appropriate places so -m<chip> will correctly select libgcc.a
My problem is that with a multi-lib'd compiler, glibc will only build
a *single* library set, and that is for the compiler with out *any* -m
I want to change that so I can have a compiler generate linux
executables for any of coldfire v4e, 68020, 68040, 68060, etc.
Peter Barada Peter.Barada@motorola.com
Wizard 781-852-2768 (direct)
WaveMark Solutions(wholly owned by Motorola) 781-270-0193 (fax)