"David A. Markowitz" <david.a.markowitz(a)gmail.com> writes:
Many thanks Andreas, I've solved the problem now. While digging
compiler.py code, I noticed a check for the PYCUDA_DEFAULT_NVCC_FLAGS
environment variable, which is then passed to nvcc. Ultimately I was able
to solve my problem by putting a file in /etc/profile.d/ with the contents:
This offers a simple but effective way for PyCUDA to point nvcc in the
I'm still not sure why I wasn't able to fix the "libdevice library not
found" error by modifying nvcc.profile directly, but the above is probably
a better solution regardless, because it doesn't require modifications to a
file that affects nvcc's operation in all use cases (i.e. even when it's
not called by PyCUDA). Since I've only encountered this problem using
PyCUDA, it makes sense that the solution should only kick in when nvcc is
called by PyCUDA.
I'm really looking forward to using this software package. Thank you for
all of your hard work putting it together!
Glad to hear you got things to work!