Peter Heywood

Node 20 based actions are incompatible with centos7 due to glibc requirement apparently, meaning both checkout@v4 and upload-artifact@v4 are not compatible with manylinux2014 containers. ``` /__e/node20/bin/node: /lib64/libm.so.6: version `GLIBC_2.27' not...

Replaced by #1228

Edited to adapt this to CCCL, the combined successor to thrust, cub and libcudacxx.

Currently, the only dynamic links that are not allowed bymanlinux are: ``` libcuda.so.1 libnvrtc.so.11.2 ``` This confirms that libcudart.so is being statically linked (which is default in CMake when using...

General dlopen process / things to do + CMake option `USE_DLOPEN` or similar, which then sets a macro on the static library target which enebales the dlopen code path(s) +...

I've got a proof of concept working which uses dlopen for `libcuda.so.1`, using 2 of the functions from the driver api. It's a long way from perfect, and wrapping methods...

I've made some more progress (both positive and negative) with visuslaition wheels using auditwheel for compliance with visualisation, by using `patchelf` to skip the current `libcuda.so` issues. ## Pypi/Manylinux and...

As another example of auditwheel and patchelf being used, ONNXruntime uses a similar (but python-based) process in `setup.py` to remove the cuda dependencies before rapairing the wheel. It's unclear if...

re: `libcuda.so` etc, Nvidia/DALI is another example which dynamic links against `libcuda.so`. They provide a CMake library target which is the stub that mocks `libcuda.so`, using a python script to...

When CUDA dislikes the version of clang (or gcc) used, it emits a compile time error. When CMake attempts to check for a working CUDA compiler, it doesn't output why...