From: "Jose E. Marchesi" <jose.marchesi@oracle.com>
To: nick.alcock@oracle.com
Cc: Tom Tromey <tom@tromey.com>,
"Jose E. Marchesi via Gdb-patches" <gdb-patches@sourceware.org>,
Simon Marchi <simark@simark.ca>,
indu.bhagat@oracle.com, elena.zannoni@oracle.com
Subject: Re: [PATCH] gdb: use libtool in GDB_AC_CHECK_BFD
Date: Thu, 10 Nov 2022 17:35:09 +0100 [thread overview]
Message-ID: <87sfiqsr7m.fsf@oracle.com> (raw)
In-Reply-To: <875yfmztd6.fsf@tromey.com> (Tom Tromey's message of "Thu, 10 Nov 2022 09:06:45 -0700")
>>>>>> "Jose" == Jose E Marchesi via Gdb-patches <gdb-patches@sourceware.org> writes:
>
> Jose> About gdb/Makefile.in... dunno, $(ZLIB) is included in CLIBS. This
> Jose> makes me think GDB uses zlib directly?
>
> Jose> If it doesn't, I think you can remove:
>
> It doesn't directly:
>
> murgatroyd. git grep 'include.*zlib.h' | grep -v ChangeLog | grep -v '^zlib/'
> bfd/compress.c:#include <zlib.h>
> binutils/readelf.c:#include <zlib.h>
> gas/compress-debug.c:#include <zlib.h>
> gold/compressed_output.cc:#include <zlib.h>
> gprofng/src/DbeJarFile.cc:#include "zlib.h"
> include/ctf-api.h:#include <zlib.h>
> libbacktrace/ztest.c:#include <zlib.h>
> libctf/ctf-open.c:#include <zlib.h>
> libctf/ctf-serialize.c:#include <zlib.h>
>
> Jose> 1) The calls to AM_ZLIB and AC_ZSTD from gdb/configure.ac.
> Jose> 2) The definition of ZLIB and ZLIBINC from gdb/Makefile.in
> Jose> 3) ../config/zlib.m4 from aclocal_m4_deps in gdb/Makefile.in
>
> ... however the use in ctf-api.h seems like it would prevent removing
> some of the configury. gdb includes this header and so it needs the
> correct -I options to find the in-tree zlib.h.
>
> I don't see why ctf-api.h needs this include, but I essentially don't
> know anything about CTF.
Nick, would it be possible to remove the include of zlib.h from
ctf-api.h? Even if libctf uses zlib, it would be good to not expose the
dependency in the API header...
next prev parent reply other threads:[~2022-11-10 16:33 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-07 19:46 Jose E. Marchesi
2022-11-10 10:02 ` Jose E. Marchesi
2022-11-10 13:50 ` Simon Marchi
2022-11-10 14:55 ` Jose E. Marchesi
2022-11-10 16:06 ` Tom Tromey
2022-11-10 16:35 ` Jose E. Marchesi [this message]
2022-11-10 17:11 ` Nick Alcock
2022-11-10 17:46 ` Simon Marchi
2022-11-11 13:17 ` Nix
2022-11-11 13:51 ` Simon Marchi
2022-11-14 13:56 ` Nick Alcock
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=87sfiqsr7m.fsf@oracle.com \
--to=jose.marchesi@oracle.com \
--cc=elena.zannoni@oracle.com \
--cc=gdb-patches@sourceware.org \
--cc=indu.bhagat@oracle.com \
--cc=nick.alcock@oracle.com \
--cc=simark@simark.ca \
--cc=tom@tromey.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).