public inbox for git-commits@fedoraproject.org
help / color / mirror / Atom feed
From: Ali Erdinc Koroglu <ali.koroglu@oss.qualcomm.com>
To: git-commits@fedoraproject.org
Subject: [rpms/openvdb] rawhide: FTBSFS fix (rhbz#2504382)
Date: Thu, 06 Aug 2026 10:36:49 GMT	[thread overview]
Message-ID: <178601260989.1.14559536815164917112.rpms-openvdb-c26113783fb1@fedoraproject.org> (raw)

A new commit has been pushed.

Repo   : rpms/openvdb
Branch : rawhide
Commit : c26113783fb132412395e840a3f9c3912a0a40e1
Author : Ali Erdinc Koroglu <ali.koroglu@oss.qualcomm.com>
Date   : 2026-08-06T13:36:36+03:00
Stats  : +30/-0 in 2 file(s)
URL    : https://src.fedoraproject.org/rpms/openvdb/c/c26113783fb132412395e840a3f9c3912a0a40e1?branch=rawhide

Log:
FTBSFS fix (rhbz#2504382)

---
diff --git a/2200.patch b/2200.patch
new file mode 100644
index 0000000..9d9d3a7
--- /dev/null
+++ b/2200.patch
@@ -0,0 +1,27 @@
+diff --git a/openvdb/openvdb/thread/Threading.h b/openvdb/openvdb/thread/Threading.h
+index b339a85ecc..f1433341f9 100644
+--- a/openvdb/openvdb/thread/Threading.h
++++ b/openvdb/openvdb/thread/Threading.h
+@@ -14,14 +14,16 @@
+ #endif
+ 
+ 
+-/// @note tbb/blocked_range.h is the ONLY include that persists from TBB 2020
+-///   to TBB 2021 that itself includes the TBB specific version header files.
+-///   In TBB 2020, the version header was called tbb/stddef.h. In 2021, it's
+-///   called tbb/version.h. We include tbb/blocked_range.h here to indirectly
+-///   access the version defines in a consistent way so that downstream
+-///   software doesn't need to provide compile time defines.
+ #include <tbb/blocked_range.h>
+ #include <tbb/task.h>
++/// @note tbb/task_arena.h is the ONLY include that persists from TBB 2020
++///   to TBB 2021 to TBB 2023 that itself includes the TBB specific version
++///   header files.
++///   In TBB 2020, the version header was called tbb/stddef.h. In 2021+, it's
++///   called tbb/version.h. We include tbb/task_arena.h here to indirectly
++///   access the version defines in a consistent way so that downstream
++///   software doesn't need to provide compile time defines.
++#include <tbb/task_arena.h>
+ #include <tbb/task_group.h>
+ 
+ namespace openvdb {

diff --git a/openvdb.spec b/openvdb.spec
index a8e4c7a..49759ae 100644
--- a/openvdb.spec
+++ b/openvdb.spec
@@ -31,6 +31,9 @@ URL:            https://www.openvdb.org/
 
 Source0:        https://github.com/AcademySoftwareFoundation/%{name}/archive/v%{version}/%{name}-%{version}.tar.gz
 
+# https://github.com/AcademySoftwareFoundation/openvdb/pull/2200
+Patch0:		2200.patch
+
 # OpenVDB no longer builds on 32bits with latest TBB due to OOM.
 ExcludeArch:    %{ix86}
 

                 reply	other threads:[~2026-08-06 10:36 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=178601260989.1.14559536815164917112.rpms-openvdb-c26113783fb1@fedoraproject.org \
    --to=ali.koroglu@oss.qualcomm.com \
    --cc=git-commits@fedoraproject.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