Hello! Is there a reason why the PETSc build system looks for libOpenCL.a, but not for libOpenCL.so <https://urldefense.us/v3/__http://libopencl.so/__;!!G_uCfscf7eWS!aUphnoqlYDmqiqau_zLjz7XYVRCrIS7jxMEPFgTLd1sLr9q23CNw_4oCjg_wtfFJ9P9SzlfKpcPjjS2eLJs$ > on linux platforms? I have a machine with debian 12.5 and nvidia card. It has these packages installed:
cuda-opencl-12-5/unknown,now 12.5.39-1 amd64 [installed,automatic] cuda-opencl-dev-12-5/unknown,now 12.5.39-1 amd64 [installed,automatic] nvidia-libopencl1/unknown,now 555.42.02-1 amd64 [installed,automatic] nvidia-opencl-common/unknown,now 555.42.02-1 amd64 [installed,automatic] nvidia-opencl-icd/unknown,now 555.42.02-1 amd64 [installed,automatic] opencl-c-headers/stable,now 3.0~2023.02.06-1 all [installed,automatic] opencl-clhpp-headers/stable,now 3.0~2023.02.06-1 all [installed,automatic] opencl-headers/stable,now 3.0~2023.02.06-1 all [installed] It only has .so, but no .a $ find /usr -iname 'libopencl*' /usr/local/cuda-12.5/targets/x86_64-linux/lib/libOpenCL.so.1.0.0 /usr/local/cuda-12.5/targets/x86_64-linux/lib/libOpenCL.so.1 /usr/local/cuda-12.5/targets/x86_64-linux/lib/libOpenCL.so /usr/local/cuda-12.5/targets/x86_64-linux/lib/libOpenCL.so.1.0 /usr/lib/x86_64-linux-gnu/libOpenCL.so.1.0.0 /usr/lib/x86_64-linux-gnu/libOpenCL.so.1 Are users supposed to use `--with-opencl-include=` and `--with-opencl-lib` switches in this case? Thanks, David
