From: Daniel Jacobowitz <drow@mvista.com>
To: Alexandre Oliva <aoliva@redhat.com>
Cc: gcc-patches@gcc.gnu.org, binutils@sources.redhat.com,
gdb-patches@sources.redhat.com
Subject: Re: Unify --with-sysroot defaults
Date: Thu, 20 Feb 2003 15:22:00 -0000 [thread overview]
Message-ID: <20030220152243.GB29197@nevyn.them.org> (raw)
In-Reply-To: <or1y23fexa.fsf@free.redhat.lsd.ic.unicamp.br>
On Thu, Feb 20, 2003 at 07:02:25AM -0300, Alexandre Oliva wrote:
> Currently, GCC accepts --with-sysroot without an argument, whereas ld
> and gdb don't. Also, GCC's default sysroot is not considered
> relocatable, even though the whole point of picking that default was
> such that it was. This patch arranges for all three tools to use the
> same relocatable default. Ok to install in ld and gdb? (I'll install
> it in gcc when I get approval for the others).
Fine for GDB too. Should we be moving any of this logic to the top level?
--
Daniel Jacobowitz
MontaVista Software Debian GNU/Linux Developer
prev parent reply other threads:[~2003-02-20 15:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-20 10:05 Alexandre Oliva
2003-02-20 14:50 ` Nick Clifton
2003-02-20 15:22 ` Daniel Jacobowitz [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=20030220152243.GB29197@nevyn.them.org \
--to=drow@mvista.com \
--cc=aoliva@redhat.com \
--cc=binutils@sources.redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=gdb-patches@sources.redhat.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