#2 configure warns about arrayobject.h

[Philipp Gortan]

he, when trying to build python-gtkextra from cvs, i
get the following:

i'm using python2.4 and gtk+extra from cvs built for
gtk2 on gentoo

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 gcc... 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 gcc accepts -g... yes
checking for gcc option to accept ANSI C... none needed
checking dependency style of gcc... gcc3
checking for a sed that does not truncate output...
/usr/bin/sed
checking for egrep... grep -E
checking for ld used by 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 recognise dependent libraries... pass_all
checking how to run the C preprocessor... 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 for g++... g++
checking whether we are using the GNU C++ compiler... yes
checking whether g++ accepts -g... yes
checking dependency style of g++... gcc3
checking how to run the C++ preprocessor... g++ -E
checking for g77... no
checking for f77... no
checking for xlf... no
checking for frt... no
checking for pgf77... no
checking for fort77... no
checking for fl32... no
checking for af77... no
checking for f90... no
checking for xlf90... no
checking for pgf90... no
checking for epcf90... no
checking for f95... no
checking for fort... no
checking for xlf95... no
checking for ifc... no
checking for efc... no
checking for pgf95... no
checking for lf95... no
checking for gfortran... no
checking whether we are using the GNU Fortran 77
compiler... no
checking whether accepts -g... no
checking the maximum length of command line
arguments... 32768
checking command to parse /usr/bin/nm -B output from
gcc object... ok
checking for objdir... .libs
checking for ar... ar
checking for ranlib... ranlib
checking for strip... strip
checking for correct ltmain.sh version... yes
checking if gcc static flag works... yes
checking if gcc supports -fno-rtti -fno-exceptions... no
checking for gcc option to produce PIC... -fPIC
checking if gcc PIC flag -fPIC works... yes
checking if gcc supports -c -o file.o... yes
checking whether the 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
appending configuration tag "CXX" to libtool
checking for ld used by g++...
/usr/i686-pc-linux-gnu/bin/ld
checking if the linker (/usr/i686-pc-linux-gnu/bin/ld)
is GNU ld... yes
checking whether the g++ linker
(/usr/i686-pc-linux-gnu/bin/ld) supports shared
libraries... yes
checking for g++ option to produce PIC... -fPIC
checking if g++ PIC flag -fPIC works... yes
checking if g++ supports -c -o file.o... yes
checking whether the g++ linker
(/usr/i686-pc-linux-gnu/bin/ld) supports shared
libraries... yes
checking dynamic linker characteristics... GNU/Linux ld.so
checking how to hardcode library paths into programs...
immediate
checking whether stripping libraries is possible... yes
appending configuration tag "F77" to libtool
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 >= 2.2... okay
checking for headers required to compile python
extensions... found
checking for pkg-config... /usr/bin/pkg-config
checking for GTK+ - version >= 2.0.0... yes (version 2.6.2)
checking for gtkextra-2.0 >= 1.1.0... yes
checking GTKEXTRA_CFLAGS... -DXTHREADS -D_REENTRANT
-DXUSE_MTSAFE_API -I/usr/local/include/gtkextra-2.0
-I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include
-I/usr/include/gtk-2.0 -I/usr/lib/gtk-2.0/include
-I/usr/X11R6/include -I/usr/include/atk-1.0
-I/usr/include/pango-1.0 -I/usr/include/freetype2
-I/usr/include/freetype2/config
checking GTKEXTRA_LIBS... -Wl,--export-dynamic
-L/usr/local/lib -lgtkextra-x11-2.0 -lgtk-x11-2.0
-lgdk-x11-2.0 -latk-1.0 -lgdk_pixbuf-2.0 -lm
-lpangoxft-1.0 -lpangox-1.0 -lpango-1.0 -lgobject-2.0
-lgmodule-2.0 -ldl -lglib-2.0
checking for pygtk-2.0 >= 1.99.8... yes
checking PYGTK_CFLAGS... -I/usr/include/pygtk-2.0
-I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include
checking PYGTK_LIBS... -lgobject-2.0 -lglib-2.0
checking PYGTK_DEFSDIR... /usr/share/pygtk/2.0/defs
checking arrayobject.h usability... no
checking arrayobject.h presence... yes
configure: WARNING: arrayobject.h: present but cannot
be compiled
configure: WARNING: arrayobject.h: check for
missing prerequisite headers?
configure: WARNING: arrayobject.h: see the Autoconf
documentation
configure: WARNING: arrayobject.h: section "Present
But Cannot Be Compiled"
configure: WARNING: arrayobject.h: proceeding with the
preprocessor's result
configure: WARNING: arrayobject.h: in the future, the
compiler will take precedence
configure: WARNING: ##
-------------------------------------------------------------
##
configure: WARNING: ## Report this to
http://sourceforge.net/tracker/?group_id=35371 ##
configure: WARNING: ##
-------------------------------------------------------------
##
checking for arrayobject.h... yes

[Toby D. Reeves]

Logged In: YES
user_id=91780

Does "./configure --disable-numpy" work?

[Roy Rankin]

Cannot reproduce and request for further info not supplied