public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "charlet at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug ada/14435] gnatchop cannot use the compiled compiler in Ada's testsuite because of changed GCC_EXEC_PREFIX semantics
Date: Tue, 16 Mar 2004 14:13:00 -0000 [thread overview]
Message-ID: <20040316141329.30914.qmail@sources.redhat.com> (raw)
In-Reply-To: <20040304214646.14435.hjl@lucon.org>
------- Additional Comments From charlet at gcc dot gnu dot org 2004-03-16 14:13 -------
Fixing the incorrect summary line.
Arno
--
What |Removed |Added
----------------------------------------------------------------------------
Summary|Ada's testsuite does not use|gnatchop cannot use the
|the compiled compiler |compiled compiler in Ada's
| |testsuite because of changed
| |GCC_EXEC_PREFIX semantics
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=14435
next prev parent reply other threads:[~2004-03-16 14:13 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-04 21:46 [Bug ada/14435] New: Ada testsuite doesn't use the newly compiler hjl at lucon dot org
2004-03-05 0:13 ` [Bug ada/14435] " charlet at gcc dot gnu dot org
2004-03-05 1:47 ` hjl at lucon dot org
2004-03-05 8:34 ` [Bug driver/14435] [3.4 regression] GCC_EXEC_PREFIX does not work as expected charlet at gcc dot gnu dot org
2004-03-16 1:54 ` [Bug ada/14435] Ada's testsuite does not use the compiled compiler pinskia at gcc dot gnu dot org
2004-03-16 8:43 ` charlet at act-europe dot fr
2004-03-16 14:13 ` charlet at gcc dot gnu dot org [this message]
2005-05-17 11:58 ` [Bug ada/14435] gnatchop cannot use the compiled compiler in Ada's testsuite because of changed GCC_EXEC_PREFIX semantics charlet at gcc dot gnu dot org
[not found] <bug-14435-682@http.gcc.gnu.org/bugzilla/>
2006-01-22 14:47 ` hjl at lucon dot org
2006-01-24 13:43 ` hjl at lucon dot org
2006-01-24 14:10 ` hjl at lucon dot org
2006-01-24 14:10 ` hjl at lucon 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=20040316141329.30914.qmail@sources.redhat.com \
--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).