From: Ian Lance Taylor <iant@google.com>
To: Jerry Quinn <jlquinn@optonline.net>
Cc: "gcc\@gcc.gnu.org" <gcc@gcc.gnu.org>
Subject: Re: [gcc-in-cxx] zlib?
Date: Thu, 16 Jul 2009 02:08:00 -0000 [thread overview]
Message-ID: <m3ocrl753a.fsf@google.com> (raw)
In-Reply-To: <1247708793.4098.365.camel@cerberus.qb5.org> (Jerry Quinn's message of "Wed\, 15 Jul 2009 21\:46\:33 -0400")
Jerry Quinn <jlquinn@optonline.net> writes:
> Hi. I started looking at what it would take to convert zlib to build
> with c++.
The zlib library in gcc is actually a copy of upstream sources, so I
don't think it would be a good idea to make this change. We should stay
as close to the upstream source as possible.
Ian
next prev parent reply other threads:[~2009-07-16 2:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-16 1:46 Jerry Quinn
2009-07-16 2:08 ` Ian Lance Taylor [this message]
2009-07-16 2:25 ` Jerry Quinn
2009-07-16 3:25 ` Ian Lance Taylor
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=m3ocrl753a.fsf@google.com \
--to=iant@google.com \
--cc=gcc@gcc.gnu.org \
--cc=jlquinn@optonline.net \
/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).