This is the mail archive of the
mailing list for the GDB project.
Re: RFC: Add zlib source to src CVS resposity
- From: Ian Lance Taylor <iant at google dot com>
- To: fche at redhat dot com (Frank Ch. Eigler)
- Cc: "H.J. Lu" <hjl dot tools at gmail dot com>, Binutils <binutils at sourceware dot org>, GCC Development <gcc at gcc dot gnu dot org>, GDB <gdb at sourceware dot org>
- Date: Sun, 31 Oct 2010 11:42:29 -0700
- Subject: Re: RFC: Add zlib source to src CVS resposity
- References: <AANLkTikYSxV51_452Wuqox6mQ3_QwNjzNkBgV=NzKk4f__16997.email@example.com> <firstname.lastname@example.org>
email@example.com (Frank Ch. Eigler) writes:
> "H.J. Lu" <firstname.lastname@example.org> writes:
>> [...] By default, the in-tree zlib is used. If you configure
>> binutis using --with-system-zlib, system zlib will be used. [...]
> Can you summarize what modern platforms lack a system zlib, and what
> justifies using the proposed in-tree copy by default?
This is a good point. We need zlib in the gcc repository because we
build it for the target, but this issue does not arise in the src
repository. So this becomes a question for the binutils maintainers: do
the binutils want to be self-contained, or do they want to follow the
path of gcc and require additional libraries to be installed before a
build can succeed?