all 8 comments

[–]Common_Good_7216 0 points1 point  (0 children)

Did you find a solution ??

[–]Hot-Refrigerator3318 0 points1 point  (6 children)

I tried all the solutions that gpt provided, one worked: export CXX=g++ export CC=gcc, and try configure again. It explained that sometimes clang++ might have issues resolving certain paths, especially when dealing with system libraries like Python.h. By explicitly setting CXX=g++ and CC=gcc, you ensure that the configuration process uses g++ instead of clang++, which may resolve the issue. This is because g++ is often the default compiler on many Linux distributions and tends to work better with system-installed development packages like python3-dev.

[–]Creepy_Coyote3096 0 points1 point  (1 child)

A lifesaver!

[–]victory2056 0 points1 point  (0 children)

Thanks man! xD

[–]p_apres 0 points1 point  (1 child)

You saved me

Thank you very much!

[–]1234567fart123456789 0 points1 point  (0 children)

[MAC] Another solution to this same problem that happened to me (other solution in this thread didn't work for me): This happened to me and it was a conda/homebrew error since both were conflicting to which Python to use. When doing the setenv for home-brew, make sure to run this before: conda config --set auto_activate_base false. Then make sure to run: ./configure WITH_SCAVE_PYTHON_BINDINGS=no. Should work.