Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Paolo Bonzini <paolo.bonzini@lu.unisi.ch>
To: DJ Delorie <dj@redhat.com>,
	 binutils@sources.redhat.com,  gdb-patches@sources.redhat.com,
	GCC Patches <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH] Fix in-srcdir build of gcc
Date: Sat, 26 Feb 2005 19:36:00 -0000	[thread overview]
Message-ID: <42203256.6040108@lu.unisi.ch> (raw)
In-Reply-To: <200502251943.j1PJhnxo031954@greed.delorie.com>

> As I am a proponent of "principle of least surprise"

I am too.  Unfortunately this patch on one hand makes ./configure work 
for gcc, on the other hand it makes it more "surprising" for 
binutils/gdb.  I am especially concerned about gdb, because of the two 
it is the one that is most likely to be built by casual users doing 
"./configure && make".

In-srcdir toplevel bootstrap definitely won't work without a patch such 
as this, because it wants to symlink or rename directories (e.g. 
stage2-gcc is linked to gcc, and stage1-gcc is linked to prev-gcc).  But 
maybe for the non-bootstrap case (and for gcc), it is enough on systems 
that support symlinks to symlink the current directory to the host 
directory.  This would be better for the "principle of least surprise".

(Another remark on the changes to target libraries: newlib and winsup 
are not affected because they do not special host tools, like fastjar 
for libjava, and neither do they need to access tm.h in the gcc 
directory, like libobjc).

Paolo


  reply	other threads:[~2005-02-26  8:25 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
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 [this message]
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=42203256.6040108@lu.unisi.ch \
    --to=paolo.bonzini@lu.unisi.ch \
    --cc=binutils@sources.redhat.com \
    --cc=dj@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