Re: work for glibc 2.2.5-14
On Sun, Aug 11, 2002 at 11:11:51PM -0400, Jack Howarth wrote:
>
>
> Daniel,
> Ok. I re-read you message and follow it now. The problem
> with using the versioning fixup if it doesn't go into
> gcc 3.2 is that the sister patch required for glibc is unlikely
> to go into glibc-2-2-branch either so we will have to add
> both in by hand. I'm not sure what happens if you use the
> first generation patch for libgcc-compat with Franz's gcc 3.2
> version symbol fixup. I haven't really tried that one yet.
> As I said, I never have seen any breakage under a gcc 3.1.1
> built glibc with the first generation libgcc-compat patch so
> I'm not too worried either way.
> Jack
Jack,
You've hit on exactly my concern. Both the GCC and glibc patches
represent ABI changes; I don't want Debian to deliberately import
ABI-changing patches which have been rejected by the community.
> ps The new version of the libgcc-compat patch is attached.
> Note the new libgcc-compat will require the next binutils
> post 2.13.90.0.3 which resolves a bug in binutils this patch
> tickles.
Thanks. I've been following the binutils side with some interest.
--
Daniel Jacobowitz
MontaVista Software Debian GNU/Linux Developer
Reply to: