Your message dated Sun, 28 Jul 2013 20:52:09 +0200
with message-id <20130728185208.gg20...@ramacher.at>
and subject line Re: Bug#713187: python-gtkglext1: FTBFS: configure: error:
GtkGLExt not found
has caused the Debian Bug report #713187,
regarding python-gtkglext1: FTBFS: configure: error: GtkGLExt not found
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
713187: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=713187
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-gtkglext1
Version: 1.1.0-9.1
Severity: serious
Tags: jessie sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20130620 qa-ftbfs
Justification: FTBFS on amd64
Hi,
During a rebuild of all packages in sid, your package failed to build on
amd64.
Relevant part:
> debian/rules build
> dh_testdir
> dh_autoreconf
> aclocal: warning: autoconf input should be named 'configure.ac', not
> 'configure.in'
> acinclude.m4:4: warning: underquoted definition of AM_CHECK_PYMOD
> acinclude.m4:4: run info Automake 'Extending aclocal'
> acinclude.m4:4: or see
> http://www.gnu.org/software/automake/manual/automake.html#Extending-aclocal
> libtoolize: putting auxiliary files in `.'.
> libtoolize: copying file `./ltmain.sh'
> libtoolize: Consider adding `AC_CONFIG_MACRO_DIR([m4])' to configure.in and
> libtoolize: rerunning libtoolize, to keep the correct libtool macros in-tree.
> libtoolize: Consider adding `-I m4' to ACLOCAL_AMFLAGS in Makefile.am.
> aclocal: warning: autoconf input should be named 'configure.ac', not
> 'configure.in'
> acinclude.m4:4: warning: underquoted definition of AM_CHECK_PYMOD
> acinclude.m4:4: run info Automake 'Extending aclocal'
> acinclude.m4:4: or see
> http://www.gnu.org/software/automake/manual/automake.html#Extending-aclocal
> automake: warning: autoconf input should be named 'configure.ac', not
> 'configure.in'
> automake: warning: autoconf input should be named 'configure.ac', not
> 'configure.in'
> gtk/gdkgl/Makefile.am:14: warning: 'INCLUDES' is the old name for
> 'AM_CPPFLAGS' (or '*_CPPFLAGS')
> gtk/gtkgl/Makefile.am:14: warning: 'INCLUDES' is the old name for
> 'AM_CPPFLAGS' (or '*_CPPFLAGS')
> touch configure-stamp
> dh_testdir
> mkdir -p build-2.7
> cd build-2.7 && CFLAGS="-Wall -g -O2" PYTHON=/usr/bin/python2.7 ../configure
> --host=x86_64-linux-gnu --build=x86_64-linux-gnu \
> --prefix=/usr \
> --mandir=\${prefix}/share/man \
> --infodir=\${prefix}/share/info
> checking for a BSD-compatible install... /usr/bin/install -c
> checking whether build environment is sane... yes
> checking for a thread-safe mkdir -p... /bin/mkdir -p
> checking for gawk... no
> checking for mawk... mawk
> checking whether make sets $(MAKE)... yes
> checking whether make supports nested variables... yes
> checking whether to enable maintainer-specific portions of Makefiles... no
> checking build system type... x86_64-pc-linux-gnu
> checking host system type... x86_64-pc-linux-gnu
> checking for some Win32 platform... no
> checking for native Win32... no
> checking how to print strings... printf
> checking for style of include used by make... GNU
> checking for x86_64-linux-gnu-gcc... x86_64-linux-gnu-gcc
> checking whether the C compiler works... yes
> checking for C compiler default output file name... a.out
> checking for suffix of executables...
> checking whether we are cross compiling... no
> checking for suffix of object files... o
> checking whether we are using the GNU C compiler... yes
> checking whether x86_64-linux-gnu-gcc accepts -g... yes
> checking for x86_64-linux-gnu-gcc option to accept ISO C89... none needed
> checking dependency style of x86_64-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 fgrep... /bin/grep -F
> checking for ld used by x86_64-linux-gnu-gcc... /usr/bin/ld
> checking if the linker (/usr/bin/ld) is GNU ld... yes
> checking for BSD- or MS-compatible name lister (nm)... /usr/bin/nm -B
> checking the name lister (/usr/bin/nm -B) interface... BSD nm
> checking whether ln -s works... yes
> checking the maximum length of command line arguments... 3458764513820540925
> checking whether the shell understands some XSI constructs... yes
> checking whether the shell understands "+="... yes
> checking how to convert x86_64-pc-linux-gnu file names to x86_64-pc-linux-gnu
> format... func_convert_file_noop
> checking how to convert x86_64-pc-linux-gnu file names to toolchain format...
> func_convert_file_noop
> checking for /usr/bin/ld option to reload object files... -r
> checking for x86_64-linux-gnu-objdump... objdump
> checking how to recognize dependent libraries... pass_all
> checking for x86_64-linux-gnu-dlltool... dlltool
> checking how to associate runtime and link libraries... printf %s\n
> checking for x86_64-linux-gnu-ar... no
> checking for ar... ar
> checking for archiver @FILE support... @
> checking for x86_64-linux-gnu-strip... no
> checking for strip... strip
> checking for x86_64-linux-gnu-ranlib... no
> checking for ranlib... ranlib
> checking command to parse /usr/bin/nm -B output from x86_64-linux-gnu-gcc
> object... ok
> checking for sysroot... no
> checking for x86_64-linux-gnu-mt... no
> checking for mt... no
> checking if : is a manifest tool... no
> checking how to run the C preprocessor... x86_64-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 for dlfcn.h... yes
> checking for objdir... .libs
> checking if x86_64-linux-gnu-gcc supports -fno-rtti -fno-exceptions... no
> checking for x86_64-linux-gnu-gcc option to produce PIC... -fPIC -DPIC
> checking if x86_64-linux-gnu-gcc PIC flag -fPIC -DPIC works... yes
> checking if x86_64-linux-gnu-gcc static flag -static works... yes
> checking if x86_64-linux-gnu-gcc supports -c -o file.o... yes
> checking if x86_64-linux-gnu-gcc supports -c -o file.o... (cached) yes
> checking whether the x86_64-linux-gnu-gcc linker (/usr/bin/ld -m elf_x86_64)
> 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
> checking for python version... 2.7
> checking for python platform... linux2
> checking for python script directory... ${prefix}/lib/python2.7/dist-packages
> checking for python extension module directory...
> ${exec_prefix}/lib/python2.7/dist-packages
> checking for python >= 2.2... okay
> checking for headers required to compile python extensions... found
> checking for x86_64-linux-gnu-pkg-config... no
> checking for pkg-config... /usr/bin/pkg-config
> checking pkg-config is at least version 0.9.0... yes
> checking for PYGTK... yes
> checking for pygtk-codegen-2.0... /usr/bin/pygtk-codegen-2.0
> checking for pygtk defs... /usr/share/pygtk/2.0/defs
> ../configure: line 12255: ./libtool: No such file or directory
> checking for x86_64-linux-gnu-pkg-config... /usr/bin/pkg-config
> checking pkg-config is at least version 0.16... yes
> checking for GLIB - version >= 2.0.0... yes (version 2.36.3)
> checking for pkg-config... (cached) /usr/bin/pkg-config
> checking for GTK+ - version >= 2.0.0... yes (version 2.24.18)
> checking for pkg-config... (cached) /usr/bin/pkg-config
> Package pangox was not found in the pkg-config search path.
> Perhaps you should add the directory containing `pangox.pc'
> to the PKG_CONFIG_PATH environment variable
> Package 'pangox', required by 'GdkGLExt', not found
> Package pangox was not found in the pkg-config search path.
> Perhaps you should add the directory containing `pangox.pc'
> to the PKG_CONFIG_PATH environment variable
> Package 'pangox', required by 'GdkGLExt', not found
> checking for GtkGLExt - version >= 1.0.0... no
> *** Could not run GtkGLExt test program, checking why...
> *** The test program failed to compile or link. See the file config.log for
> the
> *** exact error that occured. This usually means GtkGLExt is incorrectly
> installed.
> configure: error: GtkGLExt not found
> make: *** [build-2.7/configure-stamp] Error 1
The full build log is available from:
http://aws-logs.debian.net/ftbfs-logs/2013/06/20/python-gtkglext1_1.1.0-9.1_unstable.log
A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!
About the archive rebuild: The rebuild was done on EC2 VM instances from
Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
failed build was retried once to eliminate random failures.
--- End Message ---
--- Begin Message ---
On 2013-06-22 14:08:08, Lucas Nussbaum wrote:
> Source: python-gtkglext1
> Version: 1.1.0-9.1
> Severity: serious
> Tags: jessie sid
> User: debian...@lists.debian.org
> Usertags: qa-ftbfs-20130620 qa-ftbfs
> Justification: FTBFS on amd64
>
> Hi,
>
> During a rebuild of all packages in sid, your package failed to build on
> amd64.
>
> Relevant part:
> > debian/rules build
> > dh_testdir
> > dh_autoreconf
> > aclocal: warning: autoconf input should be named 'configure.ac', not
> > 'configure.in'
> > acinclude.m4:4: warning: underquoted definition of AM_CHECK_PYMOD
> > acinclude.m4:4: run info Automake 'Extending aclocal'
> > acinclude.m4:4: or see
> > http://www.gnu.org/software/automake/manual/automake.html#Extending-aclocal
> > libtoolize: putting auxiliary files in `.'.
> > libtoolize: copying file `./ltmain.sh'
> > libtoolize: Consider adding `AC_CONFIG_MACRO_DIR([m4])' to configure.in and
> > libtoolize: rerunning libtoolize, to keep the correct libtool macros
> > in-tree.
> > libtoolize: Consider adding `-I m4' to ACLOCAL_AMFLAGS in Makefile.am.
> > aclocal: warning: autoconf input should be named 'configure.ac', not
> > 'configure.in'
> > acinclude.m4:4: warning: underquoted definition of AM_CHECK_PYMOD
> > acinclude.m4:4: run info Automake 'Extending aclocal'
> > acinclude.m4:4: or see
> > http://www.gnu.org/software/automake/manual/automake.html#Extending-aclocal
> > automake: warning: autoconf input should be named 'configure.ac', not
> > 'configure.in'
> > automake: warning: autoconf input should be named 'configure.ac', not
> > 'configure.in'
> > gtk/gdkgl/Makefile.am:14: warning: 'INCLUDES' is the old name for
> > 'AM_CPPFLAGS' (or '*_CPPFLAGS')
> > gtk/gtkgl/Makefile.am:14: warning: 'INCLUDES' is the old name for
> > 'AM_CPPFLAGS' (or '*_CPPFLAGS')
> > touch configure-stamp
> > dh_testdir
> > mkdir -p build-2.7
> > cd build-2.7 && CFLAGS="-Wall -g -O2" PYTHON=/usr/bin/python2.7
> > ../configure --host=x86_64-linux-gnu --build=x86_64-linux-gnu \
> > --prefix=/usr \
> > --mandir=\${prefix}/share/man \
> > --infodir=\${prefix}/share/info
> > checking for a BSD-compatible install... /usr/bin/install -c
> > checking whether build environment is sane... yes
> > checking for a thread-safe mkdir -p... /bin/mkdir -p
> > checking for gawk... no
> > checking for mawk... mawk
> > checking whether make sets $(MAKE)... yes
> > checking whether make supports nested variables... yes
> > checking whether to enable maintainer-specific portions of Makefiles... no
> > checking build system type... x86_64-pc-linux-gnu
> > checking host system type... x86_64-pc-linux-gnu
> > checking for some Win32 platform... no
> > checking for native Win32... no
> > checking how to print strings... printf
> > checking for style of include used by make... GNU
> > checking for x86_64-linux-gnu-gcc... x86_64-linux-gnu-gcc
> > checking whether the C compiler works... yes
> > checking for C compiler default output file name... a.out
> > checking for suffix of executables...
> > checking whether we are cross compiling... no
> > checking for suffix of object files... o
> > checking whether we are using the GNU C compiler... yes
> > checking whether x86_64-linux-gnu-gcc accepts -g... yes
> > checking for x86_64-linux-gnu-gcc option to accept ISO C89... none needed
> > checking dependency style of x86_64-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 fgrep... /bin/grep -F
> > checking for ld used by x86_64-linux-gnu-gcc... /usr/bin/ld
> > checking if the linker (/usr/bin/ld) is GNU ld... yes
> > checking for BSD- or MS-compatible name lister (nm)... /usr/bin/nm -B
> > checking the name lister (/usr/bin/nm -B) interface... BSD nm
> > checking whether ln -s works... yes
> > checking the maximum length of command line arguments... 3458764513820540925
> > checking whether the shell understands some XSI constructs... yes
> > checking whether the shell understands "+="... yes
> > checking how to convert x86_64-pc-linux-gnu file names to
> > x86_64-pc-linux-gnu format... func_convert_file_noop
> > checking how to convert x86_64-pc-linux-gnu file names to toolchain
> > format... func_convert_file_noop
> > checking for /usr/bin/ld option to reload object files... -r
> > checking for x86_64-linux-gnu-objdump... objdump
> > checking how to recognize dependent libraries... pass_all
> > checking for x86_64-linux-gnu-dlltool... dlltool
> > checking how to associate runtime and link libraries... printf %s\n
> > checking for x86_64-linux-gnu-ar... no
> > checking for ar... ar
> > checking for archiver @FILE support... @
> > checking for x86_64-linux-gnu-strip... no
> > checking for strip... strip
> > checking for x86_64-linux-gnu-ranlib... no
> > checking for ranlib... ranlib
> > checking command to parse /usr/bin/nm -B output from x86_64-linux-gnu-gcc
> > object... ok
> > checking for sysroot... no
> > checking for x86_64-linux-gnu-mt... no
> > checking for mt... no
> > checking if : is a manifest tool... no
> > checking how to run the C preprocessor... x86_64-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 for dlfcn.h... yes
> > checking for objdir... .libs
> > checking if x86_64-linux-gnu-gcc supports -fno-rtti -fno-exceptions... no
> > checking for x86_64-linux-gnu-gcc option to produce PIC... -fPIC -DPIC
> > checking if x86_64-linux-gnu-gcc PIC flag -fPIC -DPIC works... yes
> > checking if x86_64-linux-gnu-gcc static flag -static works... yes
> > checking if x86_64-linux-gnu-gcc supports -c -o file.o... yes
> > checking if x86_64-linux-gnu-gcc supports -c -o file.o... (cached) yes
> > checking whether the x86_64-linux-gnu-gcc linker (/usr/bin/ld -m
> > elf_x86_64) 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
> > checking for python version... 2.7
> > checking for python platform... linux2
> > checking for python script directory...
> > ${prefix}/lib/python2.7/dist-packages
> > checking for python extension module directory...
> > ${exec_prefix}/lib/python2.7/dist-packages
> > checking for python >= 2.2... okay
> > checking for headers required to compile python extensions... found
> > checking for x86_64-linux-gnu-pkg-config... no
> > checking for pkg-config... /usr/bin/pkg-config
> > checking pkg-config is at least version 0.9.0... yes
> > checking for PYGTK... yes
> > checking for pygtk-codegen-2.0... /usr/bin/pygtk-codegen-2.0
> > checking for pygtk defs... /usr/share/pygtk/2.0/defs
> > ../configure: line 12255: ./libtool: No such file or directory
> > checking for x86_64-linux-gnu-pkg-config... /usr/bin/pkg-config
> > checking pkg-config is at least version 0.16... yes
> > checking for GLIB - version >= 2.0.0... yes (version 2.36.3)
> > checking for pkg-config... (cached) /usr/bin/pkg-config
> > checking for GTK+ - version >= 2.0.0... yes (version 2.24.18)
> > checking for pkg-config... (cached) /usr/bin/pkg-config
> > Package pangox was not found in the pkg-config search path.
> > Perhaps you should add the directory containing `pangox.pc'
> > to the PKG_CONFIG_PATH environment variable
> > Package 'pangox', required by 'GdkGLExt', not found
> > Package pangox was not found in the pkg-config search path.
> > Perhaps you should add the directory containing `pangox.pc'
> > to the PKG_CONFIG_PATH environment variable
> > Package 'pangox', required by 'GdkGLExt', not found
> > checking for GtkGLExt - version >= 1.0.0... no
> > *** Could not run GtkGLExt test program, checking why...
> > *** The test program failed to compile or link. See the file config.log for
> > the
> > *** exact error that occured. This usually means GtkGLExt is incorrectly
> > installed.
> > configure: error: GtkGLExt not found
> > make: *** [build-2.7/configure-stamp] Error 1
The error was caused by #709554 which is now fixed. python-gtkglext1 builds fine
again. Closing.
Regards
--
Sebastian Ramacher
signature.asc
Description: Digital signature
--- End Message ---
