Bugzilla Bug 191590

Hi,

while running today's world update, I discovered following problem:

>>> Compiling source in /var/tmp/portage/dev-python/dbus-python-0.82.2/work/dbus-python-0.82.2 ...
 * econf: updating dbus-python-0.82.2/config.guess with
/usr/share/gnuconfig/config.guess
 * econf: updating dbus-python-0.82.2/config.sub with
/usr/share/gnuconfig/config.sub
./configure --prefix=/usr --host=i686-pc-linux-gnu --mandir=/usr/share/man
--infodir=/usr/share/info --datadir=/usr/share --sysconfdir=/etc
--localstatedir=/var/lib --docdir=/usr/share/doc/dbus-python-0.82.2
--build=i686-pc-linux-gnu
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for gawk... gawk
checking whether make sets $(MAKE)... yes
checking build system type... i686-pc-linux-gnu
checking host system type... i686-pc-linux-gnu
checking for style of include used by make... GNU
checking for i686-pc-linux-gnu-gcc... i686-pc-linux-gnu-gcc
checking for C compiler default output file name... a.out
checking whether the C compiler works... yes
checking whether we are cross compiling... no
checking for suffix of executables... 
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether i686-pc-linux-gnu-gcc accepts -g... yes
checking for i686-pc-linux-gnu-gcc option to accept ISO C89... none needed
checking dependency style of i686-pc-linux-gnu-gcc... gcc3
checking for a sed that does not truncate output... /bin/sed
checking for grep that handles long lines and -e... /bin/grep
checking for egrep... /bin/grep -E
checking for ld used by i686-pc-linux-gnu-gcc... /usr/i686-pc-linux-gnu/bin/ld
checking if the linker (/usr/i686-pc-linux-gnu/bin/ld) is GNU ld... yes
checking for /usr/i686-pc-linux-gnu/bin/ld option to reload object files... -r
checking for BSD-compatible nm... /usr/bin/nm -B
checking whether ln -s works... yes
checking how to recognize dependent libraries... pass_all
checking how to run the C preprocessor... i686-pc-linux-gnu-gcc -E
checking for ANSI C header files... yes
checking for sys/types.h... yes
checking for sys/stat.h... yes
checking for stdlib.h... yes
checking for string.h... yes
checking for memory.h... yes
checking for strings.h... yes
checking for inttypes.h... yes
checking for stdint.h... yes
checking for unistd.h... yes
checking dlfcn.h usability... yes
checking dlfcn.h presence... yes
checking for dlfcn.h... yes
checking the maximum length of command line arguments... 98304
checking command to parse /usr/bin/nm -B output from i686-pc-linux-gnu-gcc
object... ok
checking for objdir... .libs
checking for i686-pc-linux-gnu-ar... i686-pc-linux-gnu-ar
checking for i686-pc-linux-gnu-ranlib... i686-pc-linux-gnu-ranlib
checking for i686-pc-linux-gnu-strip... i686-pc-linux-gnu-strip
checking if i686-pc-linux-gnu-gcc supports -fno-rtti -fno-exceptions... no
checking for i686-pc-linux-gnu-gcc option to produce PIC... -fPIC
checking if i686-pc-linux-gnu-gcc PIC flag -fPIC works... yes
checking if i686-pc-linux-gnu-gcc static flag -static works... yes
checking if i686-pc-linux-gnu-gcc supports -c -o file.o... yes
checking whether the i686-pc-linux-gnu-gcc linker
(/usr/i686-pc-linux-gnu/bin/ld) supports shared libraries... yes
checking whether -lc should be explicitly linked in... no
checking dynamic linker characteristics... GNU/Linux ld.so
checking how to hardcode library paths into programs... immediate
checking whether stripping libraries is possible... yes
checking if libtool supports shared libraries... yes
checking whether to build shared libraries... yes
checking whether to build static libraries... no
configure: creating libtool
checking for a Python interpreter with version >= 2.4.0... python
checking for python... /usr/bin/python
checking for python version... 2.4
checking for python platform... linux2
checking for python script directory... ${prefix}/lib/python2.4/site-packages
checking for python extension module directory...
${exec_prefix}/lib/python2.4/site-packages
checking for Python headers using /usr/bin/python-config --includes...
-lpython2.4 -lm -L/usr/lib/python2.4/config 
checking whether those headers are sufficient... no
configure: error: could not find Python headers

-----------------------
Okay, so I searched for the reason and got...

configure:9844: checking whether those headers are sufficient
configure:9862: i686-pc-linux-gnu-gcc -E  -lpython2.4 -lm
-L/usr/lib/python2.4/config  conftest.c
conftest.c:24:20: error: Python.h: No such file or directory
distcc[23058] ERROR: compile (null) on localhost failed
configure:9868: $? = 1
configure: failed program was:
| /* confdefs.h.  */
| #define PACKAGE_NAME "dbus-python"
| #define PACKAGE_TARNAME "dbus-python"
| #define PACKAGE_VERSION "0.82.2"
| #define PACKAGE_STRING "dbus-python 0.82.2"
| #define PACKAGE_BUGREPORT
"http://bugs.freedesktop.org/enter_bug.cgi?product=dbus&component=python"
| #define DBUS_PYTHON_MAJOR_VERSION 0
| #define DBUS_PYTHON_MINOR_VERSION 82
| #define DBUS_PYTHON_MICRO_VERSION 2
| #define PACKAGE "dbus-python"
| #define VERSION "0.82.2"
| #define STDC_HEADERS 1
| #define HAVE_SYS_TYPES_H 1
| #define HAVE_SYS_STAT_H 1
| #define HAVE_STDLIB_H 1
| #define HAVE_STRING_H 1
| #define HAVE_MEMORY_H 1
| #define HAVE_STRINGS_H 1
| #define HAVE_INTTYPES_H 1
| #define HAVE_STDINT_H 1
| #define HAVE_UNISTD_H 1
| #define HAVE_DLFCN_H 1
| /* end confdefs.h.  */
| #include <Python.h>
configure:9880: result: no
configure:9882: error: could not find Python headers
---------------------------------------------------

Any ideas/bugfixes in sight?


-Ionic

Any comments Python herd? It worked for me.

Could you post your python version, please?

one box is ~arch and one box is arch. so, 2.4.4-r4 on one and 2.5.1-r2 on the
other

appears it's an issue with the old python-config. depping on 2.4.4-r5 and
higher so we get the new one.

forgot to close bug

(In reply to comment #5)
> forgot to close bug
> 

Could you tell me how did you fix it?
I have this bug too