public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: "H.J. Lu" <hjl.tools@gmail.com>
To: Binutils <binutils@sourceware.org>
Cc: GDB <gdb-patches@sourceware.org>
Subject: Re: [PATCH 1/8] Add --with-system-zlib in bfd
Date: Sun, 29 Mar 2015 14:10:00 -0000	[thread overview]
Message-ID: <CAMe9rOp9RHgjnG3JpfSFXsyT4jwutoC7FWTWFzfoKEnT0GC48Q@mail.gmail.com> (raw)
In-Reply-To: <20150326155711.GA10088@gmail.com>

On Thu, Mar 26, 2015 at 8:57 AM, H.J. Lu <hjl.tools@gmail.com> wrote:
> I imported zlib from GCC.  This patch adds --with-system-zlib and remove
> --with-zlib in bfd.  OK for master?
>
> Thanks.
>
>
> H.J.
> ---
>         * Makefile.am (ZLIB): New.
>         (ZLIBINC): Likewise.
>         (AM_CFLAGS): Add $(ZLIBINC).
>         (libbfd_la_LIBADD): Add $(ZLIB).
>         * compress.c: Don't check HAVE_ZLIB_H to include <zlib.h>.
>         (decompress_contents): Don't check HAVE_ZLIB_H.
>         (decompress_contents): Likewise.
>         (bfd_compress_section_contents): Likewise.
>         (bfd_get_full_section_contents): Likewise.
>         (bfd_init_section_decompress_status): Likewise.
>         (bfd_init_section_compress_status): Likewise.
>         * configure.ac (AM_ZLIB): Removed
>         (zlibdir): New.  AC_SUBST.
>         (zlibinc): Likewise.
>         Add --with-system-zlib.
>         * Makefile.in: Regenerated.
>         * acinclude.m4: Likewise.
>         * config.in: Likewise.
>         * configure: Likewise.
>         * doc/Makefile.in: Likewise.

I will check in this patch shortly.

-- 
H.J.

  reply	other threads:[~2015-03-29 14:10 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-26 15:57 H.J. Lu
2015-03-29 14:10 ` H.J. Lu [this message]
2015-03-30 15:52   ` Steve Ellcey
2015-03-30 16:32     ` H.J. Lu
2015-03-30 16:45       ` Luis Machado
2015-03-30 16:51         ` H.J. Lu
2015-03-30 17:13           ` Steve Ellcey
2015-03-30 17:21             ` H.J. Lu
2015-03-30 17:36               ` Steve Ellcey
2015-03-30 19:33                 ` Antoine Tremblay
2015-03-30 19:37                   ` Antoine Tremblay
2015-03-31 17:13                     ` Antoine Tremblay
2015-03-31 17:16                       ` H.J. Lu
2015-03-31 17:18                         ` Antoine Tremblay
2015-03-31 18:55                           ` H.J. Lu
2015-03-31 20:16                           ` H.J. Lu
2015-04-01 12:18                             ` Antoine Tremblay
2015-04-02  3:22                             ` Bin.Cheng
2015-04-02  3:53                               ` Bin.Cheng
2015-03-30 20:19                   ` H.J. Lu
2015-03-31 12:08                     ` Antoine Tremblay
2015-03-30 18:18           ` Luis Machado
2015-03-30 17:20       ` H.J. Lu
2015-03-31  6:13 ` Mike Frysinger
2015-03-31 10:10   ` H.J. Lu
2015-03-31 10:37     ` Pedro Alves
2015-03-31 10:46       ` H.J. Lu
2015-03-31 10:53         ` Pedro Alves
2015-03-31 11:33           ` H.J. Lu
2015-03-31 11:46             ` Pedro Alves
2015-03-31 12:01               ` H.J. Lu
2015-03-31 12:15                 ` Pedro Alves
2015-03-31 13:43                   ` H.J. Lu
2015-03-31 13:46                     ` Pedro Alves
2015-03-31 16:41     ` Mike Frysinger
2015-03-31 16:56       ` H.J. Lu
2015-03-31 17:01         ` Mike Frysinger
2015-03-31 17:04           ` 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=CAMe9rOp9RHgjnG3JpfSFXsyT4jwutoC7FWTWFzfoKEnT0GC48Q@mail.gmail.com \
    --to=hjl.tools@gmail.com \
    --cc=binutils@sourceware.org \
    --cc=gdb-patches@sourceware.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).