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 10:53:00 -0000 [thread overview]
Message-ID: <551A7CB1.4060101@redhat.com> (raw)
In-Reply-To: <CAMe9rOomwTtSiSS1K1zQpGvpArqZLDfOyapDVvC=Yfy5m3zBEg@mail.gmail.com>
On 03/31/2015 11:46 AM, H.J. Lu wrote:
> On Tue, Mar 31, 2015 at 3:37 AM, Pedro Alves <palves@redhat.com> wrote:
>> On 03/31/2015 11:10 AM, H.J. Lu wrote:
>>> On Mon, Mar 30, 2015 at 11:13 PM, Mike Frysinger <vapier@gentoo.org> wrote:
>>>> On 26 Mar 2015 08:57, H.J. Lu wrote:
>>>>> --- a/bfd/configure.ac
>>>>> +++ b/bfd/configure.ac
>>>>>
>>>>> -# Link in zlib if we can. This allows us to read compressed debug sections.
>>>>> -# This is used only by compress.c.
>>>>> -AM_ZLIB
>>>>> +# Use the system's zlib library.
>>>>> +zlibdir=-L../zlib
>>>>> +zlibinc="-I\$(srcdir)/../zlib"
>>>>> +AC_ARG_WITH(system-zlib,
>>>>> +[AS_HELP_STRING([--with-system-zlib], [use installed libz])],
>>>>> +zlibdir=
>>>>> +zlibinc=
>>>>> +)
>>>>
>>>> this is wrong. the 3rd arg is whether the option was specified, not that the
>>>> option was disabled. you need to check $withval is equal to "no" (or not equal
>>>> to "yes").
>>>> -mike
>>>
>>> That is what gcc/configure.ac has and it works for me.
>>>
>>>
>>
>> Why are we patching every tool's configury instead of tweaking
>> config/zlib.m4 (where AM_ZLIB is from)? We go from a single
>> place to edit, to the same configure bits spread around the
>> tree. Seems like a step backwards.
>>
>
> Replace AM_ZLIB in configure.ac isn't complete. I also needed to change
Never said it was complete.
>
> * Makefile.am (ZLIB): New.
> (ZLIBINC): Likewise.
> (AM_CFLAGS): Add $(ZLIBINC).
> (libbfd_la_LIBADD): Add $(ZLIB).
>
> It is better for Makefile.am to use what configure.ac defines
That's orthogonal. How configure.ac defines what Makefile.am
consumes is the issue. That can either be through a shared macro,
which makes sure all tools have the exact same command line option
(like AM_ZLIB), or you manually put the same configure.ac bits
everywhere.
Thanks,
Pedro Alves
next prev parent reply other threads:[~2015-03-31 10:53 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 [this message]
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=551A7CB1.4060101@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