From: Daniel Jacobowitz <drow@false.org>
To: Paolo Bonzini <paolo.bonzini@lu.unisi.ch>
Cc: binutils@sources.redhat.com, gdb-patches@sources.redhat.com,
gcc-patches@sources.redhat.com
Subject: Re: [PATCH] Fix in-srcdir build of gcc
Date: Fri, 25 Feb 2005 16:34:00 -0000 [thread overview]
Message-ID: <20050225155806.GA17653@nevyn.them.org> (raw)
In-Reply-To: <421F4992.3030000@lu.unisi.ch>
On Fri, Feb 25, 2005 at 04:51:46PM +0100, Paolo Bonzini wrote:
> This patch is a "definitive" solution to the problem of building gcc
> in-srcdir. It builds host modules out of srcdir always, so that they do
> not conflict with the configuration of build or target modules. For an
> out-of-srcdir build, this does not change anything, but when --srcdir=.
> gcc will be configured to for example host-i686-pc-linux-gnu/gcc, ld
> will be configured to for example host-i686-pc-linux-gnu/ld, etc.
>
> While this can be even expected for gcc, which anyway is almost always
> built out-of-srcdir, it may violate the "principle of least surprise"
> for binutils or gdb. In that case, --srcdir=. is ok. That's why I am
> posting to all three lists.
>
> The patch requires some changes in target libraries to be able to find
> the newly-built gcc, but this is not necessary in src packages.
Did you try newlib or winsup?
--
Daniel Jacobowitz
CodeSourcery, LLC
next prev parent reply other threads:[~2005-02-25 15:58 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-25 16:12 Paolo Bonzini
2005-02-25 16:34 ` Daniel Jacobowitz [this message]
2005-02-25 20:34 ` Paolo Bonzini
2005-02-25 19:44 ` Joseph S. Myers
2005-02-25 21:22 ` DJ Delorie
2005-02-26 19:36 ` Paolo Bonzini
2005-02-27 0:23 ` Paolo Bonzini
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=20050225155806.GA17653@nevyn.them.org \
--to=drow@false.org \
--cc=binutils@sources.redhat.com \
--cc=gcc-patches@sources.redhat.com \
--cc=gdb-patches@sources.redhat.com \
--cc=paolo.bonzini@lu.unisi.ch \
/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