Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: DJ Delorie <dj@redhat.com>
To: "Joseph S. Myers" <joseph@codesourcery.com>
Cc: gcc@gcc.gnu.org, binutils@sourceware.org, gdb@sourceware.org,
	       newlib@sourceware.org
Subject: Re: On the toplevel configure and build system
Date: Tue, 29 Mar 2011 22:28:00 -0000	[thread overview]
Message-ID: <201103292228.p2TMSAPB006048@greed.delorie.com> (raw)
In-Reply-To: <Pine.LNX.4.64.1103292059260.2595@digraph.polyomino.org.uk>	(joseph@codesourcery.com)


> 2. If you put directories from the GCC repository into your build, you 
> should expect GCC and its libraries to be built; toplevel should not 
> disable GCC on the grounds that GCC does not support a given target.  

I disagree.  We have a single combined gcc+binutils+etc internal tree
that's used for many targets; some support gcc, some do not.  I added
another "don't build gcc for this" just last week.

> If in future the src repository is split up into separate repositories for 
> different projects, this principle will apply in a more fine-grained way - 

I see no reason to stop people from building in a combined source tree
for multiple targets, and expecting it to work.


  reply	other threads:[~2011-03-29 22:28 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-29 21:52 Joseph S. Myers
2011-03-29 22:28 ` DJ Delorie [this message]
2011-03-29 23:29   ` Joseph S. Myers
2011-03-29 23:41   ` Frank Ch. Eigler
2011-03-29 23:48     ` DJ Delorie
2011-03-29 23:52     ` Joseph S. Myers
2011-03-29 22:50 ` Geoffrey Keating
2011-03-30  0:07 ` Ian Lance Taylor
2011-03-29 23:45   ` Joseph S. Myers
2011-03-30 13:37 ` Tom Tromey
2011-03-30 15:16 ` Joseph S. Myers
2011-03-30 15:34   ` DJ Delorie
2011-03-30 15:54     ` Joseph S. Myers
2011-03-31  7:44       ` Paolo Bonzini
2011-03-31 12:09         ` Joseph S. Myers
2011-03-31  7:46   ` 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=201103292228.p2TMSAPB006048@greed.delorie.com \
    --to=dj@redhat.com \
    --cc=binutils@sourceware.org \
    --cc=gcc@gcc.gnu.org \
    --cc=gdb@sourceware.org \
    --cc=joseph@codesourcery.com \
    --cc=newlib@sourceware.org \
    /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