Your message dated Wed, 18 Jun 2025 14:56:24 -0400
with message-id <c23b567ed1f6b4eeb78c1da1a0444369183af19d.ca...@debian.org>
and subject line Re: pytorch-cuda: FTBFS: ld.lld: error: undefined reference:
std::ios_base_library_init()@GLIBCXX_3.4.32
has caused the Debian Bug report #1105066,
regarding pytorch-cuda: FTBFS: ld.lld: error: undefined reference:
std::ios_base_library_init()@GLIBCXX_3.4.32
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
1105066: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1105066
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: src:pytorch-cuda
Version: 2.6.0+dfsg-7
Severity: serious
Tags: ftbfs trixie sid
Dear maintainer:
During a rebuild of all packages in unstable, your package failed to build:
--------------------------------------------------------------------------------
[...]
[2465/2591] : && /usr/bin/cuda-g++ -Wdate-time -D_FORTIFY_SO
[too-long-redacted] urce=bin/c10_tempfile_test && :
[2466/2591] : && /usr/bin/cuda-g++ -Wdate-time -D_FORTIFY_SO
[too-long-redacted] source=bin/c10_typeid_test && :
[2467/2591] : && /usr/bin/cuda-g++ -Wdate-time -D_FORTIFY_SO
[too-long-redacted] 10_intrusive_ptr_benchmark && :
FAILED: bin/c10_intrusive_ptr_benchmark
: && /usr/bin/cuda-g++ -Wdate-time -D_FORTIFY_SOURCE=2 -g -O
[too-long-redacted] 10_intrusive_ptr_benchmark && :
ld.lld: error: undefined reference: std::ios_base_library_init()@GLIBCXX_3.4.32
>>> referenced by /usr/lib/x86_64-linux-gnu/libbenchmark.so (disallowed by
>>> --no-allow-shlib-undefined)
collect2: error: ld returned 1 exit status
[2468/2591] /usr/bin/cuda-g++ -DDNNL_EXPERIMENTAL_UKERNEL -D
[too-long-redacted] test/cpp/lazy/test_lazy_ops.cpp
ninja: build stopped: subcommand failed.
Building wheel torch-2.6.0+debian
-- Building version 2.6.0+debian
cmake -GNinja -DBLAS=Generic -DBUILD_PYTHON=True -DBUILD_SPLIT_CUDA=ON
-DBUILD_TEST=True -DCMAKE_BUILD_TYPE=RelWithDebInfo
-DCMAKE_INSTALL_PREFIX=/<<PKGBUILDDIR>>/torch
-DCMAKE_PREFIX_PATH=/usr/local/lib/python3.13/dist-packages
-DONNX_NAMESPACE=onnx -DPython_EXECUTABLE=/usr/bin/python3.13
-DTORCH_BUILD_VERSION=2.6.0+debian
-DTORCH_CUDA_ARCH_LIST=5.0;6.0;7.0;7.5;8.0;8.6;9.0+PTX -DUSE_CUDA=ON
-DUSE_CUDNN=ON -DUSE_DISTRIBUTED=ON -DUSE_FBGEMM=OFF -DUSE_GFLAGS=OFF
-DUSE_GLOG=OFF -DUSE_GLOO=ON -DUSE_ITT=OFF -DUSE_KINETO=ON
-DUSE_LLVM=/usr/lib/llvm-19 -DUSE_MAGMA=OFF -DUSE_MIOPEN=OFF -DUSE_MKLDNN=ON
-DUSE_MPI=OFF -DUSE_NNPACK=OFF -DUSE_NUMPY=True -DUSE_PYTORCH_QNNPACK=ON
-DUSE_ROCM=OFF -DUSE_SYSTEM_LIBS=ON -DUSE_SYSTEM_NCCL=ON -DUSE_TENSORPIPE=ON
-DUSE_VULKAN=1 -DUSE_XNNPACK=ON /<<PKGBUILDDIR>>
cmake --build . --target install --config RelWithDebInfo -- -j 2 -v
make[1]: *** [debian/rules:199: override_dh_auto_install] Error 1
make[1]: Leaving directory '/<<PKGBUILDDIR>>'
make: *** [debian/rules:162: binary] Error 2
dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2
--------------------------------------------------------------------------------
The above is just how the build ends and not necessarily the most relevant part.
If required, the full build log is available here:
https://people.debian.org/~sanvila/build-logs/202505/
About the archive rebuild: The build was made on virtual machines from AWS,
using sbuild and a reduced chroot with only build-essential packages.
If you could not reproduce the bug please contact me privately, as I
am willing to provide ssh access to a virtual machine where the bug is
fully reproducible.
If this is really a bug in one of the build-depends, please use
reassign and add an affects on src:pytorch-cuda, so that this is still
visible in the BTS web page for this package.
Thanks.
--- End Message ---
--- Begin Message ---
The reported issue no longer exists with CUDA 12.4.
Marking the bug as done.
On Thu, 2025-06-12 at 12:28 +0200, Santiago Vila wrote:
> Hi. nvidia version 12.4 has been uploaded for unstable today, so there
> is some chance that this will be fixed after such version propagates to
> testing.
>
> (But I've not tested building the pytorch-cuda in unstable using 12.4 yet)
>
> Thanks.
--- End Message ---
