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

>> I guess I could do that for a single configuration, but I'm still
>> trying to figure out if glibc can deal with multi-lib like newlib
>> does.  If so then I could with one build create *all* of the glibc
>> variants, one for each mutil-lib that the compiler supports.
>It can't.

Ok, so it can't.  Bummer.

What's the best way to add --target=coldfire-linux or
--target=m68k-linux-coldfire to gcc-3.2 which would be the same as
m68k-linux, but use gcc/config/m68k/cf-linux.h instead of
gcc/config/m68k/linux.h?  I'm asking since I have to munge
gcc/config/m68k/linux.h to build for ColdFire.... 

>> And you thought it already took a while to build glibc :-)  Imagine what
>> its like building 5 times as many libraries (m86020, m68020/m68881,
>> m68040, m68060, mcfv4e).
>... and that's why it doesn't :)

Actually gcc doesn't multilib m68k-linux so glibc(if it supported
multilib) would only build one anyway.  In my case I want to build
two, one for m68020-040 and mcfv4e. Of course it could be extended to
all the *possible* m68k-linux targets... 

Peter Barada                         
Wizard                                         781-852-2768 (direct)
WaveMark Solutions(wholly owned by Motorola)   781-270-0193 (fax)

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