public inbox for java-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Matthias Klose <doko@ubuntu.com>
To: Joel Brobecker <brobecker@adacore.com>
Cc: GCC Patches <gcc-patches@gcc.gnu.org>,
	       GCJ-patches <java-patches@gcc.gnu.org>,
	gdb-patches@sourceware.org,
	       binutils <binutils@sourceware.org>
Subject: Re: update zlib to 1.2.8
Date: Mon, 23 Nov 2015 20:29:00 -0000	[thread overview]
Message-ID: <5653770B.9030204@ubuntu.com> (raw)
In-Reply-To: <20151123181303.GG3377@adacore.com>

On 23.11.2015 19:13, Joel Brobecker wrote:
>> In GCC zlib is only used for libjava; for binutils and gdb it is used when
>> building without --with-system-zlib.  This just updates zlib from 1.2.7 to
>> 1.2.8 (released in 2013).  Applies cleanly, libjava still builds and doesn't
>> show any regressions in the testsuite.  Ok to apply (even if we already are
>> in stage3)?
>
>> +2015-11-23  Matthias Klose  <doko@ubuntu.com>
>> +
>> +       * Imported zlib 1.2.8; merged local changes.
>
> Should not be a problem for GDB, since we're not near branching time.
>
> Out of curiosity, what prompted this update? Just to be in sync with
> the latest? Or was there an actual bug that you hit which 1.2.8 fixes?

No, just a packaging issue with somebody mentioning a static binutils build. 
That's when I saw the outdated version.

Now updated in the GCC VCS.

Matthias

  reply	other threads:[~2015-11-23 20:29 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-23  4:37 Matthias Klose
2015-11-23  9:44 ` Andrew Haley
2015-11-23 17:33 ` Jeff Law
2015-11-23 18:13 ` Joel Brobecker
2015-11-23 20:29   ` Matthias Klose [this message]
2015-11-24 14:39     ` Joel Brobecker

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=5653770B.9030204@ubuntu.com \
    --to=doko@ubuntu.com \
    --cc=binutils@sourceware.org \
    --cc=brobecker@adacore.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=gdb-patches@sourceware.org \
    --cc=java-patches@gcc.gnu.org \
    /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).