From: Ian Lance Taylor <iant@google.com>
To: Nick Clifton <nickc@redhat.com>
Cc: "H.J. Lu" <hjl.tools@gmail.com>,
GCC Development <gcc@gcc.gnu.org>,
Binutils <binutils@sourceware.org>,
GDB <gdb@sourceware.org>
Subject: Re: RFC: Add zlib source to src CVS resposity
Date: Tue, 02 Nov 2010 13:22:00 -0000 [thread overview]
Message-ID: <mcrpqunx3lb.fsf@google.com> (raw)
In-Reply-To: <4CCFC979.1060605@redhat.com> (Nick Clifton's message of "Tue, 02 Nov 2010 08:19:05 +0000")
Nick Clifton <nickc@redhat.com> writes:
> Right - this decision has been made. We are not going to include
> zlib the in the binutils sources.
>
> Thanks for suggesting the idea and working on the patch, but in the
> end it was just not a path we wanted to go down.
I think the next decision is whether to require the host system to have
zlib, much as gcc requires the host system to have gmp, mpfr, and mpc.
Ian
next prev parent reply other threads:[~2010-11-02 13:22 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <AANLkTikYSxV51_452Wuqox6mQ3_QwNjzNkBgV=NzKk4f__16997.3676828251$1288473196$gmane$org@mail.gmail.com>
2010-10-30 21:37 ` Frank Ch. Eigler
2010-10-30 22:28 ` H.J. Lu
2010-10-31 18:42 ` Ian Lance Taylor
2010-10-31 18:58 ` H.J. Lu
2010-10-31 19:13 ` Ian Lance Taylor
2010-11-01 17:13 ` Nick Clifton
2010-11-01 17:19 ` Daniel Jacobowitz
2010-11-01 23:56 ` Alan Modra
2010-11-02 1:03 ` Christopher Faylor
2010-11-02 8:19 ` Nick Clifton
2010-11-02 13:22 ` Ian Lance Taylor [this message]
2010-11-09 14:19 ` Mike Frysinger
2010-11-02 10:46 ` Paolo Bonzini
2010-10-31 19:54 ` Weddington, Eric
2010-10-30 21:12 H.J. Lu
2010-10-30 22:19 ` John Reiser
2010-11-01 17:21 ` Nick Clifton
2010-11-01 17:23 ` Nathan Froyd
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=mcrpqunx3lb.fsf@google.com \
--to=iant@google.com \
--cc=binutils@sourceware.org \
--cc=gcc@gcc.gnu.org \
--cc=gdb@sourceware.org \
--cc=hjl.tools@gmail.com \
--cc=nickc@redhat.com \
/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).