[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#1089271: pytorch-cuda: FTBFS with make 4.4.1



Package: src:pytorch-cuda
Version: 2.4.1-4
User: debian-qa@lists.debian.org
Usertags: make-4.4
Severity: important
Tags: ftbfs

Dear Maintainer,

This package fails to build from source with Make 4.4.1, most likely because of
changes in $(shell) environment handling: environment variables exported from
Makefiles are now made available to commands invoked using $(shell), which
can cause issues with recursive definitions in particular. See
https://salsa.debian.org/debian/make/-/blob/master/debian/NEWS for a complete
list of backward-incompatible changes since Make 4.3.

Below you will find how the builds end, hopefully the most relevant
part from the build log. A full build log is available here:

https://people.debian.org/~sanvila/make-4.4/build-logs/

Make 4.4.1 is currently available in experimental and will hopefully
soon be uploaded to unstable, at which time this bug will become
release-critical.

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 affects, so that this is still visible in the BTS web
page for this package.

Please reach out to the Make maintainer, Stephen Kitt <skitt@debian.org> if
you need help fixing this.

--------------------------------------------------------------------------------
debian/rules:41: pipe: Too many open files
debian/rules:41: pipe: Too many open files
debian/rules:41: pipe: Too many open files
debian/rules:41: pipe: Too many open files
debian/rules:41: pipe: Too many open files
debian/rules:41: pipe: Too many open files
debian/rules:41: pipe: Too many open files
debian/rules:41: pipe: Too many open files
debian/rules:41: pipe: Too many open files
debian/rules:41: pipe: Too many open files
debian/rules:41: pipe: Too many open files
debian/rules:41: pipe: Too many open files
debian/rules:41: pipe: Too many open files
debian/rules:41: pipe: Too many open files
debian/rules:41: pipe: Too many open files
debian/rules:41: pipe: Too many open files
debian/rules:41: pipe: Too many open files
debian/rules:41: pipe: Too many open files
debian/rules:41: pipe: Too many open files
debian/rules:41: pipe: Too many open files
debian/rules:41: pipe: Too many open files
debian/rules:41: pipe: Too many open files
debian/rules:41: pipe: Too many open files
debian/rules:41: pipe: Too many open files
debian/rules:41: pipe: Too many open files
debian/rules:41: pipe: Too many open files
debian/rules:41: pipe: Too many open files
debian/rules:41: pipe: Too many open files
debian/rules:41: pipe: Too many open files
debian/rules:41: pipe: Too many open files
debian/rules:41: pipe: Too many open files
debian/rules:41: pipe: Too many open files
debian/rules:41: pipe: Too many open files
debian/rules:41: pipe: Too many open files
debian/rules:41: pipe: Too many open files
debian/rules:41: pipe: Too many open files
debian/rules:41: pipe: Too many open files
debian/rules:41: pipe: Too many open files
debian/rules:41: pipe: Too many open files
debian/rules:41: pipe: Too many open files
debian/rules:41: pipe: Too many open files
debian/rules:41: pipe: Too many open files
debian/rules:41: pipe: Too many open files
debian/rules:41: pipe: Too many open files
debian/rules:41: pipe: Too many open files
debian/rules:41: pipe: Too many open files
debian/rules:41: pipe: Too many open files
debian/rules:41: pipe: Too many open files
debian/rules:41: pipe: Too many open files
debian/rules:41: pipe: Too many open files
debian/rules:41: pipe: Too many open files
debian/rules:41: pipe: Too many open files
debian/rules:41: pipe: Too many open files
debian/rules:41: pipe: Too many open files
debian/rules:41: pipe: Too many open files
debian/rules:41: pipe: Too many open files
debian/rules:41: pipe: Too many open files
debian/rules:41: pipe: Too many open files
debian/rules:41: pipe: Too many open files
debian/rules:41: pipe: Too many open files
debian/rules:41: pipe: Too many open files
debian/rules:41: pipe: Too many open files
debian/rules:41: pipe: Too many open files
debian/rules:41: pipe: Too many open files
debian/rules:41: pipe: Too many open files
debian/rules:41: pipe: Too many open files
debian/rules:41: pipe: Too many open files
debian/rules:41: pipe: Too many open files
debian/rules:41: pipe: Too many open files
debian/rules:41: pipe: Too many open files
debian/rules:41: pipe: Too many open files
debian/rules:41: pipe: Too many open files
debian/rules:41: pipe: Too many open files
debian/rules:41: pipe: Too many open files
debian/rules:41: pipe: Too many open files
debian/rules:41: pipe: Too many open files
for PY in ; do \
        $PY setup.py install --install-layout=deb \
	--root=/debian/python3-torch/ ;\
        done
# [list shared objects] use `ls build/lib/*.so` to get a list of all compiled shared objects.
echo {begin listing shared objects}
{begin listing shared objects}
find build/lib -type f | sort
find: ‘build/lib’: No such file or directory
echo {end listing shared objects}
{end listing shared objects}
# [python3-torch::headers -> libtorch-dev] move the headers out of the python package
mkdir -pv debian/libtorch-dev/usr/include
mkdir: created directory 'debian/libtorch-dev'
mkdir: created directory 'debian/libtorch-dev/usr'
mkdir: created directory 'debian/libtorch-dev/usr/include'
mv -v debian/python3-torch/usr/lib/python3*/dist-packages/torch/include/* \
	debian/libtorch-dev/usr/include/
mv: cannot stat 'debian/python3-torch/usr/lib/python3*/dist-packages/torch/include/*': No such file or directory
make[1]: *** [debian/rules:193: override_dh_auto_install] Error 1
make[1]: Leaving directory '/<<PKGBUILDDIR>>'
make: *** [debian/rules:161: binary] Error 2
dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2
--------------------------------------------------------------------------------


Reply to: