From: Doug Evans <dje@transmeta.com>
To: Nathanael Nerode <neroden@twcny.rr.com>
Cc: gcc-patches@gcc.gnu.org, binutils@sources.redhat.com,
gdb-patches@sources.redhat.com
Subject: (toplevel) Don't look for unprefixed tools unless they're appropriate
Date: Sat, 28 Dec 2002 08:17:00 -0000 [thread overview]
Message-ID: <15885.51112.736635.958996@casey.transmeta.com> (raw)
In-Reply-To: <20021228072212.GA7409@doctormoo>
Nathanael Nerode writes:
> I'd rather have them default "correctly", but that's somewhat less
> trivial, and it's really only useful for people who 'configure',
> relocate, and then 'make', which doesn't work anyway.
What do you mean by "relocate"?
prev parent reply other threads:[~2002-12-28 15:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-27 23:29 Nathanael Nerode
2002-12-28 1:01 ` Alexandre Oliva
2002-12-28 7:48 ` Doug Evans
2002-12-28 9:58 ` Alexandre Oliva
2002-12-28 8:17 ` Doug Evans [this message]
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=15885.51112.736635.958996@casey.transmeta.com \
--to=dje@transmeta.com \
--cc=binutils@sources.redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=gdb-patches@sources.redhat.com \
--cc=neroden@twcny.rr.com \
/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