From: Alexandre Oliva <aoliva@redhat.com>
To: Nathanael Nerode <neroden@twcny.rr.com>
Cc: gcc-patches@gcc.gnu.org, binutils@sources.redhat.com,
gdb-patches@sources.redhat.com
Subject: Re: (toplevel) Don't look for unprefixed tools unless they're appropriate
Date: Sat, 28 Dec 2002 01:01:00 -0000 [thread overview]
Message-ID: <or65te8qmg.fsf@free.redhat.lsd.ic.unicamp.br> (raw)
In-Reply-To: <20021228072212.GA7409@doctormoo>
On Dec 28, 2002, Nathanael Nerode <neroden@twcny.rr.com> wrote:
> Tested on i686-pc-linux-gnu with a Canadian cross. Now if the
> prefixed tools can't be found (and the unprefixed tools are incorrect),
> the tool values default to blank, which will cause entirely different
> errors. (Heh.)
Hmm... I don't quite like a blank default. I'd much rather default
to <host/target>-<tool>, since this at least gives the user the
opportunity to adjust PATH after configure, and gives more of an idea
of what's going on.
> * configure.in: Don't default to unprefixed tools unless
> the native tools will work.
> * configure: Regenerate.
Nevertheless, this patch is correct, and approved. The change in the
default should be addressed as a separate patch.
Thanks,
--
Alexandre Oliva Enjoy Guarana', see http://www.ic.unicamp.br/~oliva/
Red Hat GCC Developer aoliva@{redhat.com, gcc.gnu.org}
CS PhD student at IC-Unicamp oliva@{lsd.ic.unicamp.br, gnu.org}
Free Software Evangelist Professional serial bug killer
next prev parent reply other threads:[~2002-12-28 9:00 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 [this message]
2002-12-28 7:48 ` Doug Evans
2002-12-28 9:58 ` Alexandre Oliva
2002-12-28 8:17 ` Doug Evans
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=or65te8qmg.fsf@free.redhat.lsd.ic.unicamp.br \
--to=aoliva@redhat.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