From: Ian Lance Taylor <iant@google.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 23:33:00 -0000 [thread overview]
Message-ID: <mcr7hbh33kh.fsf@google.com> (raw)
In-Reply-To: <Pine.LNX.4.64.1103292059260.2595@digraph.polyomino.org.uk> (Joseph S. Myers's message of "Tue, 29 Mar 2011 21:52:16 +0000 (UTC)")
"Joseph S. Myers" <joseph@codesourcery.com> writes:
> 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.
The expect program is used by dejagnu, and I believe it will be used
when running tests if both dejagnu and expect are in the source tree.
At least, it used to work that way. Everything else looks OK to me.
Ian
next prev parent reply other threads:[~2011-03-29 23:33 UTC|newest]
Thread overview: 17+ 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-29 23:33 ` Ian Lance Taylor [this message]
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 7:46 ` Paolo Bonzini
2011-03-31 12:20 ` Joseph S. Myers
2011-03-31 7:50 ` 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=mcr7hbh33kh.fsf@google.com \
--to=iant@google.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).