Source: java-access-bridge
Version: 1.26.2-3
Severity: serious
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20091117 qa-ftbfs
Justification: FTBFS on amd64
Hi,
During a rebuild of all packages in sid, your package failed to build on
amd64.
Relevant part:
> make[1]: Entering directory
> `/build/user-java-access-bridge_1.26.2-3-amd64-Vg6Kqg/java-access-bridge-1.26.2'
> make[1]: *** No rule to make target `distclean'.
> make[1]: Leaving directory
> `/build/user-java-access-bridge_1.26.2-3-amd64-Vg6Kqg/java-access-bridge-1.26.2'
> make: [makefile-clean] Error 2 (ignored)
> rm -f debian/stamp-makefile-build
> for i in ./config.guess ./config.sub ; do \
> if test -e $i.cdbs-orig ; then \
> mv $i.cdbs-orig $i ; \
> fi ; \
> done
> dh_clean
> rm -f debian/stamp-autotools-files
> dpkg-source -b java-access-bridge-1.26.2
> dpkg-source: info: using source format `1.0'
> dpkg-source: info: building java-access-bridge using existing
> java-access-bridge_1.26.2.orig.tar.gz
> dpkg-source: info: building java-access-bridge in
> java-access-bridge_1.26.2-3.diff.gz
> dpkg-source: info: building java-access-bridge in
> java-access-bridge_1.26.2-3.dsc
> debian/rules build
> test -x debian/rules
> mkdir -p "."
> if test -e /usr/share/misc/config.guess ; then \
> for i in ./config.guess ; do \
> if ! test -e $i.cdbs-orig ; then \
> mv $i $i.cdbs-orig ; \
> cp --remove-destination
> /usr/share/misc/config.guess $i ; \
> fi ; \
> done ; \
> fi
> if test -e /usr/share/misc/config.sub ; then \
> for i in ./config.sub ; do \
> if ! test -e $i.cdbs-orig ; then \
> mv $i $i.cdbs-orig ; \
> cp --remove-destination
> /usr/share/misc/config.sub $i ; \
> fi ; \
> done ; \
> fi
> touch debian/stamp-autotools-files
> chmod a+x
> /build/user-java-access-bridge_1.26.2-3-amd64-Vg6Kqg/java-access-bridge-1.26.2/./configure
> cd . && CC="cc" CXX="g++" CFLAGS="-g -O2 -g -Wall -O2" CXXFLAGS="-g -O2 -g
> -Wall -O2" CPPFLAGS="" LDFLAGS=""
> /build/user-java-access-bridge_1.26.2-3-amd64-Vg6Kqg/java-access-bridge-1.26.2/./configure
> --build=x86_64-linux-gnu --prefix=/usr --includedir="\${prefix}/include"
> --mandir="\${prefix}/share/man" --infodir="\${prefix}/share/info"
> --sysconfdir=/etc --localstatedir=/var
> --libexecdir="\${prefix}/lib/java-access-bridge" --disable-maintainer-mode
> --disable-dependency-tracking --disable-silent-rules --srcdir=.
> 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... gawk
> checking whether make sets $(MAKE)... yes
> checking for "/usr/lib/jvm/java-6-openjdk/bin/java"... yes
> checking for gcc... cc
> 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 cc accepts -g... yes
> checking for cc option to accept ISO C89... none needed
> checking for style of include used by make... GNU
> checking dependency style of cc... none
> checking for a BSD-compatible install... /usr/bin/install -c
> checking for strerror in -lcposix... no
> /build/user-java-access-bridge_1.26.2-3-amd64-Vg6Kqg/java-access-bridge-1.26.2/./configure:
> line 3881: test: =: unary operator expected
> checking build system type... x86_64-pc-linux-gnu
> checking host system type... x86_64-pc-linux-gnu
> checking platform to setup platform specific variables... linux-gnu
> 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 cc... /usr/bin/ld
> checking if the linker (/usr/bin/ld) is GNU ld... yes
> checking for /usr/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... cc -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 whether we are using the GNU C++ compiler... yes
> checking whether g++ accepts -g... yes
> checking dependency style of g++... none
> checking how to run the C++ preprocessor... g++ -E
> checking for g77... no
> checking for xlf... no
> checking for f77... no
> checking for frt... no
> checking for pgf77... no
> checking for cf77... no
> checking for fort77... no
> checking for fl32... no
> checking for af77... no
> checking for xlf90... no
> checking for f90... no
> checking for pgf90... no
> checking for pghpf... no
> checking for epcf90... no
> checking for gfortran... no
> checking for g95... no
> checking for xlf95... no
> checking for f95... no
> checking for fort... no
> checking for ifort... no
> checking for ifc... no
> checking for efc... no
> checking for pgf95... no
> checking for lf95... no
> checking for ftn... 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 cc object... ok
> checking for objdir... .libs
> checking for ar... ar
> checking for ranlib... ranlib
> checking for strip... strip
> checking if cc supports -fno-rtti -fno-exceptions... no
> checking for cc option to produce PIC... -fPIC
> checking if cc PIC flag -fPIC works... yes
> checking if cc static flag -static works... yes
> checking if cc supports -c -o file.o... yes
> checking whether the cc 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... yes
> configure: creating libtool
> appending configuration tag "CXX" to libtool
> checking for ld used by g++... /usr/bin/ld -m elf_x86_64
> checking if the linker (/usr/bin/ld -m elf_x86_64) is GNU ld... yes
> checking whether the g++ linker (/usr/bin/ld -m elf_x86_64) supports shared
> libraries... yes
> checking for g++ option to produce PIC... -fPIC
> checking if g++ PIC flag -fPIC works... yes
> checking if g++ static flag -static works... yes
> checking if g++ supports -c -o file.o... yes
> checking whether the g++ linker (/usr/bin/ld -m elf_x86_64) supports shared
> libraries... yes
> checking dynamic linker characteristics... GNU/Linux ld.so
> checking how to hardcode library paths into programs... immediate
> appending configuration tag "F77" to libtool
> checking for pkg-config... /usr/bin/pkg-config
> checking pkg-config is at least version 0.9.0... yes
> configure: error: Package requirements (
> gtk+-2.0 >= 1.17.0
> ) were not met:
>
> No package 'gtk+-2.0' found
>
> Consider adjusting the PKG_CONFIG_PATH environment variable if you
> installed software in a non-standard prefix.
>
> Alternatively, you may set the environment variables GTK_CFLAGS
> and GTK_LIBS to avoid the need to call pkg-config.
> See the pkg-config man page for more details.
>
> make: *** [config.status] Error 1
The full build log is available from:
http://people.debian.org/~lucas/logs/2009/11/17/java-access-bridge_1.26.2-3_lsid64.buildlog
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 about 50 AMD64 nodes
of the Grid'5000 platform, using a clean chroot. Internet was not
accessible from the build systems.
--
| Lucas Nussbaum
| lu...@lucas-nussbaum.net http://www.lucas-nussbaum.net/ |
| jabber: lu...@nussbaum.fr GPG: 1024D/023B3F4F |
_______________________________________________
pkg-java-maintainers mailing list
pkg-java-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/mailman/listinfo/pkg-java-maintainers
