unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: Simon South <simon@simonsouth.net>
To: 53724@debbugs.gnu.org
Subject: [bug#53724] [PATCH staging 0/2] gnu: tbb: Fix build on AArch64; update to 2021.5.0.
Date: Wed,  2 Feb 2022 09:41:00 -0500	[thread overview]
Message-ID: <cover.1643812145.git.simon@simonsouth.net> (raw)

These patches

- Allow the tbb package to build on AArch64 by backporting an upstream commit
  that prevents one of the test cases from failing on that platform[0], and

- Update tbb itself to 2021.5.0.

On x86-64 the updated package and its 320 dependents build for me without any
new failures: only dealii-openmpi, python-dolfin-adjoint, python-vedo and
shogun fail, as they all do presently on the staging branch.

On AArch64 the updated package now builds fine and I'm in the (lengthy)
process of checking its dependencies, though an unrelated build failure in
ceres-solver and the lack of a Haskell compiler limit how far this will go
anyway.

[0] See https://github.com/oneapi-src/oneTBB/issues/687

--
Simon South
simon@simonsouth.net


Simon South (2):
  gnu: tbb: Fix test on AArch64.
  gnu: tbb: Update to 2021.5.0.

 gnu/local.mk                                  |  1 +
 .../patches/tbb-fix-test-on-aarch64.patch     | 35 +++++++++++++++++++
 gnu/packages/tbb.scm                          |  8 +++--
 3 files changed, 42 insertions(+), 2 deletions(-)
 create mode 100644 gnu/packages/patches/tbb-fix-test-on-aarch64.patch


base-commit: 1a5302435ff0d2822b823f5a6fe01faa7a85c629
-- 
2.34.0





             reply	other threads:[~2022-02-02 16:00 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-02 14:41 Simon South [this message]
2022-02-02 14:41 ` [bug#53722] [PATCH staging 1/2] gnu: tbb: Fix test on AArch64 Simon South
2022-02-02 14:47 ` [bug#53724] [PATCH staging 2/2] gnu: tbb: Update to 2021.5.0 Simon South
2022-02-05  0:15 ` bug#53724: [PATCH staging 0/2] gnu: tbb: Fix build on AArch64; update " Ludovic Courtès

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=cover.1643812145.git.simon@simonsouth.net \
    --to=simon@simonsouth.net \
    --cc=53724@debbugs.gnu.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.
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).