OpenVDB-11 uses slightly different API for nanovdb which is not taken into account in blender-4.0.2. This was patched in 4.0.1, but the patch has not been included in 4.0.2. The patch in upstream differs from what was in 4.0.1 and it is probably only targeted for 4.1, but it applies cleanly to 4.0.2 too. Upstream patch https://projects.blender.org/blender/blender/commit/bbb7e7a6d57f0b24d3b7374fb3747baf0d128d24 fixes the issue. Reproducible: Always Steps to Reproduce: 1. USE="nanovdb openvdb tbb openexr" emerge =blender-4.0.2 (only nanovdb is relevant here, rest included for verbosity from REQUIRED_USE) Actual Results: Build errors to /var/tmp/portage/media-gfx/blender-4.0.2/work/blender-4.0.2/intern/cycles/scene/image_vdb.cpp: In member function ‘bool ccl::ToNanoOp::operator()(const openvdb::v11_0::GridBase::ConstPtr&)’: /var/tmp/portage/media-gfx/blender-4.0.2/work/blender-4.0.2/intern/cycles/scene/image_vdb.cpp:58:33: error: ‘openToNanoVDB’ is not a member of ‘nanovdb’ Expected Results: Successful build. USE=-nanovdb is a workaround without other modifications. Adding the patch to /etc/portage/patches/media-gfx/blender-4.0.2/ is a temporary solution for nanovdb.
Created attachment 889206 [details] build.log without patch using openvdb-11.0.0, USE=nanovdb
Created attachment 889207 [details, diff] Patch from upstream for openvdb-11 with nanovdb ( https://projects.blender.org/blender/blender/commit/bbb7e7a6d57f0b24d3b7374fb3747baf0d128d24 )
*** This bug has been marked as a duplicate of bug 925534 ***
