MVIG-SJTU / AlphaPose

Real-Time and Accurate Full-Body Multi-Person Pose Estimation&Tracking System
http://mvig.org/research/alphapose.html
Other
7.96k stars 1.97k forks source link

Issues getting alphapose to work #1099

Open JulianGodd opened 1 year ago

JulianGodd commented 1 year ago

Running this command from a conda environment: python setup.py build develop --user

/home/julian/miniconda3/lib/python3.9/site-packages/torch/cuda/__init__.py:88: UserWarning: CUDA initialization: Unexpected error from cudaGetDeviceCount(). Did you run some cuda functions before calling NumCudaDevices() that might have already set an error? Error 804: forward compatibility was attempted on non supported HW (Triggered internally at ../c10/cuda/CUDAFunctions.cpp:109.)
  return torch._C._cuda_getDeviceCount() > 0
No CUDA runtime is found, using CUDA_HOME='/usr/local/cuda'
/home/julian/miniconda3/lib/python3.9/site-packages/setuptools/installer.py:27: SetuptoolsDeprecationWarning: setuptools.installer is deprecated. Requirements should be satisfied by a PEP 517 installer.
  warnings.warn(
running build
running build_py
copying alphapose/version.py -> build/lib.linux-x86_64-3.9/alphapose
running build_ext
/home/julian/miniconda3/lib/python3.9/site-packages/torch/utils/cpp_extension.py:387: UserWarning: The detected CUDA version (11.8) has a minor version mismatch with the version that was used to compile PyTorch (11.7). Most likely this shouldn't be a problem.
  warnings.warn(CUDA_MISMATCH_WARN.format(cuda_str_version, torch.version.cuda))
/home/julian/miniconda3/lib/python3.9/site-packages/torch/utils/cpp_extension.py:397: UserWarning: There are no g++ version bounds defined for CUDA version 11.8
  warnings.warn(f'There are no {compiler_name} version bounds defined for CUDA version {cuda_str_version}')
building 'detector.nms.soft_nms_cpu' extension
Emitting ninja build file /home/julian/Documents/Alphapose attempt/AlphaPose/build/temp.linux-x86_64-3.9/build.ninja...
Compiling objects...
Allowing ninja to set a default number of workers... (overridable by setting the environment variable MAX_JOBS=N)
ninja: no work to do.
g++ -pthread -B /home/julian/miniconda3/compiler_compat -shared -Wl,-rpath,/home/julian/miniconda3/lib -Wl,-rpath-link,/home/julian/miniconda3/lib -L/home/julian/miniconda3/lib -L/home/julian/miniconda3/lib -Wl,-rpath,/home/julian/miniconda3/lib -Wl,-rpath-link,/home/julian/miniconda3/lib -L/home/julian/miniconda3/lib "/home/julian/Documents/Alphapose attempt/AlphaPose/build/temp.linux-x86_64-3.9/detector/nms/src/soft_nms_cpu.o" -o build/lib.linux-x86_64-3.9/detector/nms/soft_nms_cpu.cpython-39-x86_64-linux-gnu.so
/home/julian/miniconda3/compiler_compat/ld: /lib/x86_64-linux-gnu/libm.so.6: unknown type [0x13] section `.relr.dyn'
/home/julian/miniconda3/compiler_compat/ld: skipping incompatible /lib/x86_64-linux-gnu/libm.so.6 when searching for /lib/x86_64-linux-gnu/libm.so.6
/home/julian/miniconda3/compiler_compat/ld: cannot find /lib/x86_64-linux-gnu/libm.so.6
/home/julian/miniconda3/compiler_compat/ld: /lib/x86_64-linux-gnu/libm.so.6: unknown type [0x13] section `.relr.dyn'
/home/julian/miniconda3/compiler_compat/ld: skipping incompatible /lib/x86_64-linux-gnu/libm.so.6 when searching for /lib/x86_64-linux-gnu/libm.so.6
/home/julian/miniconda3/compiler_compat/ld: /lib/x86_64-linux-gnu/libmvec.so.1: unknown type [0x13] section `.relr.dyn'
/home/julian/miniconda3/compiler_compat/ld: skipping incompatible /lib/x86_64-linux-gnu/libmvec.so.1 when searching for /lib/x86_64-linux-gnu/libmvec.so.1
/home/julian/miniconda3/compiler_compat/ld: cannot find /lib/x86_64-linux-gnu/libmvec.so.1
/home/julian/miniconda3/compiler_compat/ld: /lib/x86_64-linux-gnu/libmvec.so.1: unknown type [0x13] section `.relr.dyn'
/home/julian/miniconda3/compiler_compat/ld: skipping incompatible /lib/x86_64-linux-gnu/libmvec.so.1 when searching for /lib/x86_64-linux-gnu/libmvec.so.1
collect2: error: ld returned 1 exit status
error: command '/usr/bin/g++' failed with exit code 1

Do you know what could cause this? Thanks in advance

Fang-Haoshu commented 1 year ago

Hi, sorry but we haven't met that before. Perhaps you can try google the error