public inbox for elfutils@sourceware.org
 help / color / mirror / Atom feed
From: "Martin Liška" <mliska@suse.cz>
To: Mark Wielaard <mark@klomp.org>
Cc: Mark Wielaard <aegon@wildebeest.org>, elfutils-devel@sourceware.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: <57b03cfc-a50a-026d-bbaf-fd05b85fa1f8@suse.cz> (raw)
In-Reply-To: <Y6OY4lpJ5RYXrC1m@wildebeest.org>

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:
>> https://github.com/facebook/zstd/commit/d7d89513d6a21
>>
>> and so it's present in zstd since 1.4.0. Can we somehow specify library version
>> in configure.ac?
> 

Hi Mark.

> 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
> libcurl.

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?

Thanks,
Martin

> 
> Cheers,
> 
> Mark


  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

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=57b03cfc-a50a-026d-bbaf-fd05b85fa1f8@suse.cz \
    --to=mliska@suse.cz \
    --cc=aegon@wildebeest.org \
    --cc=elfutils-devel@sourceware.org \
    --cc=mark@klomp.org \
    /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).