svox2
svox2 copied to clipboard
Installation issue
Received error while pip install -e . --verbose
OS: Ubuntu
cuda 11.7 (its working fine with other code/repo, so not likely a cuda issue.)
Using pip 22.3.1 from /home/anaconda3/envs/plenoxel/lib/python3.8/site-packages/pip (python 3.8)
Obtaining file:///home/svox2
Running command python setup.py egg_info
running egg_info
creating /tmp/pip-pip-egg-info-57_evqkd/svox2.egg-info
writing /tmp/pip-pip-egg-info-57_evqkd/svox2.egg-info/PKG-INFO
writing dependency_links to /tmp/pip-pip-egg-info-57_evqkd/svox2.egg-info/dependency_links.txt
writing top-level names to /tmp/pip-pip-egg-info-57_evqkd/svox2.egg-info/top_level.txt
writing manifest file '/tmp/pip-pip-egg-info-57_evqkd/svox2.egg-info/SOURCES.txt'
No CUDA runtime is found, using CUDA_HOME='/usr/local/cuda-11.7'
package init file 'svox2/csrc/init.py' not found (or not a regular file)
reading manifest file '/tmp/pip-pip-egg-info-57_evqkd/svox2.egg-info/SOURCES.txt'
adding license file 'LICENSE'
writing manifest file '/tmp/pip-pip-egg-info-57_evqkd/svox2.egg-info/SOURCES.txt'
Preparing metadata (setup.py) ... done
Installing collected packages: svox2
Running setup.py develop for svox2
Running command python setup.py develop
running develop
running egg_info
writing svox2.egg-info/PKG-INFO
writing dependency_links to svox2.egg-info/dependency_links.txt
writing top-level names to svox2.egg-info/top_level.txt
No CUDA runtime is found, using CUDA_HOME='/usr/local/cuda-11.7'
package init file 'svox2/csrc/init.py' not found (or not a regular file)
reading manifest file 'svox2.egg-info/SOURCES.txt'
adding license file 'LICENSE'
writing manifest file 'svox2.egg-info/SOURCES.txt'
running build_ext
Traceback (most recent call last):
File "
× python setup.py develop did not run successfully.
│ exit code: 1
╰─> See above for output.
note: This error originates from a subprocess, and is likely not a problem with pip.
full command: /home/anaconda3/envs/plenoxel/bin/python -c '
exec(compile('"'"''"'"''"'"'
# This is <pip-setuptools-caller> -- a caller that pip uses to run setup.py
#
# - It imports setuptools before invoking setup.py, to enable projects that directly
# import from `distutils.core` to work with newer packaging standards.
# - It provides a clear error message when setuptools is not installed.
# - It sets `sys.argv[0]` to the underlying `setup.py`, when invoking `setup.py` so
# setuptools doesn'"'"'t think the script is `-c`. This avoids the following warning:
# manifest_maker: standard file '"'"'-c'"'"' not found".
# - It generates a shim setup.py, for handling setup.cfg-only projects.
import os, sys, tokenize
try:
import setuptools
except ImportError as error:
print(
"ERROR: Can not execute `setup.py` since setuptools is not available in "
"the build environment.",
file=sys.stderr,
)
sys.exit(1)
__file__ = %r
sys.argv[0] = __file__
if os.path.exists(__file__):
filename = __file__
with tokenize.open(__file__) as f:
setup_py_code = f.read()
else:
filename = "<auto-generated setuptools caller>"
setup_py_code = "from setuptools import setup; setup()"
exec(compile(setup_py_code, filename, "exec"))
'"'"''"'"''"'"' % ('"'"'/home/svox2/setup.py'"'"',), "<pip-setuptools-caller>", "exec"))' develop --no-deps
cwd: /home/svox2/
error: subprocess-exited-with-error
× python setup.py develop did not run successfully. │ exit code: 1 ╰─> See above for output.
note: This error originates from a subprocess, and is likely not a problem with pip.
I'm having the exact same error! Have you managed to solve it?
I tried a lot to fix this issue, and I finally found out that there is a simple way to fix this.
First, remove your 'plenoxel' conda environment.
Second, set the specific version of pytorch in environment.yml
like this.
- pytorch=1.11.0
(line25)
Third, redo the command below
conda env create -f environment.yml
conda activate plenoxel
pip install -e . --verbose
I guess that the latest pytorch version was not well doing with plenoxel. Setting it to 1.11.0 helped this case. (Although, lots of warnings occured)
Confirmed to have solved it for me as well, thx @jaeyeol816
Thanks a lot! It also solved my problem.
Well, I added it but still not work.
I tried a lot to fix this issue, and I finally found out that there is a simple way to fix this.
First, remove your 'plenoxel' conda environment.
Second, set the specific version of pytorch in
environment.yml
like this.- pytorch=1.11.0
(line25)Third, redo the command below
conda env create -f environment.yml conda activate plenoxel pip install -e . --verbose
I guess that the latest pytorch version was not well doing with plenoxel. Setting it to 1.11.0 helped this case. (Although, lots of warnings occured)
What worked for me is specifying the cudatoolkit version in addition to the pytorch version. Specifically, I set torch==1.11.0
and cudatoolkit=11.3
in the environment.yml
before creating the conda environment.
What worked for me is specifying the cudatoolkit version in addition to the pytorch version. Specifically, I set
torch==1.11.0
andcudatoolkit=11.3
in theenvironment.yml
before creating the conda environment.
Hello, I set pytorch=1.11.0 and cudatoolkit=11.3 in the environment.yml. But I still get error.
What worked for me is specifying the cudatoolkit version in addition to the pytorch version. Specifically, I set
torch==1.11.0
andcudatoolkit=11.3
in theenvironment.yml
before creating the conda environment.Hello, I set pytorch=1.11.0 and cudatoolkit=11.3 in the environment.yml. But I still get error.
Just make it pytorch and cudatoolkit. Let it download the proper version itself. The point is that the torch should match your cuda, torch==1.11.0 may not match tour cuda.