[Openvas-devel] libpcap in openvas-libraries

[Bernhard Herzog]

On Friday 22 June 2007 12:27, Jan-Oliver Wagner wrote:
> Since no objections occured so far, I go for it and will remove
> libpcap-nessus.

Yesterday I found that both openvas-libnasl and openvas-server compile without 
problems if openvas-libraries is configured with --disable-nessuspcap.  The 
only problem I encountered was in openvas-libnasl whose configure script 
looks for pcap_restart, pcap_yyrestart, or yyrestart in the pcap library.  
pcap_restart is present in the libpcap-nessus but not in the libcap shipped 
with Debian etch.  AFAICT this is no problem as none of the restart functions 
are actually called anywhere in openvas-libnasl and the precompiler macro 
PCAP_RESTART defined by the configure check isn't referenced anywhere in the 
sources either.  I've simply removed the check from configure.in, regenerated 
configure and the configure/make/make install succeeded without problems.

Before I check that in, what's the policy on regenerating configure?  The 
version in SVN rev. 196 was generated by autoconf version 2.13.  The autoconf 
in etch has version 2.61 and the configure script generated by that is quite 
different from the on in SVN even if configure.in is not changed.

OTOH, when I run the autoconf of Debian sarge (which is version 2.13) I get a 
few warnings and the resulting configure script is slightly different from 
the one in SVN:

Index: configure
===================================================================
--- configure	(revision 234)
+++ configure	(working copy)
@@ -728,7 +728,7 @@
 
 
 test "x$prefix" != "xNONE" || prefix=/usr/local
-PATH=$DESTDIR${prefix}/bin:$PATH; export PATH
+PATH=${prefix}/bin:$PATH; export PATH
 
 
   Bernhard
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
Url : http://lists.wald.intevation.org/pipermail/openvas-devel/attachments/20070622/3092bc35/attachment.pgp