:: [devuan-dev] bug#369: marked as don…
Página superior
Eliminar este mensaje
Responder a este mensaje
Autor: Devuan bug Tracking System
Fecha:  
A: Mark Hindley
Asunto: [devuan-dev] bug#369: marked as done (nvidia-cuda-dev: Missing folder in LIBRARIES environment variable in /etc/nvcc.profile)
Your message dated Wed, 11 Jan 2023 12:53:08 +0000
with message-id <Y76xNLqtr/hqK1mH@???>
and subject line Re: bug#369: nvidia-cuda-dev: Missing folder in LIBRARIES environment variable in /etc/nvcc.profile
has caused the Devuan bug report #369,
regarding nvidia-cuda-dev: Missing folder in LIBRARIES environment variable in /etc/nvcc.profile
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 owner@???
immediately.)


--
369: https://bugs.devuan.org/cgi/bugreport.cgi?bug=369
Devuan Bug Tracking System
Contact owner@??? with problems
Package: nvidia-cuda-dev
Version: 10.1.105-3+b1
Severity: important

Dear Maintainer,

The NVCC compiler (or rather the nvlink linker) looks for libraries in
the folder listed in the LIBRARIES environment variable. This
environment variable is added to from within the nvcc.profile file. In
Debian/Devuan, that file is located in /etc and contains:

LIBRARIES       =+ $(_SPACE_) -L/usr/lib/x86_64-linux-gnu/stubs


However - that's not the only necessary folder (perhaps not even the
more important one): nvlink needs to be search /usr/lib/x86_64-linux-gnu
as well (without the /stubs).

And indeed, if we look at /usr/local/cuda-10.1/bin/nvcc.profile (which
is also installed for some reason), we find:

LIBRARIES        =+ $(_SPACE_)
"-L$(TOP)/$(_TARGET_DIR_)/lib$(_TARGET_SIZE_)/stubs"
"-L$(TOP)/$(_TARGET_DIR_)/lib$(_TARGET_SIZE_)"


... with both folders.

This is a bug, and it makes nvlink fail to link even simple programs in
some cases. See, for example:

https://stackoverflow.com/q/59481689/1593077



-- System Information:
Debian Release: 10.0
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 5.2.0-3-amd64 (SMP w/4 CPU cores)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE,
TAINT_UNSIGNED_MODULE
Locale: LANG=en_IL, LC_CTYPE=en_IL (charmap=UTF-8), LANGUAGE=en_IL:en
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)

Versions of packages nvidia-cuda-dev depends on:
ii  libaccinj64-10.1  10.1.105-3+b1
ii  libcublas10       10.1.105-3+b1
ii  libcublaslt10     10.1.105-3+b1
ii  libcudart10.1     10.1.105-3+b1
ii  libcufft10        10.1.105-3+b1
ii  libcufftw10       10.1.105-3+b1
ii  libcuinj64-10.1   10.1.105-3+b1
ii  libcurand10       10.1.105-3+b1
ii  libcusolver10     10.1.105-3+b1
ii  libcusparse10     10.1.105-3+b1
ii  libnppc10         10.1.105-3+b1
ii  libnppial10       10.1.105-3+b1
ii  libnppicc10       10.1.105-3+b1
ii  libnppicom10      10.1.105-3+b1
ii  libnppidei10      10.1.105-3+b1
ii  libnppif10        10.1.105-3+b1
ii  libnppig10        10.1.105-3+b1
ii  libnppim10        10.1.105-3+b1
ii  libnppist10       10.1.105-3+b1
ii  libnppisu10       10.1.105-3+b1
ii  libnppitc10       10.1.105-3+b1
ii  libnpps10         10.1.105-3+b1
ii  libnvblas10       10.1.105-3+b1
ii  libnvgraph10      10.1.105-3+b1
ii  libnvidia-ml1     430.50-1
ii  libnvjpeg10       10.1.105-3+b1
ii  libnvrtc10.1      10.1.105-3+b1
ii  libnvtoolsext1    10.1.105-3+b1
ii  libnvvm3          10.1.105-3+b1
ii  libthrust-dev     1.9.5-1


Versions of packages nvidia-cuda-dev recommends:
ii  libcuda1 [libcuda-10.1-1]    430.50-1
ii  libgl1-mesa-dev [libgl-dev]  19.1.6-1
ii  libnvcuvid1                  430.50-1
ii  libvdpau-dev                 1.2-1


nvidia-cuda-dev suggests no packages.
Version: 10.1.168-6

Closing as fixed in Debian.

Mark