> -----Original Message----- > From: Ian Lance Taylor [mailto:i...@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 > > f...@redhat.com (Frank Ch. Eigler) writes: > > > "H.J. Lu" <hjl.to...@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
