From: "Ludovic Courtès" <ludo@gnu.org>
To: Simon South <simon@simonsouth.net>
Cc: 58757-done@debbugs.gnu.org
Subject: bug#58757: [PATCH staging] gnu: tbb: Update to 2021.6.0.
Date: Fri, 18 Nov 2022 15:14:25 +0100 [thread overview]
Message-ID: <874juwbb9a.fsf@gnu.org> (raw)
In-Reply-To: <cover.1666611894.git.simon@simonsouth.net> (Simon South's message of "Mon, 24 Oct 2022 08:13:57 -0400")
Hi Simon,
Simon South <simon@simonsouth.net> skribis:
> This patch updates TBB ("Thread Building Blocks") to version 2021.6.0.
>
> It also removes a now-obsolete patch that was added temporarily to allow
> building on AArch64.[0]
>
> I've tested this against the staging branch on x86_64-linux and aarch64-linux
> and everything seems okay.
>
> - On x86_64-linux, I've rebuilt without issue all 406 dependent packages
> reported by "guix refresh --list-dependent tbb" except for
> python-dolfin-adjoint, r-mlr3ordinal and shogun, but these do not appear to
> be new failures.[1]
>
> - On aarch64-linux, of tbb's immediate dependents[2] nlopt, octave, openvdb,
> salmon and suitesparse build without issue. The remainder (or their own
> dependencies) fail but none appear to be new failures.[3]
>
> As usual, building the full set of dependents would require packages (like
> the Haskell compiler) that either are not yet available for AArch64 or are
> not feasible to build on the hobbyist boards I have available.
Thanks for testing it thoroughly.
I figured applying it on current ‘master’ (time has passed…) wasn’t
unreasonable given the number of dependents. Unfortunately
<https://qa.guix.gnu.org/issue/58757> didn’t pick it up but I confirmed
that it still builds and passes tests on x86_64-linux.
> gnu: tbb: Update to 2021.6.0.
Applied, thanks!
Ludo’.
prev parent reply other threads:[~2022-11-18 14:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-24 12:13 [bug#58757] [PATCH staging] gnu: tbb: Update to 2021.6.0 Simon South
2022-10-24 12:19 ` Simon South
2022-11-18 14:14 ` Ludovic Courtès [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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=874juwbb9a.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=58757-done@debbugs.gnu.org \
--cc=simon@simonsouth.net \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
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).