glibc-2.13 branch slightly broken
Carlos O'Donell
carlos@codesourcery.com
Wed Jul 13 17:58:00 GMT 2011
On 7/13/2011 1:51 AM, Mike Frysinger wrote:
> the glibc-2.13 branch has this commit that was made after the 2.13 tag:
> commit 968dad0ab1f367a087ff4ad503b511dd0c565adc
> Author: Ulrich Drepper <drepper@gmail.com>
> Subject: Fix ordering of DSO constructors and destructors.
>
> unfortunately, this breaks quite a few apps and needs the follow up fix:
> 6b1e7d1992cd89032df431c0e0d1418b97e57cd8
>
> so on the off chance people are still adding to the glibc-2.13 branch, this
> would be one to cherry pick otherwise glibc-2.13.1 is going to be broken out
> of the box :/.
> -mike
Mike,
Thanks, I had not noticed that. I've kicked off a reg test build and I'll
look at the commit and see if it can be included as-is without any modification.
I'm worried about introducing a patch of this complexity to a stable 2.13 branch.
The right solution might be to backout 968dad0ab1f367a087ff4ad503b511dd0c565adc.
Cheers,
Carlos.
--
Carlos O'Donell
Mentor Graphics / CodeSourcery
carlos@codesourcery.com
+1 (613) 963 1026
More information about the Libc-alpha
mailing list