This is the mail archive of the
libc-help@sourceware.org
mailing list for the glibc project.
Why does pthread_cancel_init() dlopen libgcc_s.so.1?
- From: "Dave Barach" <dbarach at verizon dot net>
- To: <libc-help at sourceware dot org>
- Date: Mon, 19 Oct 2009 11:41:02 -0400
- Subject: Why does pthread_cancel_init() dlopen libgcc_s.so.1?
Wonder if someone can explain why pthread_cancel_init() dlopens
libgcc_s.so.1?
At a higher level: why are some bits of the pthread implementation present
in glibc, while other bits come from libgcc?
Why would one care? When building a cross toolchain: we configure gcc w/
--enable-threads=single (so the gcc build doesn't depend on glibc), build
gcc, build glibc, then reconfigure and rebuild gcc to generate
libgcc_s.so.1.
Is there a better way to solve the interdependency between glibc and
libgcc_s when building a cross toolchain?
Thanks... Dave Barach