Your message dated Tue, 8 Sep 2009 20:00:07 +0200
with message-id <200909082000.11250.w...@cyconet.org>
and subject line Re: [Openvas-distro-deb] Bug#545637: openvas-libraries: FTBFS:
configure: error: you need to install pcap library with development files
has caused the Debian Bug report #545637,
regarding openvas-libraries: FTBFS: configure: error: you need to install pcap
library with development files
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.)
--
545637: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=545637
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: openvas-libraries
Version: 2.0.4-1
Severity: serious
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20090907 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[2]: Entering directory
> `/build/user-openvas-libraries_2.0.4-1-amd64-Jt7JKR/openvas-libraries-2.0.4/libopenvas_hg'
> make[2]: Leaving directory
> `/build/user-openvas-libraries_2.0.4-1-amd64-Jt7JKR/openvas-libraries-2.0.4/libopenvas_hg'
> rm -f openvas-libraries.tmpl libopenvas-config libopenvas-config.pre
> rm -rf doc/generated
> make[1]: Leaving directory
> `/build/user-openvas-libraries_2.0.4-1-amd64-Jt7JKR/openvas-libraries-2.0.4'
> rm -f config.sub config.guess
> dh_clean
> dpkg-source -b openvas-libraries-2.0.4
> dpkg-source: info: using source format `1.0'
> dpkg-source: info: building openvas-libraries using existing
> openvas-libraries_2.0.4.orig.tar.gz
> dpkg-source: info: building openvas-libraries in
> openvas-libraries_2.0.4-1.diff.gz
> dpkg-source: warning: ignoring deletion of file config.sub
> dpkg-source: warning: ignoring deletion of file config.guess
> dpkg-source: info: building openvas-libraries in openvas-libraries_2.0.4-1.dsc
> debian/rules build
> test -d debian/patched || install -d debian/patched
> dpatch apply-all
> dpatch cat-all >>patch-stampT
> mv -f patch-stampT patch-stamp
> dh_testdir
> # Add here commands to configure the package.
> cp -f /usr/share/misc/config.sub config.sub
> cp -f /usr/share/misc/config.guess config.guess
> ./configure --build x86_64-linux-gnu --prefix=/usr
> --mandir=\${prefix}/share/man --infodir=\${prefix}/share/info
> --localstatedir=/var CFLAGS="-g -O2" LDFLAGS="-Wl,-z,defs"
> 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 ISO C89... none needed
> checking build system type... x86_64-pc-linux-gnu
> checking host system type... x86_64-pc-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 gcc... /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... 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 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 gcc object... ok
> checking for objdir... .libs
> checking for ar... ar
> checking for ranlib... ranlib
> checking for strip... strip
> 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 static flag -static works... yes
> checking if gcc supports -c -o file.o... yes
> checking whether the 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... 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 if the compiler understands -pipe... yes
> checking whether make sets $(MAKE)... yes
> checking for a BSD-compatible install... /usr/bin/install -c
> checking for pkg-config... /usr/bin/pkg-config
> checking pkg-config is at least version 0.9.0... yes
> checking for GLIB... yes
> checking gcrypt.h usability... yes
> checking gcrypt.h presence... yes
> checking for gcrypt.h... yes
> checking for dn_expand in -lresolv... no
> checking for __dn_expand in -lresolv... yes
> checking for gnutls_init in -lgnutls... yes
> checking for pcap_restart in -lpcap... no
> configure: error: you need to install pcap library with development files
> make: *** [config.status] Error 1
The full build log is available from:
http://people.debian.org/~lucas/logs/2009/09/07/openvas-libraries_2.0.4-1_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 |
--- End Message ---
--- Begin Message ---
Package: openvas-libraries
Version: 2.0.4-2
Hi Lucas,
On Tuesday, 8. September 2009, Lucas Nussbaum wrote:
> During a rebuild of all packages in sid, your package failed to build on
> amd64.
>
> Relevant part:
[...]
> > checking for pcap_restart in -lpcap... no
> > configure: error: you need to install pcap library with development files
> > make: *** [config.status] Error 1
>
> The full build log is available from:
>
> http://people.debian.org/~lucas/logs/2009/09/07/openvas-libraries_2.0.4-1_
> lsid64.buildlog
thanks for reporting the bug. I uploaded a package fixing the issue some
minutes before your mail arrived:
Changes:
openvas-libraries (2.0.4-2) unstable; urgency=medium
.
* Add README.source
* add 10_fix_llib.dpatch to remove llib to fix problems on mips
* add 10_fix_pcap_config.dpatch to get pcap recognized again
With kind regards, Jan.
--
Never write mail to <w...@spamfalle.info>, you have been warned!
-----BEGIN GEEK CODE BLOCK-----
Version: 3.1
GIT d-- s+: a- C+++ UL++++ P+ L+++ E- W+++ N+++ o++ K++ w--- O M V- PS PE
Y++ PGP++ t-- 5 X R tv- b+ DI- D++ G++ e++ h-- r+++ y+++
------END GEEK CODE BLOCK------
signature.asc
Description: This is a digitally signed message part.
--- End Message ---
