public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "others1 at pervalidus dot net" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sources.redhat.com Subject: [Bug nptl/11682] undefined reference to `__condvar_cleanup' from 2.3.5 to 2.12 Date: Wed, 09 Jun 2010 18:50:00 -0000 [thread overview] Message-ID: <20100609185015.23909.qmail@sourceware.org> (raw) In-Reply-To: <20100609022334.11682.others1@pervalidus.net> ------- Additional Comments From others1 at pervalidus dot net 2010-06-09 18:50 ------- Andreas Jaeger reported it in 2005 - http://sourceware.org/ml/libc-alpha/2005-07/msg00045.html My GCC was compiled agaist glibc 2.3.5. I thought that was fixed. Here, what I did is -have-ssp = no +have-ssp = yes in config.make. Anyway, I still don't know why 2.12 fails. Do you think I should try compiling it after 2.11.2 is installed ? BTW, dozens of nptl tests failed with 2.11.2. I guess, because 2.3.5 was installed. -- http://sourceware.org/bugzilla/show_bug.cgi?id=11682 ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
next prev parent reply other threads:[~2010-06-09 18:50 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2010-06-09 2:23 [Bug nptl/11682] New: " others1 at pervalidus dot net 2010-06-09 9:32 ` [Bug nptl/11682] " pasky at suse dot cz 2010-06-09 14:34 ` others1 at pervalidus dot net 2010-06-09 18:02 ` pasky at suse dot cz 2010-06-09 18:50 ` others1 at pervalidus dot net [this message] [not found] <bug-11682-131@http.sourceware.org/bugzilla/> 2014-06-30 17:51 ` fweimer at redhat dot com
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=20100609185015.23909.qmail@sourceware.org \ --to=sourceware-bugzilla@sourceware.org \ --cc=glibc-bugs@sources.redhat.com \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).