From: Thomas Fitzsimmons <email@example.com>
To: Mark Wielaard <firstname.lastname@example.org>
Cc: "Martin Liška" <email@example.com>,
"Dan Horák" <firstname.lastname@example.org>
Subject: Re: xxhash devel on buildbot workers
Date: Thu, 07 Jul 2022 11:04:49 -0400 [thread overview]
Message-ID: <email@example.com> (raw)
In-Reply-To: <firstname.lastname@example.org> (Mark Wielaard's message of "Thu, 07 Jul 2022 15:36:47 +0200")
Mark Wielaard <email@example.com> writes:
> On Thu, 2022-07-07 at 14:29 +0200, Martin Liška wrote:
>> I've just pushed the revision. Can you please install xxhash-devel
>> (libxxhash-dev for Debian)
>> for all non-container builders?
> Installed on centos-x86_64, debian-arm64, debian-armhf and debian-i386.
> Dan, could you install xxhash-devel on lfedora1 marist (s390x) and the
> fit.vutbr.cz (ppc64le) server?
> Tom, could you install libxxhash-dev on the debian-ppc64 server
> BTW. Note that on debian-oldstable (the arm64 and armhf boards)
> xxhash.h tries to include xxhash.c with XXH_INLINE_ALL, which doesn't
> work. We'll probably need a configure check or simply upgrade to a
> newer version.
I installed libxxhash-dev:ppc64 0.8.1-1. According to comments in
xxhash.h, this version is new enough that it does not host the
implementation inside xxhash.c.
next prev parent reply other threads:[~2022-07-07 15:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <firstname.lastname@example.org>
[not found] ` <20220625194440.GA16194@gnu.wildebeest.org>
[not found] ` <email@example.com>
[not found] ` <firstname.lastname@example.org>
[not found] ` <email@example.com>
[not found] ` <firstname.lastname@example.org>
[not found] ` <email@example.com>
2022-07-07 13:36 ` xxhash devel on buildbot workers (Was: [PATCH] Use xxHash hashing algorithm) Mark Wielaard
2022-07-07 15:04 ` Thomas Fitzsimmons [this message]
2022-07-11 7:48 ` Dan Horák
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).