From: "Martin Liška" <email@example.com>
To: Mark Wielaard <firstname.lastname@example.org>
Cc: Mark Wielaard <email@example.com>, firstname.lastname@example.org
Subject: Re: ☠ Buildbot (GNU Toolchain): elfutils-try-debian-armhf - failed compile (failure) (users/marxin/try-zstd-support-v2)
Date: Thu, 22 Dec 2022 10:09:49 +0100 [thread overview]
Message-ID: <email@example.com> (raw)
On 12/22/22 00:38, Mark Wielaard wrote:
> Hi Martin,
> On Wed, Dec 21, 2022 at 07:29:19PM +0100, Martin Liška wrote:
>>> What goes wrong is that this debian old stable arm setup has libzstd
>>> containing a ZSTD_compressStream2 symbol...
>>> 40: 0000d349 264 FUNC GLOBAL DEFAULT 11 ZSTD_compressStream2
>>> But the zstd.h header doesn't expose it...
>> Yeah, that's their way of how to move an API from "staging" into a stable state.
>> It was changed in:
>> and so it's present in zstd since 1.4.0. Can we somehow specify library version
>> in configure.ac?
> It isn't as nice, but since there seems to be a pkgconfig libzstd.pc
> you could use PKG_CHECK_MODULES. See for example how we check for
I can see it, however, it not easily addable to eu_ZIPLIB function :/ I must confess,
this autoconf machinery is always something that makes me crazy :)
Do you have an elegant way how to handle it?
next prev parent reply other threads:[~2022-12-22 9:09 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20221221111547.74C4C385B50B@sourceware.org>
2022-12-21 14:20 ` Martin Liška
2022-12-21 14:42 ` Mark Wielaard
2022-12-21 14:54 ` Frank Ch. Eigler
2022-12-21 15:21 ` Mark Wielaard
2022-12-21 18:29 ` Martin Liška
2022-12-21 23:38 ` Mark Wielaard
2022-12-22 9:09 ` Martin Liška [this message]
2022-12-22 18:17 ` Mark Wielaard
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:
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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).