From: "Weddington, Eric" <Eric.Weddington@atmel.com>
To: "Ian Lance Taylor" <iant@google.com>,
"Frank Ch. Eigler" <fche@redhat.com>
Cc: "H.J. Lu" <hjl.tools@gmail.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: Sun, 31 Oct 2010 19:54:00 -0000 [thread overview]
Message-ID: <258DDD1F44B6ED4AAFD4370847CF58D50D9CAE11@csomb01.corp.atmel.com> (raw)
In-Reply-To: <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
next prev parent reply other threads:[~2010-10-31 19:54 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
2010-10-31 19:54 ` Weddington, Eric [this message]
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=258DDD1F44B6ED4AAFD4370847CF58D50D9CAE11@csomb01.corp.atmel.com \
--to=eric.weddington@atmel.com \
--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).