From: kenner@vlsi1.ultra.nyu.edu (Richard Kenner)
To: gdr@integrable-solutions.net
Cc: gcc-bugs@gcc.gnu.org, gcc@gcc.gnu.org
Subject: Re: [3.2] Can ada/6160 be cured from 3.3 or trunk?
Date: Tue, 28 Jan 2003 15:50:00 -0000 [thread overview]
Message-ID: <10301281422.AA14183@vlsi1.ultra.nyu.edu> (raw)
It would be helpful if you (GNAT folks) could investigate this issue.
Fundamentally, it boils down to the following: In the command invocation
gnatbind -I. [args]
gnatbind gets resolved to whatever is found in $PATH
It is *supposed* to get resolved to $PATH when it is invoked in that way.
next reply other threads:[~2003-01-28 14:19 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-28 15:50 Richard Kenner [this message]
2003-01-28 16:29 ` Gabriel Dos Reis
2003-01-28 16:43 ` Christian Cornelssen
2003-01-28 19:37 ` Geert Bosch
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=10301281422.AA14183@vlsi1.ultra.nyu.edu \
--to=kenner@vlsi1.ultra.nyu.edu \
--cc=gcc-bugs@gcc.gnu.org \
--cc=gcc@gcc.gnu.org \
--cc=gdr@integrable-solutions.net \
/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).