Python missing or unusable while compiling gdb under Cent OS 5

3
votes

I checked this question and it is not applicable. Python missing or unusable error while cross compiling GDB

I'm trying to build gdb 7.5 with python support on Cent OS 5.

configure --with-expat --with-python

Does not log any errors and the Python devel files are installed.

I set LDFLAGS="L/usr/local/expat-2.1 -L/opt/python27/lib

/opt/python27/lib contains:

rwxrwxrwx  1 root root      19 Mar 14 15:35 libpython2.7.so -> libpython2.7.so.1.0
-r-xr-xr-x  1 root root 1893448 Aug 30  2012 libpython2.7.so.1.0
drwxr-xr-x  2 root root    4096 Mar 14 15:35 pkgconfig
drwxr-xr-x 27 root root   20480 Mar 14 21:49 python2.7

Running make produces this error:

checking whether to use python... yes
checking for python... /opt/python27/bin/python
checking for python2.7... no
configure: error: python is missing or unusable

/opt/python27/bin/python exists has the correct permissions and is executable.

Why can't the link process find python?

2
pythonpython-2.7gdbmakefile
You need to read config.log and find out what exactly has failed. - wRAR
There are no errors in config.log. - Robert
Then you are reading the wrong config.log. - wRAR
I've looked through all 13 config.log and the there errors are either: - the standard choke errors - ac_nonexistent.h errors which don't affect compilation - conftest.c errors which don't apply to this compilation Where would you suggest looking? - Robert
You should read only one config.log, in the build directory. - wRAR

2 Answers

3
votes

The next line AFTER the configure: error: line should be something like:

make[1]: [configure-gdb]: ....

telling you that this error comes from running configure in the gdb subdirectory. So you should look in the config.log file there. This should show you something that configure tried to do that failed -- probably a chunk of C code that failed to compile, with an error message from the compiler something like 'can't find include file "Python.h"'. This tells you what the problem is -- it couldn't find the python header file used to embed python in gdb.

Now your problem may be slightly different, but its probably related to not having the python embedding components properly installed.

1
votes

Why can't the link process find python?

It's not the link process; it's the configure process in one of the subdirectories.

Find out which subdirectory it is (make should say Leaving directory XXXX), and look in config.log in that subdirectory for what went wrong.

The reason I posted is that config.log does not point to a problem, yet when I run make I receive the error from the original post

The make process runs additional configure processes. Your error is clearly from that additional process. You claim to have checked all config.logs in all subdirectories, but that appears unlikely given the symptoms you've described.