public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "ghazi at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug bootstrap/42424] [4.5 Regression] in-tree GMP/MPFR/MPC bootstrap fails Date: Thu, 07 Jan 2010 21:58:00 -0000 [thread overview] Message-ID: <20100107215840.16587.qmail@sourceware.org> (raw) In-Reply-To: <bug-42424-17110@http.gcc.gnu.org/bugzilla/> ------- Comment #9 from ghazi at gcc dot gnu dot org 2010-01-07 21:58 ------- Subject: Bug 42424 Author: ghazi Date: Thu Jan 7 21:58:23 2010 New Revision: 155712 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=155712 Log: PR bootstrap/42424 * configure.ac: Include libtool m4 files. (_LT_CHECK_OBJDIR): Call it. (extra_mpc_mpfr_configure_flags, extra_mpc_gmp_configure_flags, gmplibs, ppllibs, clooglibs): Use $lt_cv_objdir. * configure: Regenerate. Modified: trunk/ChangeLog trunk/configure trunk/configure.ac -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=42424
next prev parent reply other threads:[~2010-01-07 21:58 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2009-12-18 8:38 [Bug bootstrap/42424] New: " developer at sandoe-acoustics dot co dot uk 2010-01-02 16:24 ` [Bug bootstrap/42424] " ghazi at gcc dot gnu dot org 2010-01-02 16:41 ` developer at sandoe-acoustics dot co dot uk 2010-01-02 19:53 ` fxcoudert at gcc dot gnu dot org 2010-01-03 11:15 ` rguenth at gcc dot gnu dot org 2010-01-03 11:17 ` [Bug bootstrap/42424] [4.5 Regression] " rguenth at gcc dot gnu dot org 2010-01-03 15:31 ` ghazi at gcc dot gnu dot org 2010-01-06 23:26 ` ghazi at gcc dot gnu dot org 2010-01-06 23:50 ` fxcoudert at gcc dot gnu dot org 2010-01-07 21:58 ` ghazi at gcc dot gnu dot org [this message] 2010-01-08 12:57 ` rguenth at gcc dot gnu dot 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=20100107215840.16587.qmail@sourceware.org \ --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).