Bug #62
closedLibnet related configure.in issues
Description
I've found two problems with suricata configure{,.in}. The first
is in an error diagnostic (see attached patch), while the second is
that --with-libnet-includes doesn't appear to alter the definition of
libnet_dir, the list of candidate libnet include directories.
--- configure.in 2010-01-19 13:27:06.000000000 -0800
+++ configure.in.orig 2009-12-31 11:48:25.000000000 -0800@ -332,7 +332,7
@if test "$LIBNET_INC_DIR" != ""; then
if eval "grep LIBNET_VERSION $LIBNET_INC_DIR/libnet.h | grepv 1.1 >/dev/null"; thenFAIL_MESSAGE("libnet 1.1.x (libnet.h)", $libnet_dir)
+ FAIL_MESSAGE("libnet 1.1.x (libnet.h)", $tmp)
fi#CentOS, Fedora, Ubuntu-LTS, Ubuntu all set defines to the same values. libnet-config seems
--- configure 2010-01-19 12:47:10.0000000000800for i in `echo $libnet_dir`; do
++ configure.orig 2009-12-31 11:48:51.000000000 -0800@ -12935,7 +12935,7
@
echo "**********************************************"
echo " ERROR: unable to find" "libnet 1.1.x (libnet.h)"
echo " checked in the following places"
for i in `echo $tmp`; do
echo " $i"
done
echo "**********************************************"
Updated by Will Metcalf almost 15 years ago
- Status changed from New to Resolved
This was fixed in the libhtp integration patch and is currently part of master.
Updated by Will Metcalf almost 15 years ago
- Status changed from Resolved to Closed