This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
RE: RFC: Add zlib source to src CVS resposity
- From: "Weddington, Eric" <Eric dot Weddington at atmel dot com>
- To: "Ian Lance Taylor" <iant at google dot com>, "Frank Ch. Eigler" <fche at redhat dot com>
- 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 13:53:34 -0600
- Subject: RE: RFC: Add zlib source to src CVS resposity
- References: <mcr1v762oh6.fsf@google.com>
> -----Original Message-----
> From: Ian Lance Taylor [mailto:iant@google.com]
> Sent: Sunday, October 31, 2010 12:42 PM
> To: Frank Ch. Eigler
> Cc: H.J. Lu; Binutils; GCC Development; GDB
> Subject: Re: RFC: Add zlib source to src CVS resposity
>
> fche@redhat.com (Frank Ch. Eigler) writes:
>
> > "H.J. Lu" <hjl.tools@gmail.com> 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?
Typically, building for host=mingw runs into all sorts of non-standard stuff. I don't know for sure, but I highly doubt that there is a system zlib on that platform. For gcc dependencies, it just so happens that gmp, mpfr, and mpc build just fine for mingw.
Eric Weddington