fatal error: pyconfig.h: No such file or directory

[pcmoritz]

Dear all,

if I clone the latest version of caffe from github and run 'make pycaffe', I get the following error:

In file included from /usr/include/boost/python/detail/prefix.hpp:13:0,
                 from /usr/include/boost/python/args.hpp:8,
                 from /usr/include/boost/python.hpp:11,
                 from python/caffe/_caffe.cpp:8:
/usr/include/boost/python/detail/wrap_python.hpp:50:23: fatal error: pyconfig.h: No such file or directory

I put the python subdirectory in my PYTHONPATH. This is a copy of #410, which still persists. Any help would be appreciated.

Best,
Philipp.

[longjon]

Are the appropriate headers and libraries installed for Python development on your system? Are they accessible from the paths defined by PYTHON_INCLUDES and PYTHON_LIB in Makefile.config?

(By the way, why don't we use python-config for setting those variables automatically?)

[shelhamer]

@longjon I think we don't automatically configure python in case of
multiple python installs and/or users who have a system python but really
would have a better life with Anaconda and so on.

Le mardi 10 juin 2014, longjon notifications@github.com a écrit :

Are the appropriate headers and libraries installed for Python development
on your system? Are they accessible from the paths defined by
PYTHON_INCLUDES and PYTHON_LIB in Makefile.config?

(By the way, why don't we use python-config for setting those variables
automatically?)

—
Reply to this email directly or view it on GitHub
#489 (comment).

Evan Shelhamer

[longjon]

@shelhamer that's sensible enough, although surely the user's PATH should contain the desired python, and therefore the desired python-config? (Otherwise things are likely to go poorly when the user launches python and imports pycaffe built against a different Python, as we've seen happen before.)

In any case building against Anaconda explicitly is a commented option in Makefile.config.example, the question is just what the default should be.

[pcmoritz]

Thank you for your help, adding
/usr/include/python2.7/
to the PYTHON_INCLUDE list in Makefile.config did the trick.

[crizCraig]

Specifying the correct anaconda location fixed this for me. See pull request #1296. So I changed ANACONDA_HOME to /anaconda.

[admercs]

This work for me (source):

export CPLUS_INCLUDE_PATH=/usr/include/python2.7
make clean
make all

[ghost]

I also meet this problem... and try to close it.

[ShivangiM]

Thanks @adam-erickson it worked for me too.

[dookdick]

@adam-erickson how and where should I run/put those lines in your comments? I'm quite new on Ubuntu so I need more details on this.

[chenchongsong]

@adam-erickson Thanks!!!

[alexjingjing]

@adam-erickson Thank you so much!

[adu81020799]

Thanks this helped me too

[luyao777]

export CPLUS_INCLUDE_PATH=/usr/include/python2.7

That's work for me! Thanks

[jahab]

changing the gcc version resolved my error. I configured to gcc6 from gcc7. https://medium.com/@atinesh/ubuntu-tips-and-tricks-configuring-multiple-gcc-in-same-ubuntu-machine-a391a34d79c2

[rajhlinux]

I tried all answers on this thread, none works for me on FreeBSD 13.1, using clang 13... whats the deal here?

[arjunskumar]

for ROS-noetic users

export CPLUS_INCLUDE_PATH=/usr/include/python3.8
catkin build pkg-name

[dragonQian]

这是来自QQ邮箱的假期自动回复邮件。   您好，我最近正在休假中，无法亲自回复您的邮件。我将在假期结束后，尽快给您回复。