From: Joel Brobecker <brobecker@adacore.com>
To: "H.J. Lu" <hjl.tools@gmail.com>
Cc: GDB <gdb-patches@sourceware.org>,
Tristan Gingold <gingold@adacore.com>,
Nick Clifton <nickc@redhat.com>,
Paul Koning <Paul_Koning@dell.com>,
"Joseph S. Myers" <joseph@codesourcery.com>,
Thomas Schwinge <thomas@codesourcery.com>,
Binutils <binutils@sourceware.org>
Subject: Re: RFC: Import zlib from GCC tree
Date: Thu, 19 Mar 2015 11:23:00 -0000 [thread overview]
Message-ID: <20150319112336.GA4884@adacore.com> (raw)
In-Reply-To: <CAMe9rOqQPEkvdTr8jjcy+yNaXTkTiRvceiRY_wnazRJe=rY8nQ@mail.gmail.com>
> >> I created users/hjl/zlib branch. It imported zlib into binutils-gdb tree
> >> and replaced --with-zlib with --with-system-zlib. Any feedbacks?
> >
> > I'm not sure. Wouldn't some people want to configure --without-zlib?
>
> GCC doesn't support --without-zlib nor should binutils.
> zlib is needed to implement SHF_COMPRESSED.
Generally speaking, I really don't know what to think of that.
Some people might decide that this is a feature they do not want,
in which case having support for it is just extra bloat. But,
on the other hand, zlib is probably sufficiently small that
it would not matter much. Speaking for myself, at least, I can
live with that. Just not sure about others.
Given the lack of feedback so far, I am thinking no one is strenuously
objecting. I propose we give people another week to express their
opinion, after which we can move forward. You'll need the approval
of the binutils maintainers as well, I suspect.
--
Joel
next prev parent reply other threads:[~2015-03-19 11:23 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAMe9rOp+5L0na923z1_jJQJuci=npuCQM6ktx7XG=gSOc1nZ+g@mail.gmail.com>
2015-03-14 19:31 ` Joel Brobecker
2015-03-15 15:01 ` H.J. Lu
2015-03-16 23:24 ` Joel Brobecker
2015-03-16 23:34 ` H.J. Lu
2015-03-19 11:23 ` Joel Brobecker [this message]
2015-03-23 12:33 ` H.J. Lu
2015-03-28 9:43 ` src-release broke with the zlib import Hans-Peter Nilsson
2015-03-28 13:51 ` H.J. Lu
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=20150319112336.GA4884@adacore.com \
--to=brobecker@adacore.com \
--cc=Paul_Koning@dell.com \
--cc=binutils@sourceware.org \
--cc=gdb-patches@sourceware.org \
--cc=gingold@adacore.com \
--cc=hjl.tools@gmail.com \
--cc=joseph@codesourcery.com \
--cc=nickc@redhat.com \
--cc=thomas@codesourcery.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