The leading comma looked weird; remove it.

That might be how the --disable-canusb bug got in.  Hopefully this will
make the code look a little clearer and possibly avoid future bugs of
that sort.

diff --git a/configure.in b/configure.in
index d8554ca56ef3fd9c02d64a2524de0b46a42f15a3..ba5b64e60f93eb9f78cf6b5fa60920c4d93d7510 100644 (file)
--- a/configure.in
+++ b/configure.in
@@ -1371,7 +1371,8 @@ AC_SUBST(NETFILTER_SRC)
 
 AC_ARG_ENABLE([bluetooth],
 [AC_HELP_STRING([--enable-bluetooth],[enable Bluetooth support @<:@default=yes, if support available@:>@])],
-,enable_bluetooth=yes)
+    [],
+    [enable_bluetooth=yes])
 
 if test "x$enable_bluetooth" != "xno" ; then
        dnl check for Bluetooth sniffing support
@@ -1396,7 +1397,8 @@ fi
 
 AC_ARG_ENABLE([canusb],
 [AC_HELP_STRING([--enable-canusb],[enable canusb support @<:@default=yes, if support available@:>@])],
-,enable_canusb=yes)
+    [],
+    [enable_canusb=yes])
 
 if test "x$enable_canusb" != "xno" ; then
        dnl check for canusb support
@@ -1422,7 +1424,8 @@ fi
 
 AC_ARG_ENABLE([can],
 [AC_HELP_STRING([--enable-can],[enable CAN support @<:@default=yes, if support available@:>@])],
-,enable_can=yes)
+    [],
+    [enable_can=yes])
 
 if test "x$enable_can" != "xno" ; then
        dnl check for CAN sniffing support