From: Matthias Klose <doko@ubuntu.com>
To: NightStrike <nightstrike@gmail.com>
Cc: Jeff Law <law@redhat.com>, GCC Patches <gcc-patches@gcc.gnu.org>,
gdb-patches@sourceware.org,
binutils <binutils@sourceware.org>,
Iain Buclaw <ibuclaw@gdcproject.org>,
Johannes Pfau <johannespfau@gmail.com>
Subject: Re: [patch] update zlib to the 1.2.10 release.
Date: Sun, 22 Jan 2017 18:42:00 -0000 [thread overview]
Message-ID: <d80f9723-968a-add6-02a2-fd4f8bef7893@ubuntu.com> (raw)
In-Reply-To: <CAF1jjLuVE3WWVXHWYj+Xbau-h8ohzroTSiSL0iC2BV99PHjGjg@mail.gmail.com>
On 22.01.2017 19:12, NightStrike wrote:
> On Sun, Jan 22, 2017 at 1:00 PM, Matthias Klose <doko@ubuntu.com> wrote:
>> NightStrike proposed to revert to the 1.2.8 release until zlib stabilizes again;
>> I'm open for that, but didn't want to stay with the 1.2.10 release.
>
> I don't recall making that proposal. I thought I just suggested that
> since modern zlib now supports having a separate build and source
> directory (at least according to the December changelog: "Allow
> building zlib outside of the source directory"), you should check to
> see if the gcc build system had any hacks to accomplish the same thing
> that could now be removed.
sorry for wrongly citing you. Please could you make the removal of zlib a goal
for GCC 8? I may be a bit biased trying to keep the "ongoing" d/gdc merge alive
(libgphobos requiring a target zlib).
Matthias
next prev parent reply other threads:[~2017-01-22 18:42 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-05 14:45 Matthias Klose
2017-01-12 21:17 ` Jeff Law
2017-01-12 21:27 ` Matthias Klose
2017-01-12 21:38 ` Jeff Law
2017-01-12 21:39 ` Jeff Law
2017-01-13 12:14 ` Matthias Klose
2017-01-22 18:01 ` Matthias Klose
2017-01-22 18:12 ` NightStrike
2017-01-22 18:42 ` Matthias Klose [this message]
2017-01-23 22:57 ` Iain Buclaw
2017-01-23 4:09 ` Joel Brobecker
2017-01-23 9:10 ` Matthias Klose
2017-01-23 16:01 ` Nick Clifton
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=d80f9723-968a-add6-02a2-fd4f8bef7893@ubuntu.com \
--to=doko@ubuntu.com \
--cc=binutils@sourceware.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=ibuclaw@gdcproject.org \
--cc=johannespfau@gmail.com \
--cc=law@redhat.com \
--cc=nightstrike@gmail.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).