[PATCH] Memory fencing problem in pthread cancellation

[Joseph S. Myers]

On Tue, 15 Jan 2013, Carlos O'Donell wrote:

> There might previously have been a bootstrapping issue in requiring
> a libgcc_s.so to link against because you can't have built all of
> the dynamic pieces of gcc?

Indeed, if you want to put libgcc_s.so.1 (or another SONAME on a few 
architectures) in DT_NEEDED, you need to do so in a way that does not 
involve any previously installed libgcc_s.so.1 (e.g., glibc could build 
its own dummy library and use that at static link time, as long as it 
doesn't get used later when running tests), so that building glibc with a 
static-only compiler continues to work and produce the same results as 
building it with a compiler with shared libgcc.

-- 
Joseph S. Myers
joseph@codesourcery.com