From: Geert Bosch <bosch@gnat.com>
To: Christian Cornelssen <ccorn@cs.tu-berlin.de>
Cc: Richard Kenner <kenner@vlsi1.ultra.nyu.edu>,
Gabriel Dos Reis <gdr@integrable-solutions.net>,
<gcc-bugs@gcc.gnu.org>, <gcc@gcc.gnu.org>,
Robert Dewar <dewar@gnat.com>
Subject: Re: [3.2] Can ada/6160 be cured from 3.3 or trunk?
Date: Tue, 28 Jan 2003 19:37:00 -0000 [thread overview]
Message-ID: <69B425D8-32E6-11D7-A3A7-00039344BF4A@gnat.com> (raw)
In-Reply-To: <Pine.LNX.4.33.0301281546160.5305-100000@Dachs.Bau>
On Tuesday, Jan 28, 2003, at 09:52 America/New_York, Christian
Cornelssen wrote:
> Sure? A "diff -u" on `gcc/ada/Make-lang.in' from the 3.2 and 3.3
> branches
> yields
>
> [...]
> -GNATBIND = gnatbind
> [...]
> +GNATBIND = $(STAGE_PREFIX)gnatbind -C
> [...]
This might well be the right solution. I'm testing this now on a freshly
checked out gcc-3_2-branch, using GNAT 3.13p1 as a base compiler.
Actually, I think this TN's subject was a bit misleading: the issue
is about invoking wrong gnatbind, not using a compiler that is too old.
Bootstrap will take a while. I'll report back after it finishes (or
fails)
and in case of success I'll make the fix on the branch.
-Geert
next prev parent reply other threads:[~2003-01-28 17:32 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-28 15:50 Richard Kenner
2003-01-28 16:29 ` Gabriel Dos Reis
2003-01-28 16:43 ` Christian Cornelssen
2003-01-28 19:37 ` Geert Bosch [this message]
2003-01-28 22:57 ` Gabriel Dos Reis
-- strict thread matches above, loose matches on Subject: below --
2003-01-28 23:08 Robert Dewar
2003-01-28 23:30 ` Christian Cornelssen
2003-01-31 18:48 ` Christian Cornelssen
2003-01-31 21:27 ` Geert Bosch
2003-01-28 21:39 Christian Cornelssen
2003-01-28 22:07 ` Geert Bosch
2003-01-28 16:52 Richard Kenner
2003-01-28 17:10 ` Christian Cornelssen
[not found] <Pine.LNX.4.33.0301281436270.5102-100000@Dachs.Bau>
2003-01-28 14:23 ` Gabriel Dos Reis
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=69B425D8-32E6-11D7-A3A7-00039344BF4A@gnat.com \
--to=bosch@gnat.com \
--cc=ccorn@cs.tu-berlin.de \
--cc=dewar@gnat.com \
--cc=gcc-bugs@gcc.gnu.org \
--cc=gcc@gcc.gnu.org \
--cc=gdr@integrable-solutions.net \
--cc=kenner@vlsi1.ultra.nyu.edu \
/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).