public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug bootstrap/53238] Bootstrap failure: error: 'pthread_mutex_timedlock' was not declared in this scope Date: Sat, 05 May 2012 18:57:00 -0000 [thread overview] Message-ID: <bug-53238-4-qpGHGtXBXL@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-53238-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53238 --- Comment #6 from Jonathan Wakely <redi at gcc dot gnu.org> 2012-05-05 18:13:57 UTC --- Created attachment 27320 --> http://gcc.gnu.org/bugzilla/attachment.cgi?id=27320 diff of regenerated configure N.B. you'll either need to run autoreconf or apply this patch to configure
next prev parent reply other threads:[~2012-05-05 18:14 UTC|newest] Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-05-04 20:11 [Bug bootstrap/53238] New: " skunk at iskunk dot org 2012-05-04 20:22 ` [Bug bootstrap/53238] " redi at gcc dot gnu.org 2012-05-04 20:34 ` skunk at iskunk dot org 2012-05-04 20:58 ` redi at gcc dot gnu.org 2012-05-05 16:21 ` skunk at iskunk dot org 2012-05-05 17:43 ` redi at gcc dot gnu.org 2012-05-05 18:57 ` redi at gcc dot gnu.org [this message] 2012-05-07 21:10 ` skunk at iskunk dot org 2012-05-08 18:44 ` skunk at iskunk dot org 2012-05-09 16:54 ` redi at gcc dot gnu.org 2012-05-12 8:35 ` skunk at iskunk dot org 2012-05-16 2:52 ` skunk at iskunk dot org 2012-05-16 3:11 ` redi at gcc dot gnu.org 2012-06-10 22:39 ` skunk at iskunk dot org 2012-07-16 21:34 ` redi at gcc dot gnu.org 2012-07-19 19:25 ` skunk at iskunk dot org 2012-07-19 21:11 ` skunk at iskunk dot org 2012-07-19 23:56 ` redi at gcc dot gnu.org 2012-07-20 17:44 ` skunk at iskunk dot org 2012-07-23 4:21 ` skunk at iskunk dot org 2012-07-23 8:12 ` redi at gcc dot gnu.org 2012-07-23 18:52 ` skunk at iskunk dot org 2015-02-06 17:33 ` dje at gcc dot gnu.org 2015-02-06 19:02 ` skunk at iskunk dot org 2021-07-18 7:19 ` pinskia at gcc dot gnu.org
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=bug-53238-4-qpGHGtXBXL@http.gcc.gnu.org/bugzilla/ \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.org \ /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).