Giters

rusty1s / pytorch_scatter

PyTorch Extension Library of Optimized Scatter Operations

Home Page:https://pytorch-scatter.readthedocs.io

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

undefined symbol: _ZN3c1017RegisterOperatorsD1Ev

peutch opened this issue · comments

commented

Hi,

After installing torch-scatter as follow in a Python 3.11 env with torch 2.2.0 :

pip install torch-scatter -f https://data.pyg.org/whl/torch-2.2.0+121.html

I am getting:

OSError: $VIRTUAL_ENV/lib/python3.11/site-packages/torch_scatter/_version_cuda.so: undefined symbol: _ZN3c1017RegisterOperatorsD1Ev

($VIRTUAL_ENV mask the realpath here)

but what seems strange to me is the following:

# more $VIRTUAL_ENV/lib/python3.11/site-packages/torch_scatter-2.1.2.dist-info/WHEEL 
Wheel-Version: 1.0
Generator: bdist_wheel (0.42.0)
Root-Is-Purelib: false
Tag: cp311-cp311-linux_x86_64
# ldd $VIRTUAL_ENV/lib/python3.11/site-packages/torch_scatter/_version_cuda.so
	linux-vdso.so.1 (0x00007ffce6e8f000)
	libc10.so => not found
	libtorch_cpu.so => not found
	libstdc++.so.6 => /lib/x86_64-linux-gnu/libstdc++.so.6 (0x00007fecf3e00000)
	libgcc_s.so.1 => /lib/x86_64-linux-gnu/libgcc_s.so.1 (0x00007fecf40a9000)
	libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007fecf3c1f000)
	libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x00007fecf3b40000)
	/lib64/ld-linux-x86-64.so.2 (0x00007fecf4117000)
# ldd $VIRTUAL_ENV/lib/python3.11/site-packages/torch_scatter/_version_cpu.so
	linux-vdso.so.1 (0x00007ffe37eb5000)
	libc10.so => not found
	libtorch_cpu.so => not found
	libstdc++.so.6 => /lib/x86_64-linux-gnu/libstdc++.so.6 (0x00007f5f55a00000)
	libgcc_s.so.1 => /lib/x86_64-linux-gnu/libgcc_s.so.1 (0x00007f5f55dd7000)
	libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007f5f5581f000)
	libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x00007f5f55cf6000)
	/lib64/ld-linux-x86-64.so.2 (0x00007f5f55e45000)

both are linked to libtorch_cpu.so, is that expected?
Is the first one not supposed to be linked to libtorch_cuda.so?

Regards,
Patrice

commented

Finally, I did an install from the source and I do not have the error any more while it is the same regarding the ldd outputs.
So my hypothesis was sure wrong. Sorry for that.
Don't know what happened with the pip install then...
Fill free to close my issue.