From: Paolo Bonzini <bonzini@gnu.org>
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: Thu, 31 Mar 2011 07:46:00 -0000 [thread overview]
Message-ID: <4D943146.7000409@gnu.org> (raw)
In-Reply-To: <Pine.LNX.4.64.1103301502310.20285@digraph.polyomino.org.uk>
On 03/30/2011 05:15 PM, Joseph S. Myers wrote:
> On Tue, 29 Mar 2011, Joseph S. Myers wrote:
>
>> Specifically, I propose removal of all support for building: ash autoconf
>> automake bash byacc bzip2 diff dosutils fileutils findutils find gawk
>> gettext gnuserv gzip hello indent libiconv libtool make mmalloc patch perl
>> prms rcs release recode sed send-pr shellutils tar textutils time uudecode
>> wdiff zip expect guile target-gperf target-examples target-qthreads. See
>> <http://gcc.gnu.org/ml/gcc-patches/2011-03/msg01674.html> and followups
>> regarding reasons to keep a few packages in my original list that aren't
>> in the list above.
>
> There's been push-back on libiconv and expect.
I still think expect has no reason to stay in the toplevel (not any more
than tcl or tk).
dejagnu is another story, and there's good reasons for leaving libiconv
as well.
> 2'. If the combination of directories present in the source tree would not
> build and install anything for the host or target (other than host
> libraries such as libiberty) then there should be an error at configure or
> build time. For example, a GCC source tree should not quietly build
> nothing because GCC isn't supported for the target; a binutils+gdb tree
> should not quietly build nothing for lack of BFD support, although it
> might build only a subset of binutils if ld and gdb aren't supported.
Agreed.
Paolo
prev parent reply other threads:[~2011-03-31 7:46 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
2011-03-31 12:09 ` Joseph S. Myers
2011-03-31 7:46 ` Paolo Bonzini [this message]
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=4D943146.7000409@gnu.org \
--to=bonzini@gnu.org \
--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