public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "mrs at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug ada/42554] Can't build GNAT tools Date: Fri, 19 Mar 2010 10:20:00 -0000 [thread overview] Message-ID: <20100319102006.11411.qmail@sourceware.org> (raw) In-Reply-To: <bug-42554-303@http.gcc.gnu.org/bugzilla/> ------- Comment #13 from mrs at gcc dot gnu dot org 2010-03-19 10:20 ------- Subject: Bug 42554 Author: mrs Date: Fri Mar 19 10:19:52 2010 New Revision: 157563 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=157563 Log: PR ada/42554 * configure.ac: Only pass -c to ranlib for darwin9 and earlier. * configure: Regenerate. Modified: trunk/ChangeLog trunk/configure trunk/configure.ac -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=42554
next prev parent reply other threads:[~2010-03-19 10:20 UTC|newest] Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top 2009-12-30 18:25 [Bug ada/42554] New: Can't build gnatlink, gnatmake simon at pushface dot org 2009-12-30 18:27 ` [Bug ada/42554] " simon at pushface dot org 2010-01-06 22:35 ` simon at pushface dot org 2010-01-07 22:25 ` simon at pushface dot org 2010-01-31 22:58 ` simon at pushface dot org 2010-02-01 22:54 ` simon at pushface dot org 2010-02-01 22:56 ` simon at pushface dot org 2010-02-02 1:56 ` howarth at nitro dot med dot uc dot edu 2010-02-02 6:26 ` [Bug ada/42554] Can't build GNAT tools simon at pushface dot org 2010-02-02 13:11 ` simon at pushface dot org 2010-02-02 21:25 ` simon at pushface dot org 2010-02-02 22:55 ` howarth at nitro dot med dot uc dot edu 2010-02-03 21:24 ` simon at pushface dot org 2010-03-19 10:20 ` mrs at gcc dot gnu dot org [this message] 2010-05-17 12:07 ` fxcoudert at gcc dot gnu dot org [not found] <bug-42554-4@http.gcc.gnu.org/bugzilla/> 2011-06-27 20:14 ` gcc at microbizz dot nl
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=20100319102006.11411.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).