public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Pedro Alves <palves@redhat.com>
To: "H.J. Lu" <hjl.tools@gmail.com>
Cc: Binutils <binutils@sourceware.org>, GDB <gdb-patches@sourceware.org>
Subject: Re: [PATCH 1/8] Add --with-system-zlib in bfd
Date: Tue, 31 Mar 2015 13:46:00 -0000	[thread overview]
Message-ID: <551AA52A.9000000@redhat.com> (raw)
In-Reply-To: <CAMe9rOqvAFcqRWLY3WuYh9dOH-NFDJLNhTpz3=pXtn=QsS-GJA@mail.gmail.com>

On 03/31/2015 02:43 PM, H.J. Lu wrote:
> On Tue, Mar 31, 2015 at 5:15 AM, Pedro Alves <palves@redhat.com> wrote:
>> On 03/31/2015 01:01 PM, H.J. Lu wrote:
>>>>>
>>>>>
>>>>> They're all the same.  Just a couple doesn't define zlibdir or zlibinc.
>>> If zlib.m4 is changed, I will use it and GCC can also use it. But I
>>> don't know if other packages use zlib.m4.
>>
>> Please change it.  Packages not in the tree can replace zlib.m4 with
>> something else if they need it, or adjust to the new body, and thus
>> end up consistent with the rest of the toolchain.
>>
>> "git blame" shows that zlib.m4 was invented exactly to make
>> sure bfd/gdb use the same zlib switches and checks:
>>
>>  https://sourceware.org/ml/binutils/2009-10/msg00600.html
>>
> 
> These are changes I checked in.

Thank you.

-- 
Pedro Alves

  reply	other threads:[~2015-03-31 13:46 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
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 [this message]
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=551AA52A.9000000@redhat.com \
    --to=palves@redhat.com \
    --cc=binutils@sourceware.org \
    --cc=gdb-patches@sourceware.org \
    --cc=hjl.tools@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).