Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Alexandre Oliva <aoliva@redhat.com>
To: neroden@twcny.rr.com (Nathanael Nerode)
Cc: gcc-patches@gcc.gnu.org, paolo.bonzini@lu.unisi.ch,
	binutils@sources.redhat.com, gdb-patches@sources.redhat.com,
	dj@delorie.com
Subject: Re: PR/17383: fix gcc in-srcdir build (take 2)
Date: Sun, 27 Feb 2005 08:23:00 -0000	[thread overview]
Message-ID: <ory8daoh1h.fsf@livre.redhat.lsd.ic.unicamp.br> (raw)
In-Reply-To: <20050226193558.GA5098@twcny.rr.com>

On Feb 26, 2005, neroden@twcny.rr.com (Nathanael Nerode) wrote:

> I've been wanting to do this for yonks.  Approved for mainline, unless DJ or
> Alex objects.  Give them a day or two.

DJ has objections to the change, unfortunately.  Personally, I don't
have any problem with this change: it will only affect the ./configure
case, that has long been recommended against, and even then, will only
make a difference for someone for whom the change would actually make
some difference, e.g., not someone who's only half-mindlessly building
and installing the package.  If you need to enter some sub-package
build-for-host directory, you'll probably be able to figure out what's
the right thing to do.  If you have scripts to automate some of these
steps, then you probably do this often enough that you probably don't
want to pollute your source tree with builds and already follow the
recommended procedure to build out of the source tree.  So, I'd
approve this change if it wasn't for DJ's objection.

DJ, given my arguments above, would you be willing to withdraw your
objection?

Any comments for binutils or GDB folks?  Does anyone object to moving
the directories in which we build tools for the host to a host subdir
when srcdir=.?

-- 
Alexandre Oliva             http://www.ic.unicamp.br/~oliva/
Red Hat Compiler Engineer   aoliva@{redhat.com, gcc.gnu.org}
Free Software Evangelist  oliva@{lsd.ic.unicamp.br, gnu.org}


  reply	other threads:[~2005-02-27  2:47 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-27  0:36 Nathanael Nerode
2005-02-27  8:23 ` Alexandre Oliva [this message]
2005-02-27 15:46   ` DJ Delorie
2005-02-28  4:29   ` Paolo Bonzini
2005-02-28  9:35 ` Paolo Bonzini
  -- strict thread matches above, loose matches on Subject: below --
2005-02-27  0:27 Paolo Bonzini
2005-02-28 17:20 ` Nick Clifton
2005-03-01 15:17 ` Mike Stump
2005-03-01 23:02   ` Mark Mitchell

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=ory8daoh1h.fsf@livre.redhat.lsd.ic.unicamp.br \
    --to=aoliva@redhat.com \
    --cc=binutils@sources.redhat.com \
    --cc=dj@delorie.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=gdb-patches@sources.redhat.com \
    --cc=neroden@twcny.rr.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