Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Paolo Bonzini <bonzini@gnu.org>
To: "Joseph S. Myers" <joseph@codesourcery.com>
Cc: DJ Delorie <dj@redhat.com>,
	gcc@gcc.gnu.org, binutils@sourceware.org,  gdb@sourceware.org,
	newlib@sourceware.org
Subject: Re: On the toplevel configure and build system
Date: Thu, 31 Mar 2011 07:44:00 -0000	[thread overview]
Message-ID: <4D9430CF.8020809@gnu.org> (raw)
In-Reply-To: <Pine.LNX.4.64.1103301546450.20285@digraph.polyomino.org.uk>

On 03/30/2011 05:54 PM, Joseph S. Myers wrote:
> Thanks.  My inclination is to say that this should be considered an
> independent tool in its own repository, as something not required in the
> build of any of the other tools.  More specifically, utils/mep and
> utils/wince look like independent tools each of which would better go in
> its own toplevel directory (mep-integrator, cesetup) (and would each go in
> an independent repository based on the shared toplevel, since they use
> libiberty), while utils/spu appears to have no toplevel dependencies and
> so should be completely independent, possibly without toplevel support for
> building it.  Since utils/spu and utils/wince have no non-build-system
> changes since 2000, I'd be inclined to say we should declare those two
> subdirectories dead and run "cvs rm" on them - people wanting to resurrect
> them can always extract the data from CVS later.  (And I still think
> utils/mep should move to its own toplevel directory.)

No, these tools _are_ built after all.

However, moving them to a new toplevel directory and getting rid of 
utils would be a good thing.

Paolo


  reply	other threads:[~2011-03-31  7:44 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
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 [this message]
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=4D9430CF.8020809@gnu.org \
    --to=bonzini@gnu.org \
    --cc=binutils@sourceware.org \
    --cc=dj@redhat.com \
    --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