Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

pip install fails on "Could NOT find Qhull" #261

Open
nmz787-intel opened this issue Jul 8, 2024 · 8 comments
Open

pip install fails on "Could NOT find Qhull" #261

nmz787-intel opened this issue Jul 8, 2024 · 8 comments

Comments

@nmz787-intel
Copy link

latest release (0.9.53) is failing to install, while just-prior release worked (0.9.52).

  Building wheel for gdstk (pyproject.toml): started
  Building wheel for gdstk (pyproject.toml): finished with status 'error'
  error: subprocess-exited-with-error
  
  × Building wheel for gdstk (pyproject.toml) did not run successfully.
  │ exit code: 1
  ╰─> [28 lines of output]
      *** scikit-build-core 0.9.8 using CMake 3.30.0 (wheel)
      *** Configuring CMake...
      loading initial cache file build/cp39-cp39-linux_x86_64/CMakeInit.txt
      -- The CXX compiler identification is GNU 8.2.0
      -- The C compiler identification is GNU 8.2.0
      -- Detecting CXX compiler ABI info
      -- Detecting CXX compiler ABI info - done
      -- Check for working CXX compiler: /usr/pkgs/gcc/8.2.0/bin/g++ - skipped
      -- Detecting CXX compile features
      -- Detecting CXX compile features - done
      -- Detecting C compiler ABI info
      -- Detecting C compiler ABI info - done
      -- Check for working C compiler: /usr/pkgs/gcc/8.2.0/bin/gcc - skipped
      -- Detecting C compile features
      -- Detecting C compile features - done
      -- Found ZLIB: /usr/lib64/libz.so (found suitable version "1.2.11", minimum required is "1.2.7")
      CMake Error at /tmp/pip-build-env-msgx5xg0/normal/lib/python3.9/site-packages/cmake/data/share/cmake-3.30/Modules/FindPackageHandleStandardArgs.cmake:233 (message):
        Could NOT find Qhull (missing: QHULL_LIBRARY QHULL_INCLUDE_DIR) (Required
        is at least version "8")
      Call Stack (most recent call first):
        /tmp/pip-build-env-msgx5xg0/normal/lib/python3.9/site-packages/cmake/data/share/cmake-3.30/Modules/FindPackageHandleStandardArgs.cmake:603 (_FPHSA_FAILURE_MESSAGE)
        cmake_modules/FindQhull.cmake:170 (find_package_handle_standard_args)
        src/CMakeLists.txt:23 (find_package)
      
      
      -- Configuring incomplete, errors occurred!
      
      *** CMake configuration failed
      [end of output]
  
  note: This error originates from a subprocess, and is likely not a problem with pip.
  ERROR: Failed building wheel for gdstk
@heitzmann
Copy link
Owner

This is a problem with CMake not finding qhull in your system, but there were no changes to that between release. This is probably related to some qhull installation change on the host.

@nmz787-intel
Copy link
Author

hmm, forcing my pip requirements.txt list to use 0.9.52 allows pip to proceed successfully. Is there any possibility some qhull files didn't get packaged and uploaded to pypi?

@heitzmann
Copy link
Owner

Very strange. The only qhull-related installation file is in cmake_modules, but that is present in the source distribution in pypi.

@Rishabhgoyal07
Copy link

@nmz787-intel, I am trying to run the gdstk module locally, when i am running the makefile present in the module, it is giving me the same error of Qhull not found, I have pasted the screenshot below. Can you help me resolve this issue
image

@heitzmann
Copy link
Owner

You need the qhull library installed on your system and available for CMake to find. That's the error being reported.

@nmz787-intel
Copy link
Author

@heitzmann I reviewed the commit history between the (0.9.52) and (0.9.53) releases, and didn't see anything obviously regarding QHull or packaging, are there any commits you can point me to for review? Or is there really nothing that changed?

@heitzmann
Copy link
Owner

Indeed, there were no changes between these releases, that's why I'm finding this issue so unexpected.

@vstar-lc
Copy link

@Rishabhgoyal07 Did you solve this problem and if so, how did you solve it?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants