We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Operating System: Ubuntu 22.04 **Version / Commit SHA:**openvdb 8.1 libtbb 2021.5 CMake Version: 3.22 Compiler: gcc 11
I just moved from 20.04 to 22.04 and tried to build my app installing the same packages as before:
libtbb-dev libopenvdb-dev
But now I get this build errors:
/usr/include/openvdb/tools/Count.h:51:56: error: ‘tbb::split’ has not been declared 51 | ActiveVoxelCountOp(const ActiveVoxelCountOp&, tbb::split) { } | ^~~~~ /usr/include/openvdb/tools/Count.h:87:70: error: reference to ‘split’ is ambiguous 87 | ActiveVoxelCountBBoxOp(const ActiveVoxelCountBBoxOp& other, tbb::split)
I read in another issue of some problems between libtbb and openvdb. Is this here also the case and I have to build openvdb 8.2 from source?
The text was updated successfully, but these errors were encountered:
Hi @max-os-lg,
You are correct, 8.1 is not comaptible with TBB 2021 which seems to be the default TBB in apt for 22.04.
#1366 https://bugs.launchpad.net/ubuntu/+source/openvdb/+bug/1970108
You'll need to build openvdb yourself from source if you want to use the version of TBB provided by libtbb-dev
Sorry, something went wrong.
No branches or pull requests
Environment
Operating System: Ubuntu 22.04
**Version / Commit SHA:**openvdb 8.1 libtbb 2021.5
CMake Version: 3.22
Compiler: gcc 11
Describe the problem
I just moved from 20.04 to 22.04 and tried to build my app installing the same packages as before:
But now I get this build errors:
I read in another issue of some problems between libtbb and openvdb.
Is this here also the case and I have to build openvdb 8.2 from source?
The text was updated successfully, but these errors were encountered: