public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "davek at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug ada/864] --program-suffix is ignored (for ada)
Date: Sun, 26 Jul 2009 20:39:00 -0000 [thread overview]
Message-ID: <20090726203907.26574.qmail@sourceware.org> (raw)
In-Reply-To: <bug-864-655@http.gcc.gnu.org/bugzilla/>
------- Comment #17 from davek at gcc dot gnu dot org 2009-07-26 20:39 -------
(In reply to comment #15)
> Right, my change fixed gnatmake so that it would call the proper gcc (based on
> the
> previous comments on this PR), but Makefiles have never supported
> --program-suffix, so that's not even a regression.
Uh, you both focussed on the line where I mentioned in passing that the gnat
executables don't get suffixed, and missed the actual bug report: it does *not*
call the proper GCC. Regardless of whether gnatmake itself gets a suffix or
not, it should have invoked "gcc-4", not "gcc", shouldn't it?
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=864
next prev parent reply other threads:[~2009-07-26 20:39 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-864-655@http.gcc.gnu.org/bugzilla/>
2008-05-12 23:42 ` charlet at gcc dot gnu dot org
2008-05-13 13:40 ` charlet at gcc dot gnu dot org
2008-05-13 13:41 ` charlet at gcc dot gnu dot org
2008-05-29 8:57 ` charlet at gcc dot gnu dot org
2008-05-29 8:59 ` charlet at gcc dot gnu dot org
2008-05-29 9:06 ` charlet at gcc dot gnu dot org
2009-07-26 14:26 ` davek at gcc dot gnu dot org
2009-07-26 19:53 ` rguenth at gcc dot gnu dot org
2009-07-26 20:33 ` charlet at gcc dot gnu dot org
2009-07-26 20:38 ` rguenth at gcc dot gnu dot org
2009-07-26 20:39 ` davek at gcc dot gnu dot org [this message]
2009-07-26 20:44 ` rguenther at suse dot de
2009-07-26 20:57 ` davek at gcc dot gnu dot org
[not found] <bug-864-4@http.gcc.gnu.org/bugzilla/>
2011-12-07 0:43 ` davek at gcc dot gnu.org
2011-12-07 0:47 ` davek at gcc dot gnu.org
2011-12-07 12:54 ` rguenth at gcc dot gnu.org
2013-01-04 13:53 ` rguenth at gcc dot gnu.org
2013-01-07 10:15 ` rguenth at gcc dot gnu.org
2013-01-07 10:17 ` rguenth at gcc dot gnu.org
[not found] <20001121193600.864.bh@techhouse.brown.edu>
2004-03-16 17:05 ` ludovic dot brenta at insalien 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=20090726203907.26574.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: link
Be 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).