Github messages for voidlinux
 help / color / mirror / Atom feed
From: thypon <thypon@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Merged]: tbb: update to 2021.11.0.
Date: Wed, 28 Feb 2024 17:31:32 +0100	[thread overview]
Message-ID: <20240228163132.B36F224C71@inbox.vuxu.org> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-48872@inbox.vuxu.org>

[-- Attachment #1: Type: text/plain, Size: 1407 bytes --]

There's a merged pull request on the void-packages repository

tbb: update to 2021.11.0.
https://github.com/void-linux/void-packages/pull/48872

Description:
<!-- Uncomment relevant sections and delete options which are not applicable -->

#### Testing the changes
- I tested the changes in this PR: **briefly**
- Tested TBB, but have not tested the bumped packages

<!--
#### New package
- This new package conforms to the [package requirements](https://github.com/void-linux/void-packages/blob/master/CONTRIBUTING.md#package-requirements): **YES**|**NO**
-->

<!-- Note: If the build is likely to take more than 2 hours, please add ci skip tag as described in
https://github.com/void-linux/void-packages/blob/master/CONTRIBUTING.md#continuous-integration
and test at least one native build and, if supported, at least one cross build.
Ignore this section if this PR is not skipping CI.
-->

#### Local build testing
- I built this PR locally for my native architecture, x86_64-musl
- I built this PR locally for these architectures (if supported. mark crossbuilds):
  - x86_64
  - i686
  - aarch64-musl (cross)
  - armv7l (cross)
  - armv6l-musl (cross)

Tested builds for bumped packages in all the above architectures (when supported)

Fixed the build for PrusaSlicer, however it segfaults immediately: https://github.com/void-linux/void-packages/issues/46687

[ci skip]


  parent reply	other threads:[~2024-02-28 16:31 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-21 21:37 [PR PATCH] " Calandracas606
2024-02-21 21:41 ` Calandracas606
2024-02-21 21:43 ` [PR PATCH] [Updated] " Calandracas606
2024-02-21 21:44 ` thypon
2024-02-22 19:40 ` [PR REVIEW] " cinerea0
2024-02-22 19:40 ` cinerea0
2024-02-22 19:40 ` cinerea0
2024-02-22 19:40 ` cinerea0
2024-02-22 21:45 ` [PR PATCH] [Updated] " Calandracas606
2024-02-22 21:48 ` Calandracas606
2024-02-22 22:44 ` [PR REVIEW] " Calandracas606
2024-02-22 22:45 ` Calandracas606
2024-02-28 15:45 ` thypon
2024-02-28 15:48 ` cinerea0
2024-02-28 16:31 ` thypon [this message]
2024-02-29  3:02 ` [PR REVIEW] " sgn
2024-02-29  4:52 ` Calandracas606

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=20240228163132.B36F224C71@inbox.vuxu.org \
    --to=thypon@users.noreply.github.com \
    --cc=ml@inbox.vuxu.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 NNTP newsgroup(s).