Building glibc for a mult-lib --target=m68k-linux

[Richard Zidlicky]

On Thu, Aug 22, 2002 at 03:23:40PM -0400, Peter Barada wrote:
> 
> >    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
> switches.

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.

For m68k-linux I am thinking about multi-libing some gcc libraries.
libgcc needs 68020/060 variants to avoid the emulation 32x32->64 mul/div 
instructions on the 68060. 
I assume those insn's aren't used at all in libstdc++ so there is no need 
to multilib that, but how about the java libs?


Richard