This is the mail archive of the
libc-help@sourceware.org
mailing list for the glibc project.
AW: bug with PI mutex and static linking
- From: "Warlich, Christof" <christof dot warlich at siemens dot com>
- To: "Carlos O'Donell" <carlos at systemhalted dot org>
- Cc: "Sudler, Simon" <simon dot sudler at siemens dot com>, "libc-help at sourceware dot org" <libc-help at sourceware dot org>, "Hartmann, Wolfgang" <wolfgang dot hartmann at siemens dot com>
- Date: Fri, 12 Feb 2016 07:27:13 +0000
- Subject: AW: bug with PI mutex and static linking
- Authentication-results: sourceware.org; auth=none
- References: <6D83E89737156549AEA25EF9ED712C5D18EDE2 at DEFTHW99EK1MSX dot ww902 dot siemens dot net> <CAE2sS1gnYZDc0uwx+W2xY+f7SH=i1cFF7o==EUyF9SNXWWqHzA at mail dot gmail dot com> <6D83E89737156549AEA25EF9ED712C5D18EF29 at DEFTHW99EK1MSX dot ww902 dot siemens dot net> <CAE2sS1hz=woxZCb43+TtPHK=V_qOkTSqM3r+VO1Ua4EOEqzcAQ at mail dot gmail dot com>
Carlos wrote:
> $GCC -r -nostdlib -o libpthread.o -Wl,--whole-archive ./libpthread.a
> rm libpthread.a
> ar rcs libpthread.a libpthread.o
Again, thanks a lot for this: It perfectly fixed the problem!
Looks like static builds do more and more become second class citizens only:
I assume that static builds are not covered during GLIBC regression testing?
Lesson learned on our side: If we seriously want to continue to support static
builds, we have to run the GLIBC test suite for static builds ourselves.