georghess / voxel-mae

Code for the paper "Masked Autoencoders for Self-Supervised Learning on Automotive Point Clouds"
Apache License 2.0
73 stars 6 forks source link

python setup.py develop did not run successfully. #5

Closed Varatharajan-Raja closed 1 year ago

Varatharajan-Raja commented 1 year ago
     File "/home/Voxel-MAE_PointPillars/voxel-mae/vxlppvenv/lib/python3.7/site-packages/setuptools/_distutils/command/build_ext.py", line 494, in _build_extensions_serial
        self.build_extension(ext)
      File "/home/Voxel-MAE_PointPillars/voxel-mae/vxlppvenv/lib/python3.7/site-packages/setuptools/command/build_ext.py", line 246, in build_extension
        _build_ext.build_extension(self, ext)
      File "/home/Voxel-MAE_PointPillars/voxel-mae/vxlppvenv/lib/python3.7/site-packages/setuptools/_distutils/command/build_ext.py", line 556, in build_extension
        depends=ext.depends,
      File "/home/Voxel-MAE_PointPillars/voxel-mae/vxlppvenv/lib/python3.7/site-packages/torch/utils/cpp_extension.py", line 668, in unix_wrap_ninja_compile
        with_cuda=with_cuda)
      File "/home/Voxel-MAE_PointPillars/voxel-mae/vxlppvenv/lib/python3.7/site-packages/torch/utils/cpp_extension.py", line 1578, in _write_ninja_file_and_compile_objects
        error_prefix='Error compiling objects for extension')
      File "/home/Voxel-MAE_PointPillars/voxel-mae/vxlppvenv/lib/python3.7/site-packages/torch/utils/cpp_extension.py", line 1916, in _run_ninja_build
        raise RuntimeError(message) from e
    RuntimeError: Error compiling objects for extension
    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.
    full command: /home/Voxel-MAE_PointPillars/voxel-mae/vxlppvenv/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/Voxel-MAE_PointPillars/voxel-mae/setup.py'"'"',), "<pip-setuptools-caller>", "exec"))' develop --no-deps
    cwd: /home/Voxel-MAE_PointPillars/voxel-mae/
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.

**Environment:

Python 3.7.0 torch 1.13.1+cu116 torchaudio 0.13.1+cu116 torchvision 0.14.1+cu116 mmcv-full 1.7.0 mmdet 2.26.0 mmsegmentation 0.29.1 pip 22.3.1**

georghess commented 1 year ago

Hi,

Have you installed setuptools? The error trace indicates to me that the package is missing.

Varatharajan-Raja commented 1 year ago

Requirement already satisfied: setuptools in ./vxlppvenv/lib/python3.7/site-packages (65.6.3)

Yes, It is already installed.

Varatharajan-Raja commented 1 year ago

Not sure why it did not run in venv. However, It ran while buliding docker.Therefore, closing the issue.