too long lines were shrinked: [74/102] /usr/bin/x86_64-pc-linux-gnu-g++ -DBOOST_IOSTREAMS_DYN_LINK -DBOOST_IOSTREAMS_NO_LIB -DOPENVDB_DLL -DOPENVDB_PRIVATE -DOPENVDB_USE_AVX -DOPENVDB_USE_DELAYED_LOADING -DOPENVDB_USE_LOG4CPLUS -DOPENVDB_USE_SSE42 -Dopenvdb_shared_EXPORTS -I/var/tmp/portage/media-gfx/openvdb-11.0.0/work/openvdb- [75/102] /usr/bin/x86_64-pc-linux-gnu-g++ -DBOOST_IOSTREAMS_DYN_LINK -DBOOST_IOSTREAMS_NO_LIB -DNANOVDB_USE_BLOSC -DNANOVDB_USE_INTRINSICS -DNANOVDB_USE_OPENVDB -DNANOVDB_USE_TBB -DNANOVDB_USE_ZIP -DOPENVDB_DLL -DOPENVDB_USE_AVX -DOPENVDB_USE_DELAYED_LOADING -DOPENVDB_USE_LOG4CPLUS -DOPENVDB_USE_SSE FAILED: nanovdb/nanovdb/examples/CMakeFiles/ex_make_custom_nanovdb.dir/ex_make_custom_nanovdb/make_custom_nanovdb.cc.o /usr/bin/x86_64-pc-linux-gnu-g++ -DBOOST_IOSTREAMS_DYN_LINK -DBOOST_IOSTREAMS_NO_LIB -DNANOVDB_USE_BLOSC -DNANOVDB_USE_INTRINSICS -DNANOVDB_USE_OPENVDB -DNANOVDB_USE_TBB -DNANOVDB_USE_ZIP -DOPENVDB_DLL -DOPENVDB_USE_AVX -DOPENVDB_USE_DELAYED_LOADING -DOPENVDB_USE_LOG4CPLUS -DOPENVDB_USE_SSE42 -I/var In file included from /var/tmp/portage/media-gfx/openvdb-11.0.0/work/openvdb-11.0.0/nanovdb/nanovdb/examples/ex_make_custom_nanovdb/make_custom_nanovdb.cc:4: /var/tmp/portage/media-gfx/openvdb-11.0.0/work/openvdb-11.0.0/nanovdb/nanovdb/../nanovdb/util/GridBuilder.h: In member function bool nanovdb::build::LeafNode<BuildT>::ValueIterator::isActive() const: /var/tmp/portage/media-gfx/openvdb-11.0.0/work/openvdb-11.0.0/nanovdb/nanovdb/../nanovdb/util/GridBuilder.h:1161:72: error: const struct nanovdb::build::LeafNode<BuildT> has no member named isActive [-Wtemplate-body] 1161 | bool isActive() const { NANOVDB_ASSERT(*this); return mParent->isActive(mPos);} | ^~~~~~~~ ------------------------------------------------------------------- This is an unstable amd64 chroot image at a tinderbox (==build bot) name: 23.0_hardened-20240816-201002 UNMASKED: Please re-assign to toolchain@ if you get a test failure in C, C++, or Fortran code which makes no sense. <sys-devel/gcc-15.0.9999:15 The attached etc.portage.tar.xz has all details. ------------------------------------------------------------------- gcc-config -l: [1] x86_64-pc-linux-gnu-15 * clang/llvm (if any): /usr/lib/llvm/18 18.1.8 Python 3.12.5 Available Ruby profiles: [1] ruby31 (with Rubygems) [2] ruby32 (with Rubygems) [3] ruby33 (with Rubygems) * Available Rust versions: [1] rust-bin-1.80.1 * The following VMs are available for generation-2: 1) Eclipse Temurin JDK 11.0.24_p8 [openjdk-bin-11] 2) Eclipse Temurin JDK 17.0.12_p7 [openjdk-bin-17] *) Eclipse Temurin JDK 21.0.4_p7 [openjdk-bin-21] 4) Eclipse Temurin JDK 8.422_p05 [openjdk-bin-8] Available Java Virtual Machines: [1] openjdk-bin-8 [2] openjdk-bin-11 [3] openjdk-bin-17 [4] openjdk-bin-21 system-vm The Glorious Glasgow Haskell Compilation System, version 9.2.8 php cli (if any): go version go1.23.0 linux/amd64 HEAD of ::gentoo commit 54452bccff418e9155e32b15b0d52699a2523caa Author: Repository mirror & CI <repomirrorci@gentoo.org> Date: Tue Aug 20 16:04:02 2024 +0000 2024-08-20 16:04:01 UTC emerge -qpvO =media-gfx/openvdb-11.0.0 [ebuild N ] media-gfx/openvdb-11.0.0 USE="abi11-compat blosc examples nanovdb zlib -abi9-compat -abi10-compat -abi12-compat -alembic -ax -cuda -doc -jpeg -numpy -openexr -png -python -static-libs -test -utils" CPU_FLAGS_X86="avx sse4_2" PYTHON_SINGLE_TARGET="python3_12 -python3_10 -python3_11"
Created attachment 900833 [details] emerge-info.txt
Created attachment 900834 [details] emerge-history.txt.xz
Created attachment 900835 [details] environment
Created attachment 900836 [details] etc.portage.tar.xz
Created attachment 900837 [details] media-gfx:openvdb-11.0.0:20240820-164218.log
Created attachment 900838 [details] qlist-info.txt.xz
Created attachment 900839 [details] temp.tar.xz
https://github.com/AcademySoftwareFoundation/openvdb/commit/930c3acb8e0c7c2f1373f3a70dc197f5d04dfe74
The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=05d3ddad7b4f20d1a0bc2931498ec5aa1d6bc3e5 commit 05d3ddad7b4f20d1a0bc2931498ec5aa1d6bc3e5 Author: Paul Zander <negril.nx+gentoo@gmail.com> AuthorDate: 2025-04-27 23:04:45 +0000 Commit: Sam James <sam@gentoo.org> CommitDate: 2025-04-27 23:39:03 +0000 media-gfx/openvdb: backport gcc-15 fixes Closes: https://bugs.gentoo.org/938253 Signed-off-by: Paul Zander <negril.nx+gentoo@gmail.com> Signed-off-by: Sam James <sam@gentoo.org> media-gfx/openvdb/Manifest | 1 + media-gfx/openvdb/openvdb-11.0.0-r1.ebuild | 16 +++++++++++++++- 2 files changed, 16 insertions(+), 1 deletion(-)
*** Bug 955027 has been marked as a duplicate of this bug. ***
hi there, on my system, blender does not compile, apparently due to this bug in openvdb. this is the openvdb build log now, after that commit. I have gcc 15.1 and of course it has a gcc 15.1 cross compile eselect gcc list [1] nvptx-none-15 * [2] x86_64-pc-linux-gnu-14 [3] x86_64-pc-linux-gnu-15 * and i have the recent cuda-sdk ^[[32m * ^[[39;49;00mPackage: media-gfx/openvdb-11.0.0-r1:0/11.0 ^[[32m * ^[[39;49;00mRepository: gentoo ^[[32m * ^[[39;49;00mMaintainer: negril.nx+gentoo@gmail.com proxy-maint@gentoo.org ^[[32m * ^[[39;49;00mUSE: abi11-compat abi_x86_64 amd64 blosc cpu_flags_x86_avx cpu_flags_x86_sse4_2 cuda elibc_glibc jpeg kernel_linux llvm_slot_15 nanovdb png python_single_target_python3_12 zlib ^[[32m * ^[[39;49;00mFEATURES: network-sandbox preserve-libs sandbox splitdebug userpriv usersandbox >>> Unpacking source... >>> Unpacking openvdb-11.0.0.tar.gz to /var/tmp/portage/media-gfx/openvdb-11.0.0-r1/work === Skipping unpack of openvdb-11.0.0-drop-obsolete-isActive-gcc15.patch >>> Source unpacked in /var/tmp/portage/media-gfx/openvdb-11.0.0-r1/work >>> Preparing source in /var/tmp/portage/media-gfx/openvdb-11.0.0-r1/work/openvdb-11.0.0 ... ^[[32m*^[[0m Applying openvdb-11.0.0-drop-obsolete-isActive-gcc15.patch ... ^[[A^[[228C ^[[34;01m[ ^[[32;01mok^[[34;01m ]^[[0m ^[[32m*^[[0m Source directory (CMAKE_USE_DIR): "/var/tmp/portage/media-gfx/openvdb-11.0.0-r1/work/openvdb-11.0.0" ^[[32m*^[[0m Build directory (BUILD_DIR): "/var/tmp/portage/media-gfx/openvdb-11.0.0-r1/work/openvdb-11.0.0_build" ^[[32m*^[[0m Applying openvdb-8.1.0-glfw-libdir.patch ... ^[[A^[[228C ^[[34;01m[ ^[[32;01mok^[[34;01m ]^[[0m ^[[32m*^[[0m Applying openvdb-9.0.0-fix-atomic.patch ... patching file nanovdb/nanovdb/CMakeLists.txt Hunk #1 succeeded at 69 with fuzz 1. patching file openvdb/openvdb/CMakeLists.txt Hunk #1 succeeded at 197 (offset -5 lines). ^[[A^[[228C ^[[34;01m[ ^[[32;01mok^[[34;01m ]^[[0m ^[[32m*^[[0m Applying openvdb-10.0.1-fix-linking-of-vdb_tool-with-OpenEXR.patch ... ^[[A^[[228C ^[[34;01m[ ^[[32;01mok^[[34;01m ]^[[0m ^[[32m*^[[0m Applying openvdb-10.0.1-log4cplus-version.patch ... ^[[A^[[228C ^[[34;01m[ ^[[32;01mok^[[34;01m ]^[[0m ^[[32m*^[[0m Applying openvdb-11.0.0-constexpr-version.patch ... ^[[A^[[228C ^[[34;01m[ ^[[32;01mok^[[34;01m ]^[[0m ^[[32m*^[[0m Applying openvdb-11.0.0-cmake_fixes.patch ... ^[[A^[[228C ^[[34;01m[ ^[[32;01mok^[[34;01m ]^[[0m >>> Source prepared. >>> Configuring source in /var/tmp/portage/media-gfx/openvdb-11.0.0-r1/work/openvdb-11.0.0 ... ^[[32m*^[[0m install: running my_src_configure __nvcc_device_query failed to call cudaLoader::cuInit(0) with error 0x130 (CUDA_ERROR_OPERATING_SYSTEM) ^[[31;01m*^[[0m ERROR: media-gfx/openvdb-11.0.0-r1::gentoo failed (configure phase): ^[[31;01m*^[[0m failed to query the native device ^[[31;01m*^[[0m ^[[31;01m*^[[0m Call stack: ^[[31;01m*^[[0m ebuild.sh, line 136: Called src_configure ^[[31;01m*^[[0m environment, line 3409: Called multibuild_foreach_variant 'my_src_configure' ^[[31;01m*^[[0m environment, line 2550: Called _multibuild_run 'my_src_configure' ^[[31;01m*^[[0m environment, line 2548: Called my_src_configure ^[[31;01m*^[[0m environment, line 2804: Called cuda_get_host_native_arch ^[[31;01m*^[[0m environment, line 1630: Called die ^[[31;01m*^[[0m The specific snippet of code: ^[[31;01m*^[[0m __nvcc_device_query || die "failed to query the native device" ^[[31;01m*^[[0m ^[[31;01m*^[[0m If you need support, post the output of `emerge --info '=media-gfx/openvdb-11.0.0-r1::gentoo'`, ^[[31;01m*^[[0m the complete build log and the output of `emerge -pqv '=media-gfx/openvdb-11.0.0-r1::gentoo'`. ^[[31;01m*^[[0m The complete build log is located at '/var/tmp/portage/media-gfx/openvdb-11.0.0-r1/temp/build.log'. ^[[31;01m*^[[0m The ebuild environment file is located at '/var/tmp/portage/media-gfx/openvdb-11.0.0-r1/temp/environment'. ^[[31;01m*^[[0m Working directory: '/var/tmp/portage/media-gfx/openvdb-11.0.0-r1/work/openvdb-11.0.0' ^[[31;01m*^[[0m S: '/var/tmp/portage/media-gfx/openvdb-11.0.0-r1/work/openvdb-11.0.0'
merge -pv nvidia-cuda-toolkit Local copy of remote index is up-to-date and will be used. These are the packages that would be merged, in order: Calculating dependencies... done! Dependency resolution took 4.39 s (backtrack: 0/20). [ebuild R ] dev-util/nvidia-cuda-toolkit-12.8.1:0/12.8.1::gentoo USE="debugger examples profiler rdma sanitizer" PYTHON_TARGETS="python3_12 -python3_10 -python3_11 -python3_13" 0 KiB Total: 1 package (1 reinstall), Size of downloads: 0 KiB So something like this ^[[32m*^[[0m Applying openvdb-11.0.0-cmake_fixes.patch ... ^[[A^[[228C ^[[34;01m[ ^[[32;01mok^[[34;01m ]^[[0m >>> Source prepared. >>> Configuring source in /var/tmp/portage/media-gfx/openvdb-11.0.0-r1/work/openvdb-11.0.0 ... ^[[32m*^[[0m install: running my_src_configure __nvcc_device_query failed to call cudaLoader::cuInit(0) with error 0x130 (CUDA_ERROR_OPERATING_SYSTEM) ^[[31;01m*^[[0m ERROR: media-gfx/openvdb-11.0.0-r1::gentoo failed (configure phase): ^[[31;01m*^[[0m failed to query the native device ^[[31;01m*^[[0m ^[[31;01m*^[[0m Call stack: ^[[31;01m*^[[0m should not happen... (media-gfx/openvdb-11.0.0-r1:0/11.0::gentoo, ebuild scheduled for merge) USE="abi11-compat blosc cuda jpeg nanovdb png zlib -abi10-compat -abi12-compat -abi9-compat -alembic -ax -doc -examples -numpy -openexr -python -static-libs -test -utils" ABI_X86="(64)" CPU_FLAGS_X86="avx sse4_2" LLVM_SLOT="15" PYTHON_SINGLE_TARGET="python3_12 -python3_10 -python3_11" conflicts with
Ah, I see someone noticed this already: https://bugs.gentoo.org/955021 But that means then that blender can not be compiled with cuda really until openvdb is fixed..
That's fixed now (but it belonged in a separate bug).
