Open leofang opened 1 year ago
$ conda list
# packages in environment at /opt/conda/envs/test:
#
# Name Version Build Channel
_openmp_mutex 4.5 2_gnu conda-forge
bzip2 1.0.8 hf897c2e_4 conda-forge
ca-certificates 2023.5.7 hcefe29a_0 conda-forge
cuda-cudart 12.0.107 hac28a21_1 conda-forge
cuda-nvrtc 12.0.76 hac28a21_1 conda-forge
cuda-version 12.0 hffde075_2 conda-forge
cupy 12.0.0 py310h18013f7_2 <unknown>
fastrlock 0.8 py310h16c9dca_3 conda-forge
ld_impl_linux-aarch64 2.40 h2d8c526_0 conda-forge
libblas 3.9.0 16_linuxaarch64_openblas conda-forge
libcblas 3.9.0 16_linuxaarch64_openblas conda-forge
libcublas 12.0.1.189 ha21bd82_2 conda-forge
libcufft 11.0.0.21 ha21bd82_1 conda-forge
libcurand 10.3.1.50 ha21bd82_0 conda-forge
libcusolver 11.4.2.57 ha21bd82_1 conda-forge
libffi 3.4.2 h3557bc0_5 conda-forge
libgcc-ng 12.2.0 h607ecd0_19 conda-forge
libgfortran-ng 12.2.0 he9431aa_19 conda-forge
libgfortran5 12.2.0 hf695500_19 conda-forge
libgomp 12.2.0 h607ecd0_19 conda-forge
liblapack 3.9.0 16_linuxaarch64_openblas conda-forge
libnsl 2.0.0 hf897c2e_0 conda-forge
libnvjitlink 12.0.76 ha21bd82_1 conda-forge
libopenblas 0.3.21 pthreads_h6cb6f83_3 conda-forge
libsqlite 3.41.2 h194ca79_1 conda-forge
libstdcxx-ng 12.2.0 hc13a102_19 conda-forge
libuuid 2.38.1 hb4cce97_0 conda-forge
libzlib 1.2.13 h4e544f5_4 conda-forge
ncurses 6.3 headf329_1 conda-forge
numpy 1.24.3 py310h7f380f4_0 conda-forge
openssl 3.1.0 h31becfc_3 conda-forge
pip 23.1.2 pyhd8ed1ab_0 conda-forge
python 3.10.11 ha43d526_0_cpython conda-forge
python_abi 3.10 3_cp310 conda-forge
readline 8.2 h8fc344f_1 conda-forge
setuptools 67.7.2 pyhd8ed1ab_0 conda-forge
tk 8.6.12 hd8af866_0 conda-forge
tzdata 2023c h71feb2d_0 conda-forge
wheel 0.40.0 pyhd8ed1ab_0 conda-forge
xz 5.2.6 h9cdd2b7_0 conda-forge
Am curious why we didn't see an issue in the ARM build here? Would think this would have detected a new version of GLIBC is needed and not provided for (as seen elsewhere)
@jakirkham I think only the libraries in $PREFIX/lib/
are checked for symbol compatibility. I believe the files in $PREFIX/targets/sbsa-linux/lib/
are "just files" as far as conda-build cares.
Am curious why we didn't see an issue in the ARM build here? Would think this would have detected a new version of GLIBC is needed and not provided for (as seen elsewhere)
I think what happens is that conda-build correctly found the dependency on libm.so
INFO (libcublas,targets/sbsa-linux/lib/libcublasLt.so.12.0.1.189): Needed DSO aarch64-conda-linux-gnu/sysroot/lib64/libm.so.6 found in CDT/compiler package conda-forge::sysroot_linux-aarch64-2.17-h43d7e78_13
but it didn't check if the found DSO also satisfies the glibc requirement (i.e. containing all the versioned symbols needed by libcublasLt.so).
Cross-linking to CUDA Toolkit CentOS 7 deprecation issue ( https://github.com/conda-forge/cuda-feedstock/issues/28 ), which this depends on
Note the two lines
and
Essentially, we are once again hitting the same issue as in cuSPARSELt v0.4.0 (https://github.com/conda-forge/cusparselt-feedstock/pull/23#issuecomment-1524118699) and cuDNN v8.8.0 (https://github.com/conda-forge/cudnn-feedstock/issues/58), but this went totally unnoticed until now when I work on https://github.com/conda-forge/cupy-feedstock/pull/199, because we haven't added the dlopen test to all new CUDA packages.
cc: @jakirkham