From: Jan Beulich <jbeulich@suse.com>
To: Simon Marchi <simark@simark.ca>, Fangrui Song <maskray@google.com>
Cc: binutils@sourceware.org, gdb-patches@sourceware.org
Subject: Re: [PATCH] binutils, gdb: support zstd compressed debug sections
Date: Mon, 19 Sep 2022 11:13:58 +0200 [thread overview]
Message-ID: <56fc56b4-5e36-5225-3bc4-25b548d6116c@suse.com> (raw)
In-Reply-To: <15fe4352-79e1-acd5-5a71-fc40e19047a8@simark.ca>
On 19.09.2022 08:55, Simon Marchi via Binutils wrote:
>> diff --git a/config/zstd.m4 b/config/zstd.m4
>> new file mode 100644
>> index 00000000000..b8b3a199730
>> --- /dev/null
>> +++ b/config/zstd.m4
>> @@ -0,0 +1,12 @@
>> +AC_DEFUN([AM_ZSTD],
>> +[
>> + zstdlib=
>> + AC_ARG_WITH(system-zstd,
>> + [AS_HELP_STRING([--with-system-zstd], [use installed zstd])],
>> + if test x$with_system_zstd = xyes ; then
>> + zstdlib=-lzstd
>> + AC_DEFINE(HAVE_ZSTD_H)
>> + fi
>> + )
>> + AC_SUBST(zstdlib)
>> +])
>
> Hi Fangrui,
>
> I understand that you did this by copying zlib here. However, the only
> reason we have a --use-system-zlib is because the binutils-gdb contains
> a copy of zlib, which is used by default, and --use-system-zlib can be
> used to prefer the system version. Since we don't carry a copy of zstd
> in the tree, I don't think we need --with-system-zstd.
>
> However, since zstd ships with a .pc file, my preference would be to use
> PKG_CHECK_MODULES to have pkg-config find the right flags, and have
> --with/--without-zstd. Same as I did for the msgpack library here:
>
> https://gitlab.com/gnutools/binutils-gdb/-/commit/2952f10cd79af4645222f124f28c7928287d8113
>
> I am not a binutils maintainers though (just GDB), so in the end it's up
> to the binutils maintainers to decide and GDB will probably follow suit.
FWIW I agree with the comment.
Jan
prev parent reply other threads:[~2022-09-19 9:14 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-19 4:01 Fangrui Song
2022-09-19 6:55 ` Simon Marchi
2022-09-19 8:51 ` Fangrui Song
2022-09-19 10:54 ` Simon Marchi
2022-09-19 16:45 ` Fangrui Song
2022-09-20 1:11 ` Simon Marchi
2022-09-19 9:13 ` Jan Beulich [this message]
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=56fc56b4-5e36-5225-3bc4-25b548d6116c@suse.com \
--to=jbeulich@suse.com \
--cc=binutils@sourceware.org \
--cc=gdb-patches@sourceware.org \
--cc=maskray@google.com \
--cc=simark@simark.ca \
/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).