From: Paolo Bonzini <bonzini@gnu.org>
To: Ian Lance Taylor <iant@google.com>
Cc: "H.J. Lu" <hjl.tools@gmail.com>,
"Frank Ch. Eigler" <fche@redhat.com>,
Binutils <binutils@sourceware.org>,
GCC Development <gcc@gcc.gnu.org>, GDB <gdb@sourceware.org>
Subject: Re: RFC: Add zlib source to src CVS resposity
Date: Tue, 02 Nov 2010 10:46:00 -0000 [thread overview]
Message-ID: <4CCFEBE0.1010605@gnu.org> (raw)
In-Reply-To: <mcrk4ky18i6.fsf@google.com>
On 10/31/2010 08:12 PM, Ian Lance Taylor wrote:
> I assume that the reason we do that for intl is because it has complex
> interactions with the rest of the C library, so using the wrong intl
> library will cause confusing behaviour when the LC_ environment
> variables are set. That case does not arise for zlib. I think that if
> we do ship zlib with the binutils, we might as well always build it
> rather than using complex configure tests.
I think it's also for historical reasons. Nowadays most GNU utilities
are not shipping with a copy intl anymore.
Paolo
next prev parent reply other threads:[~2010-11-02 10:46 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
2010-11-09 14:19 ` Mike Frysinger
2010-11-02 10:46 ` Paolo Bonzini [this message]
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=4CCFEBE0.1010605@gnu.org \
--to=bonzini@gnu.org \
--cc=binutils@sourceware.org \
--cc=fche@redhat.com \
--cc=gcc@gcc.gnu.org \
--cc=gdb@sourceware.org \
--cc=hjl.tools@gmail.com \
--cc=iant@google.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).