mirrors/tcpdump
0
0
Fork 0
mirror of https://github.com/the-tcpdump-group/tcpdump.git synced 2024-11-27 12:03:44 +08:00
Code Issues Packages Projects Releases Wiki Activity
55e0de4ea1
tcpdump/configure

9009 lines
243 KiB
Plaintext
Raw Normal View History

Initial revision
1999-10-08 07:47:09 +08:00
#! /bin/sh
Regenerate with autoconf 2.57.
2004-01-14 11:15:08 +08:00
# Guess values for system-dependent variables and create Makefiles.
Do the version number the way it's now done for libpcap. Use the two-argument version of AC_INIT() - which requires autoconf 2.64 or later, so require that as a minimum - and get the version string from the VERSION file. Use AC_CONFIG_SRCDIR() to say that the source directory needs tcpdump.c; the two-argument version of AC_INIT() doesn't do that. This means that we no longer have a version.c file.
2017-10-17 05:31:14 +08:00
# Generated by GNU Autoconf 2.69 for tcpdump 4.10.0-PRE-GIT.
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
#
#
# Copyright (C) 1992-1996, 1998-2012 Free Software Foundation, Inc.
#
Some versions of the HP C compiler can handle inlines, but not if they return a structure pointer. Check whether the C compiler can handle inline functions that return a structure pointer, not whether they can handle inline functions that return an int, as at least some versions of autoconf's AC_C_INLINE do.
2002-06-28 18:45:40 +08:00
#
Regenerate with autoconf 2.57.
2004-01-14 11:15:08 +08:00
# This configure script is free software; the Free Software Foundation
# gives unlimited permission to copy, distribute and modify it.
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
## -------------------- ##
## M4sh Initialization. ##
## -------------------- ##
Some versions of the HP C compiler can handle inlines, but not if they return a structure pointer. Check whether the C compiler can handle inline functions that return a structure pointer, not whether they can handle inline functions that return an int, as at least some versions of autoconf's AC_C_INLINE do.
2002-06-28 18:45:40 +08:00
We support building tcpdump with versions of libpcap other than the one with which it was released, and DLT_BLUETOOTH_HCI_H4_WITH_PHDR might be defined by pcap-bpf.h without pcap/bluetooth.h being present (as appears to be the case on Fedora 9, for example), so check whether <pcap/bluetooth.h> is usable. Update a comment - F9 appears to have a "/usr/include/pcap.h" if you install the libpcap headers. When adding -I flags when running a compiler-based test, add them to CPPFLAGS, not CFLAGS - the latter doesn't work right with AC_CHECK_HEADERS, as the "gcc -E" run doesn't have the -I flags added.
2008-09-26 05:45:50 +08:00
# Be more Bourne compatible
DUALCASE=1; export DUALCASE # for MKS sh
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
if test -n "${ZSH_VERSION+set}" && (emulate sh) >/dev/null 2>&1; then :
From Andrew Church <andrew@users.sourceforge.net>: when testing for "pcap_version", "pcap_debug", and "yydebug", don't add our own functions referring to those variables - GCC 3.4.1 optimizes the test code out before the link is done, as it's in a function that's not called.
2004-08-27 15:17:03 +08:00
emulate sh
NULLCMD=:
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
# Pre-4.2 versions of Zsh do word splitting on ${1+"$@"}, which
From Andrew Church <andrew@users.sourceforge.net>: when testing for "pcap_version", "pcap_debug", and "yydebug", don't add our own functions referring to those variables - GCC 3.4.1 optimizes the test code out before the link is done, as it's in a function that's not called.
2004-08-27 15:17:03 +08:00
# is contrary to our usage. Disable this feature.
alias -g '${1+"$@"}'='"$@"'
We support building tcpdump with versions of libpcap other than the one with which it was released, and DLT_BLUETOOTH_HCI_H4_WITH_PHDR might be defined by pcap-bpf.h without pcap/bluetooth.h being present (as appears to be the case on Fedora 9, for example), so check whether <pcap/bluetooth.h> is usable. Update a comment - F9 appears to have a "/usr/include/pcap.h" if you install the libpcap headers. When adding -I flags when running a compiler-based test, add them to CPPFLAGS, not CFLAGS - the latter doesn't work right with AC_CHECK_HEADERS, as the "gcc -E" run doesn't have the -I flags added.
2008-09-26 05:45:50 +08:00
setopt NO_GLOB_SUBST
else
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
case `(set -o) 2>/dev/null` in #(
*posix*) :
set -o posix ;; #(
*) :
;;
We support building tcpdump with versions of libpcap other than the one with which it was released, and DLT_BLUETOOTH_HCI_H4_WITH_PHDR might be defined by pcap-bpf.h without pcap/bluetooth.h being present (as appears to be the case on Fedora 9, for example), so check whether <pcap/bluetooth.h> is usable. Update a comment - F9 appears to have a "/usr/include/pcap.h" if you install the libpcap headers. When adding -I flags when running a compiler-based test, add them to CPPFLAGS, not CFLAGS - the latter doesn't work right with AC_CHECK_HEADERS, as the "gcc -E" run doesn't have the -I flags added.
2008-09-26 05:45:50 +08:00
esac
fi
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
as_nl='
'
export as_nl
# Printing a long string crashes Solaris 7 /usr/bin/printf.
as_echo='\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\'
as_echo=$as_echo$as_echo$as_echo$as_echo$as_echo
as_echo=$as_echo$as_echo$as_echo$as_echo$as_echo$as_echo
# Prefer a ksh shell builtin over an external printf program on Solaris,
# but without wasting forks for bash or zsh.
if test -z "$BASH_VERSION$ZSH_VERSION" \
&& (test "X`print -r -- $as_echo`" = "X$as_echo") 2>/dev/null; then
as_echo='print -r --'
as_echo_n='print -rn --'
elif (test "X`printf %s $as_echo`" = "X$as_echo") 2>/dev/null; then
as_echo='printf %s\n'
as_echo_n='printf %s'
else
if test "X`(/usr/ucb/echo -n -n $as_echo) 2>/dev/null`" = "X-n $as_echo"; then
as_echo_body='eval /usr/ucb/echo -n "$1$as_nl"'
as_echo_n='/usr/ucb/echo -n'
We support building tcpdump with versions of libpcap other than the one with which it was released, and DLT_BLUETOOTH_HCI_H4_WITH_PHDR might be defined by pcap-bpf.h without pcap/bluetooth.h being present (as appears to be the case on Fedora 9, for example), so check whether <pcap/bluetooth.h> is usable. Update a comment - F9 appears to have a "/usr/include/pcap.h" if you install the libpcap headers. When adding -I flags when running a compiler-based test, add them to CPPFLAGS, not CFLAGS - the latter doesn't work right with AC_CHECK_HEADERS, as the "gcc -E" run doesn't have the -I flags added.
2008-09-26 05:45:50 +08:00
else
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
as_echo_body='eval expr "X$1" : "X\\(.*\\)"'
as_echo_n_body='eval
arg=$1;
case $arg in #(
*"$as_nl"*)
expr "X$arg" : "X\\(.*\\)$as_nl";
arg=`expr "X$arg" : ".*$as_nl\\(.*\\)"`;;
esac;
expr "X$arg" : "X\\(.*\\)" | tr -d "$as_nl"
'
export as_echo_n_body
as_echo_n='sh -c $as_echo_n_body as_echo'
We support building tcpdump with versions of libpcap other than the one with which it was released, and DLT_BLUETOOTH_HCI_H4_WITH_PHDR might be defined by pcap-bpf.h without pcap/bluetooth.h being present (as appears to be the case on Fedora 9, for example), so check whether <pcap/bluetooth.h> is usable. Update a comment - F9 appears to have a "/usr/include/pcap.h" if you install the libpcap headers. When adding -I flags when running a compiler-based test, add them to CPPFLAGS, not CFLAGS - the latter doesn't work right with AC_CHECK_HEADERS, as the "gcc -E" run doesn't have the -I flags added.
2008-09-26 05:45:50 +08:00
fi
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
export as_echo_body
as_echo='sh -c $as_echo_body as_echo'
From Andrew Church <andrew@users.sourceforge.net>: when testing for "pcap_version", "pcap_debug", and "yydebug", don't add our own functions referring to those variables - GCC 3.4.1 optimizes the test code out before the link is done, as it's in a function that's not called.
2004-08-27 15:17:03 +08:00
fi
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
# The user is always right.
if test "${PATH_SEPARATOR+set}" != set; then
PATH_SEPARATOR=:
(PATH='/bin;/bin'; FPATH=$PATH; sh -c :) >/dev/null 2>&1 && {
(PATH='/bin:/bin'; FPATH=$PATH; sh -c :) >/dev/null 2>&1 ||
PATH_SEPARATOR=';'
}
From Andrew Church <andrew@users.sourceforge.net>: when testing for "pcap_version", "pcap_debug", and "yydebug", don't add our own functions referring to those variables - GCC 3.4.1 optimizes the test code out before the link is done, as it's in a function that's not called.
2004-08-27 15:17:03 +08:00
fi
We support building tcpdump with versions of libpcap other than the one with which it was released, and DLT_BLUETOOTH_HCI_H4_WITH_PHDR might be defined by pcap-bpf.h without pcap/bluetooth.h being present (as appears to be the case on Fedora 9, for example), so check whether <pcap/bluetooth.h> is usable. Update a comment - F9 appears to have a "/usr/include/pcap.h" if you install the libpcap headers. When adding -I flags when running a compiler-based test, add them to CPPFLAGS, not CFLAGS - the latter doesn't work right with AC_CHECK_HEADERS, as the "gcc -E" run doesn't have the -I flags added.
2008-09-26 05:45:50 +08:00
# IFS
# We need space, tab and new line, in precisely that order. Quoting is
# there to prevent editors from complaining about space-tab.
# (If _AS_PATH_WALK were called with IFS unset, it would disable word
# splitting by setting IFS to empty value.)
IFS=" "" $as_nl"
# Find who we are. Look in the path if we contain no directory separator.
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
as_myself=
case $0 in #((
We support building tcpdump with versions of libpcap other than the one with which it was released, and DLT_BLUETOOTH_HCI_H4_WITH_PHDR might be defined by pcap-bpf.h without pcap/bluetooth.h being present (as appears to be the case on Fedora 9, for example), so check whether <pcap/bluetooth.h> is usable. Update a comment - F9 appears to have a "/usr/include/pcap.h" if you install the libpcap headers. When adding -I flags when running a compiler-based test, add them to CPPFLAGS, not CFLAGS - the latter doesn't work right with AC_CHECK_HEADERS, as the "gcc -E" run doesn't have the -I flags added.
2008-09-26 05:45:50 +08:00
*[\\/]* ) as_myself=$0 ;;
*) as_save_IFS=$IFS; IFS=$PATH_SEPARATOR
for as_dir in $PATH
do
IFS=$as_save_IFS
test -z "$as_dir" && as_dir=.
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
test -r "$as_dir/$0" && as_myself=$as_dir/$0 && break
done
We support building tcpdump with versions of libpcap other than the one with which it was released, and DLT_BLUETOOTH_HCI_H4_WITH_PHDR might be defined by pcap-bpf.h without pcap/bluetooth.h being present (as appears to be the case on Fedora 9, for example), so check whether <pcap/bluetooth.h> is usable. Update a comment - F9 appears to have a "/usr/include/pcap.h" if you install the libpcap headers. When adding -I flags when running a compiler-based test, add them to CPPFLAGS, not CFLAGS - the latter doesn't work right with AC_CHECK_HEADERS, as the "gcc -E" run doesn't have the -I flags added.
2008-09-26 05:45:50 +08:00
IFS=$as_save_IFS
;;
esac
# We did not find ourselves, most probably we were run as `sh COMMAND'
# in which case we are not to be found in the path.
if test "x$as_myself" = x; then
as_myself=$0
fi
if test ! -f "$as_myself"; then
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
$as_echo "$as_myself: error: cannot find myself; rerun with an absolute file name" >&2
exit 1
We support building tcpdump with versions of libpcap other than the one with which it was released, and DLT_BLUETOOTH_HCI_H4_WITH_PHDR might be defined by pcap-bpf.h without pcap/bluetooth.h being present (as appears to be the case on Fedora 9, for example), so check whether <pcap/bluetooth.h> is usable. Update a comment - F9 appears to have a "/usr/include/pcap.h" if you install the libpcap headers. When adding -I flags when running a compiler-based test, add them to CPPFLAGS, not CFLAGS - the latter doesn't work right with AC_CHECK_HEADERS, as the "gcc -E" run doesn't have the -I flags added.
2008-09-26 05:45:50 +08:00
fi
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
# Unset variables that we do not need and which cause bugs (e.g. in
# pre-3.0 UWIN ksh). But do not cause bugs in bash 2.01; the "|| exit 1"
# suppresses any "Segmentation fault" message there. '((' could
# trigger a bug in pdksh 5.2.14.
for as_var in BASH_ENV ENV MAIL MAILPATH
do eval test x\${$as_var+set} = xset \
&& ( (unset $as_var) || exit 1) >/dev/null 2>&1 && unset $as_var || :
We support building tcpdump with versions of libpcap other than the one with which it was released, and DLT_BLUETOOTH_HCI_H4_WITH_PHDR might be defined by pcap-bpf.h without pcap/bluetooth.h being present (as appears to be the case on Fedora 9, for example), so check whether <pcap/bluetooth.h> is usable. Update a comment - F9 appears to have a "/usr/include/pcap.h" if you install the libpcap headers. When adding -I flags when running a compiler-based test, add them to CPPFLAGS, not CFLAGS - the latter doesn't work right with AC_CHECK_HEADERS, as the "gcc -E" run doesn't have the -I flags added.
2008-09-26 05:45:50 +08:00
done
From Andrew Church <andrew@users.sourceforge.net>: when testing for "pcap_version", "pcap_debug", and "yydebug", don't add our own functions referring to those variables - GCC 3.4.1 optimizes the test code out before the link is done, as it's in a function that's not called.
2004-08-27 15:17:03 +08:00
PS1='$ '
PS2='> '
PS4='+ '
# NLS nuisances.
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
LC_ALL=C
export LC_ALL
LANGUAGE=C
export LANGUAGE
# CDPATH.
(unset CDPATH) >/dev/null 2>&1 && unset CDPATH
# Use a proper internal environment variable to ensure we don't fall
# into an infinite loop, continuously re-executing ourselves.
if test x"${_as_can_reexec}" != xno && test "x$CONFIG_SHELL" != x; then
_as_can_reexec=no; export _as_can_reexec;
# We cannot yet assume a decent shell, so we have to provide a
# neutralization value for shells without unset; and this also
# works around shells that cannot unset nonexistent variables.
# Preserve -v and -x to the replacement shell.
BASH_ENV=/dev/null
ENV=/dev/null
(unset BASH_ENV) >/dev/null 2>&1 && unset BASH_ENV ENV
case $- in # ((((
*v*x* | *x*v* ) as_opts=-vx ;;
*v* ) as_opts=-v ;;
*x* ) as_opts=-x ;;
* ) as_opts= ;;
esac
exec $CONFIG_SHELL $as_opts "$as_myself" ${1+"$@"}
# Admittedly, this is quite paranoid, since all the known shells bail
# out after a failed `exec'.
$as_echo "$0: could not re-execute with $CONFIG_SHELL" >&2
as_fn_exit 255
fi
# We don't want this to propagate to other subprocesses.
{ _as_can_reexec=; unset _as_can_reexec;}
if test "x$CONFIG_SHELL" = x; then
as_bourne_compatible="if test -n \"\${ZSH_VERSION+set}\" && (emulate sh) >/dev/null 2>&1; then :
emulate sh
NULLCMD=:
# Pre-4.2 versions of Zsh do word splitting on \${1+\"\$@\"}, which
# is contrary to our usage. Disable this feature.
alias -g '\${1+\"\$@\"}'='\"\$@\"'
setopt NO_GLOB_SUBST
else
case \`(set -o) 2>/dev/null\` in #(
*posix*) :
set -o posix ;; #(
*) :
;;
esac
fi
"
as_required="as_fn_return () { (exit \$1); }
as_fn_success () { as_fn_return 0; }
as_fn_failure () { as_fn_return 1; }
as_fn_ret_success () { return 0; }
as_fn_ret_failure () { return 1; }
exitcode=0
as_fn_success || { exitcode=1; echo as_fn_success failed.; }
as_fn_failure && { exitcode=1; echo as_fn_failure succeeded.; }
as_fn_ret_success || { exitcode=1; echo as_fn_ret_success failed.; }
as_fn_ret_failure && { exitcode=1; echo as_fn_ret_failure succeeded.; }
if ( set x; as_fn_ret_success y && test x = \"\$1\" ); then :
else
exitcode=1; echo positional parameters were not saved.
fi
test x\$exitcode = x0 || exit 1
test -x / || exit 1"
as_suggested=" as_lineno_1=";as_suggested=$as_suggested$LINENO;as_suggested=$as_suggested" as_lineno_1a=\$LINENO
as_lineno_2=";as_suggested=$as_suggested$LINENO;as_suggested=$as_suggested" as_lineno_2a=\$LINENO
eval 'test \"x\$as_lineno_1'\$as_run'\" != \"x\$as_lineno_2'\$as_run'\" &&
test \"x\`expr \$as_lineno_1'\$as_run' + 1\`\" = \"x\$as_lineno_2'\$as_run'\"' || exit 1
test \$(( 1 + 1 )) = 2 || exit 1"
if (eval "$as_required") 2>/dev/null; then :
as_have_required=yes
else
as_have_required=no
fi
if test x$as_have_required = xyes && (eval "$as_suggested") 2>/dev/null; then :
else
as_save_IFS=$IFS; IFS=$PATH_SEPARATOR
as_found=false
for as_dir in /bin$PATH_SEPARATOR/usr/bin$PATH_SEPARATOR$PATH
From Andrew Church <andrew@users.sourceforge.net>: when testing for "pcap_version", "pcap_debug", and "yydebug", don't add our own functions referring to those variables - GCC 3.4.1 optimizes the test code out before the link is done, as it's in a function that's not called.
2004-08-27 15:17:03 +08:00
do
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
IFS=$as_save_IFS
test -z "$as_dir" && as_dir=.
as_found=:
case $as_dir in #(
/*)
for as_base in sh bash ksh sh5; do
# Try only shells that exist, to save several forks.
as_shell=$as_dir/$as_base
if { test -f "$as_shell" || test -f "$as_shell.exe"; } &&
{ $as_echo "$as_bourne_compatible""$as_required" | as_run=a "$as_shell"; } 2>/dev/null; then :
CONFIG_SHELL=$as_shell as_have_required=yes
if { $as_echo "$as_bourne_compatible""$as_suggested" | as_run=a "$as_shell"; } 2>/dev/null; then :
break 2
fi
fi
done;;
esac
as_found=false
done
$as_found || { if { test -f "$SHELL" || test -f "$SHELL.exe"; } &&
{ $as_echo "$as_bourne_compatible""$as_required" | as_run=a "$SHELL"; } 2>/dev/null; then :
CONFIG_SHELL=$SHELL as_have_required=yes
fi; }
IFS=$as_save_IFS
if test "x$CONFIG_SHELL" != x; then :
export CONFIG_SHELL
# We cannot yet assume a decent shell, so we have to provide a
# neutralization value for shells without unset; and this also
# works around shells that cannot unset nonexistent variables.
# Preserve -v and -x to the replacement shell.
BASH_ENV=/dev/null
ENV=/dev/null
(unset BASH_ENV) >/dev/null 2>&1 && unset BASH_ENV ENV
case $- in # ((((
*v*x* | *x*v* ) as_opts=-vx ;;
*v* ) as_opts=-v ;;
*x* ) as_opts=-x ;;
* ) as_opts= ;;
esac
exec $CONFIG_SHELL $as_opts "$as_myself" ${1+"$@"}
# Admittedly, this is quite paranoid, since all the known shells bail
# out after a failed `exec'.
$as_echo "$0: could not re-execute with $CONFIG_SHELL" >&2
exit 255
fi
if test x$as_have_required = xno; then :
$as_echo "$0: This script requires a shell more modern than all"
$as_echo "$0: the shells that I found on your system."
if test x${ZSH_VERSION+set} = xset ; then
$as_echo "$0: In particular, zsh $ZSH_VERSION has bugs and should"
$as_echo "$0: be upgraded to zsh 4.3.4 or later."
From Andrew Church <andrew@users.sourceforge.net>: when testing for "pcap_version", "pcap_debug", and "yydebug", don't add our own functions referring to those variables - GCC 3.4.1 optimizes the test code out before the link is done, as it's in a function that's not called.
2004-08-27 15:17:03 +08:00
else
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
$as_echo "$0: Please tell bug-autoconf@gnu.org about your system,
$0: including any error possibly output before this
$0: message. Then install a modern shell, or manually run
$0: the script under such a shell if you do have one."
Simplify the detection of OpenSSL libcrypto by using standard autoconf macros rather than a local copy of AC_LBL_SSLEAY. AC_LBL_SSLEAY is old and has not kept pace with some more recent developments in packaging like Debian and Ubuntu's multiarch support. The autoconf macros have been updated to handle multiarch so using them means that tcpdump gains the ability to be built with libcrypto on these new multiarch distros and to work successfully with Travis CI, which uses Ubuntu 12, which is one such multiarch distro (see GH-32). Fixes GH-33
2012-10-14 02:21:45 +08:00
fi
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
exit 1
fi
fi
fi
SHELL=${CONFIG_SHELL-/bin/sh}
export SHELL
# Unset more variables known to interfere with behavior of common tools.
CLICOLOR_FORCE= GREP_OPTIONS=
unset CLICOLOR_FORCE GREP_OPTIONS
## --------------------- ##
## M4sh Shell Functions. ##
## --------------------- ##
# as_fn_unset VAR
# ---------------
# Portably unset VAR.
as_fn_unset ()
{
{ eval $1=; unset $1;}
}
as_unset=as_fn_unset
# as_fn_set_status STATUS
# -----------------------
# Set $? to STATUS, without forking.
as_fn_set_status ()
{
return $1
} # as_fn_set_status
# as_fn_exit STATUS
# -----------------
# Exit the shell with STATUS, even in a "trap 0" or "set -e" context.
as_fn_exit ()
{
set +e
as_fn_set_status $1
exit $1
} # as_fn_exit
# as_fn_mkdir_p
# -------------
# Create "$as_dir" as a directory, including parents if necessary.
as_fn_mkdir_p ()
{
case $as_dir in #(
-*) as_dir=./$as_dir;;
esac
test -d "$as_dir" || eval $as_mkdir_p || {
as_dirs=
while :; do
case $as_dir in #(
*\'*) as_qdir=`$as_echo "$as_dir" | sed "s/'/'\\\\\\\\''/g"`;; #'(
*) as_qdir=$as_dir;;
esac
as_dirs="'$as_qdir' $as_dirs"
as_dir=`$as_dirname -- "$as_dir" ||
$as_expr X"$as_dir" : 'X\(.*[^/]\)//*[^/][^/]*/*$' \| \
X"$as_dir" : 'X\(//\)[^/]' \| \
X"$as_dir" : 'X\(//\)$' \| \
X"$as_dir" : 'X\(/\)' \| . 2>/dev/null ||
$as_echo X"$as_dir" |
sed '/^X\(.*[^/]\)\/\/*[^/][^/]*\/*$/{
s//\1/
q
}
/^X\(\/\/\)[^/].*/{
s//\1/
q
}
/^X\(\/\/\)$/{
s//\1/
q
}
/^X\(\/\).*/{
s//\1/
q
}
s/.*/./; q'`
test -d "$as_dir" && break
done
test -z "$as_dirs" || eval "mkdir $as_dirs"
} || test -d "$as_dir" || as_fn_error $? "cannot create directory $as_dir"
} # as_fn_mkdir_p
# as_fn_executable_p FILE
# -----------------------
# Test if FILE is an executable regular file.
as_fn_executable_p ()
{
test -f "$1" && test -x "$1"
} # as_fn_executable_p
# as_fn_append VAR VALUE
# ----------------------
# Append the text in VALUE to the end of the definition contained in VAR. Take
# advantage of any shell optimizations that allow amortized linear growth over
# repeated appends, instead of the typical quadratic growth present in naive
# implementations.
if (eval "as_var=1; as_var+=2; test x\$as_var = x12") 2>/dev/null; then :
eval 'as_fn_append ()
{
eval $1+=\$2
}'
else
as_fn_append ()
{
eval $1=\$$1\$2
}
fi # as_fn_append
# as_fn_arith ARG...
# ------------------
# Perform arithmetic evaluation on the ARGs, and store the result in the
# global $as_val. Take advantage of shells that can avoid forks. The arguments
# must be portable across $(()) and expr.
if (eval "test \$(( 1 + 1 )) = 2") 2>/dev/null; then :
eval 'as_fn_arith ()
{
as_val=$(( $* ))
}'
else
as_fn_arith ()
{
as_val=`expr "$@" || test $? -eq 1`
}
fi # as_fn_arith
# as_fn_error STATUS ERROR [LINENO LOG_FD]
# ----------------------------------------
# Output "`basename $0`: error: ERROR" to stderr. If LINENO and LOG_FD are
# provided, also output the error to LOG_FD, referencing LINENO. Then exit the
# script with STATUS, using 1 if that was 0.
as_fn_error ()
{
as_status=$1; test $as_status -eq 0 && as_status=1
if test "$4"; then
as_lineno=${as_lineno-"$3"} as_lineno_stack=as_lineno_stack=$as_lineno_stack
$as_echo "$as_me:${as_lineno-$LINENO}: error: $2" >&$4
fi
$as_echo "$as_me: error: $2" >&2
as_fn_exit $as_status
} # as_fn_error
From Andrew Church <andrew@users.sourceforge.net>: when testing for "pcap_version", "pcap_debug", and "yydebug", don't add our own functions referring to those variables - GCC 3.4.1 optimizes the test code out before the link is done, as it's in a function that's not called.
2004-08-27 15:17:03 +08:00
We support building tcpdump with versions of libpcap other than the one with which it was released, and DLT_BLUETOOTH_HCI_H4_WITH_PHDR might be defined by pcap-bpf.h without pcap/bluetooth.h being present (as appears to be the case on Fedora 9, for example), so check whether <pcap/bluetooth.h> is usable. Update a comment - F9 appears to have a "/usr/include/pcap.h" if you install the libpcap headers. When adding -I flags when running a compiler-based test, add them to CPPFLAGS, not CFLAGS - the latter doesn't work right with AC_CHECK_HEADERS, as the "gcc -E" run doesn't have the -I flags added.
2008-09-26 05:45:50 +08:00
if expr a : '\(a\)' >/dev/null 2>&1 &&
test "X`expr 00001 : '.*\(...\)'`" = X001; then
From Andrew Church <andrew@users.sourceforge.net>: when testing for "pcap_version", "pcap_debug", and "yydebug", don't add our own functions referring to those variables - GCC 3.4.1 optimizes the test code out before the link is done, as it's in a function that's not called.
2004-08-27 15:17:03 +08:00
as_expr=expr
else
as_expr=false
fi
We support building tcpdump with versions of libpcap other than the one with which it was released, and DLT_BLUETOOTH_HCI_H4_WITH_PHDR might be defined by pcap-bpf.h without pcap/bluetooth.h being present (as appears to be the case on Fedora 9, for example), so check whether <pcap/bluetooth.h> is usable. Update a comment - F9 appears to have a "/usr/include/pcap.h" if you install the libpcap headers. When adding -I flags when running a compiler-based test, add them to CPPFLAGS, not CFLAGS - the latter doesn't work right with AC_CHECK_HEADERS, as the "gcc -E" run doesn't have the -I flags added.
2008-09-26 05:45:50 +08:00
if (basename -- /) >/dev/null 2>&1 && test "X`basename -- / 2>&1`" = "X/"; then
From Andrew Church <andrew@users.sourceforge.net>: when testing for "pcap_version", "pcap_debug", and "yydebug", don't add our own functions referring to those variables - GCC 3.4.1 optimizes the test code out before the link is done, as it's in a function that's not called.
2004-08-27 15:17:03 +08:00
as_basename=basename
else
as_basename=false
fi
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
if (as_dir=`dirname -- /` && test "X$as_dir" = X/) >/dev/null 2>&1; then
as_dirname=dirname
else
as_dirname=false
fi
From Andrew Church <andrew@users.sourceforge.net>: when testing for "pcap_version", "pcap_debug", and "yydebug", don't add our own functions referring to those variables - GCC 3.4.1 optimizes the test code out before the link is done, as it's in a function that's not called.
2004-08-27 15:17:03 +08:00
We support building tcpdump with versions of libpcap other than the one with which it was released, and DLT_BLUETOOTH_HCI_H4_WITH_PHDR might be defined by pcap-bpf.h without pcap/bluetooth.h being present (as appears to be the case on Fedora 9, for example), so check whether <pcap/bluetooth.h> is usable. Update a comment - F9 appears to have a "/usr/include/pcap.h" if you install the libpcap headers. When adding -I flags when running a compiler-based test, add them to CPPFLAGS, not CFLAGS - the latter doesn't work right with AC_CHECK_HEADERS, as the "gcc -E" run doesn't have the -I flags added.
2008-09-26 05:45:50 +08:00
as_me=`$as_basename -- "$0" ||
From Andrew Church <andrew@users.sourceforge.net>: when testing for "pcap_version", "pcap_debug", and "yydebug", don't add our own functions referring to those variables - GCC 3.4.1 optimizes the test code out before the link is done, as it's in a function that's not called.
2004-08-27 15:17:03 +08:00
$as_expr X/"$0" : '.*/\([^/][^/]*\)/*$' \| \
X"$0" : 'X\(//\)$' \| \
We support building tcpdump with versions of libpcap other than the one with which it was released, and DLT_BLUETOOTH_HCI_H4_WITH_PHDR might be defined by pcap-bpf.h without pcap/bluetooth.h being present (as appears to be the case on Fedora 9, for example), so check whether <pcap/bluetooth.h> is usable. Update a comment - F9 appears to have a "/usr/include/pcap.h" if you install the libpcap headers. When adding -I flags when running a compiler-based test, add them to CPPFLAGS, not CFLAGS - the latter doesn't work right with AC_CHECK_HEADERS, as the "gcc -E" run doesn't have the -I flags added.
2008-09-26 05:45:50 +08:00
X"$0" : 'X\(/\)' \| . 2>/dev/null ||
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
$as_echo X/"$0" |
We support building tcpdump with versions of libpcap other than the one with which it was released, and DLT_BLUETOOTH_HCI_H4_WITH_PHDR might be defined by pcap-bpf.h without pcap/bluetooth.h being present (as appears to be the case on Fedora 9, for example), so check whether <pcap/bluetooth.h> is usable. Update a comment - F9 appears to have a "/usr/include/pcap.h" if you install the libpcap headers. When adding -I flags when running a compiler-based test, add them to CPPFLAGS, not CFLAGS - the latter doesn't work right with AC_CHECK_HEADERS, as the "gcc -E" run doesn't have the -I flags added.
2008-09-26 05:45:50 +08:00
sed '/^.*\/\([^/][^/]*\)\/*$/{
s//\1/
q
}
/^X\/\(\/\/\)$/{
s//\1/
q
}
/^X\/\(\/\).*/{
s//\1/
q
}
s/.*/./; q'`
regen
2000-01-08 14:00:59 +08:00
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
# Avoid depending upon Character Ranges.
as_cr_letters='abcdefghijklmnopqrstuvwxyz'
as_cr_LETTERS='ABCDEFGHIJKLMNOPQRSTUVWXYZ'
as_cr_Letters=$as_cr_letters$as_cr_LETTERS
as_cr_digits='0123456789'
as_cr_alnum=$as_cr_Letters$as_cr_digits
regen
2000-01-08 14:00:59 +08:00
From Max Laier: check whether the system has <net/pfvar.h> and: if it does, use that for the pf definitions; if it doesn't, don't compile in pf support; as both OpenBSD and FreeBSD have changed the pf definitions and header format without changing the DLT value, so you can't reliably read pflog-format libpcap files on a machine running an OS version other than the one on which the file was generated.
2007-09-13 03:36:18 +08:00
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
as_lineno_1=$LINENO as_lineno_1a=$LINENO
as_lineno_2=$LINENO as_lineno_2a=$LINENO
eval 'test "x$as_lineno_1'$as_run'" != "x$as_lineno_2'$as_run'" &&
test "x`expr $as_lineno_1'$as_run' + 1`" = "x$as_lineno_2'$as_run'"' || {
# Blame Lee E. McMahon (1931-1989) for sed's syntax. :-)
sed -n '
p
/[$]LINENO/=
' <$as_myself |
sed '
s/[$]LINENO.*/&-/
t lineno
b
:lineno
N
:loop
s/[$]LINENO\([^'$as_cr_alnum'_].*\n\)\(.*\)/\2\1\2/
t loop
s/-\n.*//
' >$as_me.lineno &&
chmod +x "$as_me.lineno" ||
{ $as_echo "$as_me: error: cannot create $as_me.lineno; rerun with a POSIX shell" >&2; as_fn_exit 1; }
From Max Laier: check whether the system has <net/pfvar.h> and: if it does, use that for the pf definitions; if it doesn't, don't compile in pf support; as both OpenBSD and FreeBSD have changed the pf definitions and header format without changing the DLT value, so you can't reliably read pflog-format libpcap files on a machine running an OS version other than the one on which the file was generated.
2007-09-13 03:36:18 +08:00
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
# If we had to re-execute with $CONFIG_SHELL, we're ensured to have
# already done that, so ensure we don't try to do so again and fall
# in an infinite loop. This has already happened in practice.
_as_can_reexec=no; export _as_can_reexec
# Don't try to exec as it changes $[0], causing all sort of problems
# (the dirname of $[0] is not the place where we might find the
# original and so on. Autoconf is especially sensitive to this).
. "./$as_me.lineno"
# Exit status is that of the last command.
exit
We support building tcpdump with versions of libpcap other than the one with which it was released, and DLT_BLUETOOTH_HCI_H4_WITH_PHDR might be defined by pcap-bpf.h without pcap/bluetooth.h being present (as appears to be the case on Fedora 9, for example), so check whether <pcap/bluetooth.h> is usable. Update a comment - F9 appears to have a "/usr/include/pcap.h" if you install the libpcap headers. When adding -I flags when running a compiler-based test, add them to CPPFLAGS, not CFLAGS - the latter doesn't work right with AC_CHECK_HEADERS, as the "gcc -E" run doesn't have the -I flags added.
2008-09-26 05:45:50 +08:00
}
From Max Laier: check whether the system has <net/pfvar.h> and: if it does, use that for the pf definitions; if it doesn't, don't compile in pf support; as both OpenBSD and FreeBSD have changed the pf definitions and header format without changing the DLT value, so you can't reliably read pflog-format libpcap files on a machine running an OS version other than the one on which the file was generated.
2007-09-13 03:36:18 +08:00
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
ECHO_C= ECHO_N= ECHO_T=
case `echo -n x` in #(((((
-n*)
case `echo 'xy\c'` in
*c*) ECHO_T=' ';; # ECHO_T is single tab character.
xy) ECHO_C='\c';;
*) echo `echo ksh88 bug on AIX 6.1` > /dev/null
ECHO_T=' ';;
esac;;
*)
ECHO_N='-n';;
esac
Check for extra networking libraries before checking for IPv6. On some platforms, such as SunOS 5.x, building the "do we have IPv6 support?" test program requires the extra networking libraries, so we need to know what extra networking libraries are required before doing that test.
2013-04-07 04:03:58 +08:00
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
rm -f conf$$ conf$$.exe conf$$.file
if test -d conf$$.dir; then
rm -f conf$$.dir/conf$$.file
We support building tcpdump with versions of libpcap other than the one with which it was released, and DLT_BLUETOOTH_HCI_H4_WITH_PHDR might be defined by pcap-bpf.h without pcap/bluetooth.h being present (as appears to be the case on Fedora 9, for example), so check whether <pcap/bluetooth.h> is usable. Update a comment - F9 appears to have a "/usr/include/pcap.h" if you install the libpcap headers. When adding -I flags when running a compiler-based test, add them to CPPFLAGS, not CFLAGS - the latter doesn't work right with AC_CHECK_HEADERS, as the "gcc -E" run doesn't have the -I flags added.
2008-09-26 05:45:50 +08:00
else
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
rm -f conf$$.dir
mkdir conf$$.dir 2>/dev/null
fi
if (echo >conf$$.file) 2>/dev/null; then
if ln -s conf$$.file conf$$ 2>/dev/null; then
as_ln_s='ln -s'
# ... but there are two gotchas:
# 1) On MSYS, both `ln -s file dir' and `ln file dir' fail.
# 2) DJGPP < 2.04 has no symlinks; `ln -s' creates a wrapper executable.
# In both cases, we have to default to `cp -pR'.
ln -s conf$$.file conf$$.dir 2>/dev/null && test ! -f conf$$.exe ||
as_ln_s='cp -pR'
elif ln conf$$.file conf$$ 2>/dev/null; then
as_ln_s=ln
else
as_ln_s='cp -pR'
fi
We support building tcpdump with versions of libpcap other than the one with which it was released, and DLT_BLUETOOTH_HCI_H4_WITH_PHDR might be defined by pcap-bpf.h without pcap/bluetooth.h being present (as appears to be the case on Fedora 9, for example), so check whether <pcap/bluetooth.h> is usable. Update a comment - F9 appears to have a "/usr/include/pcap.h" if you install the libpcap headers. When adding -I flags when running a compiler-based test, add them to CPPFLAGS, not CFLAGS - the latter doesn't work right with AC_CHECK_HEADERS, as the "gcc -E" run doesn't have the -I flags added.
2008-09-26 05:45:50 +08:00
else
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
as_ln_s='cp -pR'
We support building tcpdump with versions of libpcap other than the one with which it was released, and DLT_BLUETOOTH_HCI_H4_WITH_PHDR might be defined by pcap-bpf.h without pcap/bluetooth.h being present (as appears to be the case on Fedora 9, for example), so check whether <pcap/bluetooth.h> is usable. Update a comment - F9 appears to have a "/usr/include/pcap.h" if you install the libpcap headers. When adding -I flags when running a compiler-based test, add them to CPPFLAGS, not CFLAGS - the latter doesn't work right with AC_CHECK_HEADERS, as the "gcc -E" run doesn't have the -I flags added.
2008-09-26 05:45:50 +08:00
fi
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
rm -f conf$$ conf$$.exe conf$$.dir/conf$$.file conf$$.file
rmdir conf$$.dir 2>/dev/null
We support building tcpdump with versions of libpcap other than the one with which it was released, and DLT_BLUETOOTH_HCI_H4_WITH_PHDR might be defined by pcap-bpf.h without pcap/bluetooth.h being present (as appears to be the case on Fedora 9, for example), so check whether <pcap/bluetooth.h> is usable. Update a comment - F9 appears to have a "/usr/include/pcap.h" if you install the libpcap headers. When adding -I flags when running a compiler-based test, add them to CPPFLAGS, not CFLAGS - the latter doesn't work right with AC_CHECK_HEADERS, as the "gcc -E" run doesn't have the -I flags added.
2008-09-26 05:45:50 +08:00
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
if mkdir -p . 2>/dev/null; then
as_mkdir_p='mkdir -p "$as_dir"'
Check for extra networking libraries before checking for IPv6. On some platforms, such as SunOS 5.x, building the "do we have IPv6 support?" test program requires the extra networking libraries, so we need to know what extra networking libraries are required before doing that test.
2013-04-07 04:03:58 +08:00
else
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
test -d ./-p && rmdir ./-p
as_mkdir_p=false
Check for extra networking libraries before checking for IPv6. On some platforms, such as SunOS 5.x, building the "do we have IPv6 support?" test program requires the extra networking libraries, so we need to know what extra networking libraries are required before doing that test.
2013-04-07 04:03:58 +08:00
fi
regen
2000-01-08 14:00:59 +08:00
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
as_test_x='test -x'
as_executable_p=as_fn_executable_p
Check for extra networking libraries before checking for IPv6. On some platforms, such as SunOS 5.x, building the "do we have IPv6 support?" test program requires the extra networking libraries, so we need to know what extra networking libraries are required before doing that test.
2013-04-07 04:03:58 +08:00
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
# Sed expression to map a string onto a valid CPP name.
as_tr_cpp="eval sed 'y%*$as_cr_letters%P$as_cr_LETTERS%;s%[^_$as_cr_alnum]%_%g'"
Check for extra networking libraries before checking for IPv6. On some platforms, such as SunOS 5.x, building the "do we have IPv6 support?" test program requires the extra networking libraries, so we need to know what extra networking libraries are required before doing that test.
2013-04-07 04:03:58 +08:00
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
# Sed expression to map a string onto a valid variable name.
as_tr_sh="eval sed 'y%*+%pp%;s%[^_$as_cr_alnum]%_%g'"
Check for extra networking libraries before checking for IPv6. On some platforms, such as SunOS 5.x, building the "do we have IPv6 support?" test program requires the extra networking libraries, so we need to know what extra networking libraries are required before doing that test.
2013-04-07 04:03:58 +08:00
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
test -n "$DJDIR" || exec 7<&0 </dev/null
exec 6>&1
Check for extra networking libraries before checking for IPv6. On some platforms, such as SunOS 5.x, building the "do we have IPv6 support?" test program requires the extra networking libraries, so we need to know what extra networking libraries are required before doing that test.
2013-04-07 04:03:58 +08:00
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
# Name of the host.
# hostname on some systems (SVR3.2, old GNU/Linux) returns a bogus exit status,
# so uname gets run too.
ac_hostname=`(hostname || uname -n) 2>/dev/null | sed 1q`
Check for extra networking libraries before checking for IPv6. On some platforms, such as SunOS 5.x, building the "do we have IPv6 support?" test program requires the extra networking libraries, so we need to know what extra networking libraries are required before doing that test.
2013-04-07 04:03:58 +08:00
#
# Initializations.
#
ac_default_prefix=/usr/local
ac_clean_files=
ac_config_libobj_dir=.
LIBOBJS=
cross_compiling=no
subdirs=
From Andrew Church <andrew@users.sourceforge.net>: when testing for "pcap_version", "pcap_debug", and "yydebug", don't add our own functions referring to those variables - GCC 3.4.1 optimizes the test code out before the link is done, as it's in a function that's not called.
2004-08-27 15:17:03 +08:00
MFLAGS=
MAKEFLAGS=
Regenerate with autoconf 2.57.
2004-01-14 11:15:08 +08:00
From Andrew Church <andrew@users.sourceforge.net>: when testing for "pcap_version", "pcap_debug", and "yydebug", don't add our own functions referring to those variables - GCC 3.4.1 optimizes the test code out before the link is done, as it's in a function that's not called.
2004-08-27 15:17:03 +08:00
# Identity of this package.
Do the version number the way it's now done for libpcap. Use the two-argument version of AC_INIT() - which requires autoconf 2.64 or later, so require that as a minimum - and get the version string from the VERSION file. Use AC_CONFIG_SRCDIR() to say that the source directory needs tcpdump.c; the two-argument version of AC_INIT() doesn't do that. This means that we no longer have a version.c file.
2017-10-17 05:31:14 +08:00
PACKAGE_NAME='tcpdump'
PACKAGE_TARNAME='tcpdump'
PACKAGE_VERSION='4.10.0-PRE-GIT'
PACKAGE_STRING='tcpdump 4.10.0-PRE-GIT'
PACKAGE_BUGREPORT=''
PACKAGE_URL=''
From Andrew Church <andrew@users.sourceforge.net>: when testing for "pcap_version", "pcap_debug", and "yydebug", don't add our own functions referring to those variables - GCC 3.4.1 optimizes the test code out before the link is done, as it's in a function that's not called.
2004-08-27 15:17:03 +08:00
Regenerate with autoconf 2.57.
2004-01-14 11:15:08 +08:00
ac_unique_file="tcpdump.c"
# Factoring default headers for most tests.
ac_includes_default="\
#include <stdio.h>
We support building tcpdump with versions of libpcap other than the one with which it was released, and DLT_BLUETOOTH_HCI_H4_WITH_PHDR might be defined by pcap-bpf.h without pcap/bluetooth.h being present (as appears to be the case on Fedora 9, for example), so check whether <pcap/bluetooth.h> is usable. Update a comment - F9 appears to have a "/usr/include/pcap.h" if you install the libpcap headers. When adding -I flags when running a compiler-based test, add them to CPPFLAGS, not CFLAGS - the latter doesn't work right with AC_CHECK_HEADERS, as the "gcc -E" run doesn't have the -I flags added.
2008-09-26 05:45:50 +08:00
#ifdef HAVE_SYS_TYPES_H
Regenerate with autoconf 2.57.
2004-01-14 11:15:08 +08:00
# include <sys/types.h>
#endif
We support building tcpdump with versions of libpcap other than the one with which it was released, and DLT_BLUETOOTH_HCI_H4_WITH_PHDR might be defined by pcap-bpf.h without pcap/bluetooth.h being present (as appears to be the case on Fedora 9, for example), so check whether <pcap/bluetooth.h> is usable. Update a comment - F9 appears to have a "/usr/include/pcap.h" if you install the libpcap headers. When adding -I flags when running a compiler-based test, add them to CPPFLAGS, not CFLAGS - the latter doesn't work right with AC_CHECK_HEADERS, as the "gcc -E" run doesn't have the -I flags added.
2008-09-26 05:45:50 +08:00
#ifdef HAVE_SYS_STAT_H
Regenerate with autoconf 2.57.
2004-01-14 11:15:08 +08:00
# include <sys/stat.h>
#endif
We support building tcpdump with versions of libpcap other than the one with which it was released, and DLT_BLUETOOTH_HCI_H4_WITH_PHDR might be defined by pcap-bpf.h without pcap/bluetooth.h being present (as appears to be the case on Fedora 9, for example), so check whether <pcap/bluetooth.h> is usable. Update a comment - F9 appears to have a "/usr/include/pcap.h" if you install the libpcap headers. When adding -I flags when running a compiler-based test, add them to CPPFLAGS, not CFLAGS - the latter doesn't work right with AC_CHECK_HEADERS, as the "gcc -E" run doesn't have the -I flags added.
2008-09-26 05:45:50 +08:00
#ifdef STDC_HEADERS
Regenerate with autoconf 2.57.
2004-01-14 11:15:08 +08:00
# include <stdlib.h>
# include <stddef.h>
#else
We support building tcpdump with versions of libpcap other than the one with which it was released, and DLT_BLUETOOTH_HCI_H4_WITH_PHDR might be defined by pcap-bpf.h without pcap/bluetooth.h being present (as appears to be the case on Fedora 9, for example), so check whether <pcap/bluetooth.h> is usable. Update a comment - F9 appears to have a "/usr/include/pcap.h" if you install the libpcap headers. When adding -I flags when running a compiler-based test, add them to CPPFLAGS, not CFLAGS - the latter doesn't work right with AC_CHECK_HEADERS, as the "gcc -E" run doesn't have the -I flags added.
2008-09-26 05:45:50 +08:00
# ifdef HAVE_STDLIB_H
Regenerate with autoconf 2.57.
2004-01-14 11:15:08 +08:00
# include <stdlib.h>
# endif
#endif
We support building tcpdump with versions of libpcap other than the one with which it was released, and DLT_BLUETOOTH_HCI_H4_WITH_PHDR might be defined by pcap-bpf.h without pcap/bluetooth.h being present (as appears to be the case on Fedora 9, for example), so check whether <pcap/bluetooth.h> is usable. Update a comment - F9 appears to have a "/usr/include/pcap.h" if you install the libpcap headers. When adding -I flags when running a compiler-based test, add them to CPPFLAGS, not CFLAGS - the latter doesn't work right with AC_CHECK_HEADERS, as the "gcc -E" run doesn't have the -I flags added.
2008-09-26 05:45:50 +08:00
#ifdef HAVE_STRING_H
# if !defined STDC_HEADERS && defined HAVE_MEMORY_H
Regenerate with autoconf 2.57.
2004-01-14 11:15:08 +08:00
# include <memory.h>
# endif
# include <string.h>
#endif
We support building tcpdump with versions of libpcap other than the one with which it was released, and DLT_BLUETOOTH_HCI_H4_WITH_PHDR might be defined by pcap-bpf.h without pcap/bluetooth.h being present (as appears to be the case on Fedora 9, for example), so check whether <pcap/bluetooth.h> is usable. Update a comment - F9 appears to have a "/usr/include/pcap.h" if you install the libpcap headers. When adding -I flags when running a compiler-based test, add them to CPPFLAGS, not CFLAGS - the latter doesn't work right with AC_CHECK_HEADERS, as the "gcc -E" run doesn't have the -I flags added.
2008-09-26 05:45:50 +08:00
#ifdef HAVE_STRINGS_H
Regenerate with autoconf 2.57.
2004-01-14 11:15:08 +08:00
# include <strings.h>
#endif
We support building tcpdump with versions of libpcap other than the one with which it was released, and DLT_BLUETOOTH_HCI_H4_WITH_PHDR might be defined by pcap-bpf.h without pcap/bluetooth.h being present (as appears to be the case on Fedora 9, for example), so check whether <pcap/bluetooth.h> is usable. Update a comment - F9 appears to have a "/usr/include/pcap.h" if you install the libpcap headers. When adding -I flags when running a compiler-based test, add them to CPPFLAGS, not CFLAGS - the latter doesn't work right with AC_CHECK_HEADERS, as the "gcc -E" run doesn't have the -I flags added.
2008-09-26 05:45:50 +08:00
#ifdef HAVE_INTTYPES_H
Regenerate with autoconf 2.57.
2004-01-14 11:15:08 +08:00
# include <inttypes.h>
#endif
We support building tcpdump with versions of libpcap other than the one with which it was released, and DLT_BLUETOOTH_HCI_H4_WITH_PHDR might be defined by pcap-bpf.h without pcap/bluetooth.h being present (as appears to be the case on Fedora 9, for example), so check whether <pcap/bluetooth.h> is usable. Update a comment - F9 appears to have a "/usr/include/pcap.h" if you install the libpcap headers. When adding -I flags when running a compiler-based test, add them to CPPFLAGS, not CFLAGS - the latter doesn't work right with AC_CHECK_HEADERS, as the "gcc -E" run doesn't have the -I flags added.
2008-09-26 05:45:50 +08:00
#ifdef HAVE_STDINT_H
# include <stdint.h>
#endif
#ifdef HAVE_UNISTD_H
Regenerate with autoconf 2.57.
2004-01-14 11:15:08 +08:00
# include <unistd.h>
#endif"
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
ac_subst_vars='LTLIBOBJS
Check for extra networking libraries before checking for IPv6. On some platforms, such as SunOS 5.x, building the "do we have IPv6 support?" test program requires the extra networking libraries, so we need to know what extra networking libraries are required before doing that test.
2013-04-07 04:03:58 +08:00
INSTALL_DATA
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
INSTALL_SCRIPT
INSTALL_PROGRAM
MAN_MISC_INFO
MAN_FILE_FORMATS
LOCALSRC
V_PCAPDEP
V_INCLS
V_GROUP
V_DEFS
V_CCOPT
MKDEP
DEPENDENCY_CFLAG
Use AC_CHECK_TOOL to find ar. On some platforms, such as at least some versions of HP-UX, AR isn't automatically set by make.
2014-01-17 06:40:46 +08:00
AR
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
RANLIB
PCAP_CONFIG
LIBOBJS
EGREP
GREP
CPP
OBJEXT
EXEEXT
ac_ct_CC
CPPFLAGS
Simplify the detection of OpenSSL libcrypto by using standard autoconf macros rather than a local copy of AC_LBL_SSLEAY. AC_LBL_SSLEAY is old and has not kept pace with some more recent developments in packaging like Debian and Ubuntu's multiarch support. The autoconf macros have been updated to handle multiarch so using them means that tcpdump gains the ability to be built with libcrypto on these new multiarch distros and to work successfully with Travis CI, which uses Ubuntu 12, which is one such multiarch distro (see GH-32). Fixes GH-33
2012-10-14 02:21:45 +08:00
LDFLAGS
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
CFLAGS
CC
SHLICC2
host_os
host_vendor
host_cpu
host
build_os
build_vendor
build_cpu
build
target_alias
host_alias
build_alias
Simplify the detection of OpenSSL libcrypto by using standard autoconf macros rather than a local copy of AC_LBL_SSLEAY. AC_LBL_SSLEAY is old and has not kept pace with some more recent developments in packaging like Debian and Ubuntu's multiarch support. The autoconf macros have been updated to handle multiarch so using them means that tcpdump gains the ability to be built with libcrypto on these new multiarch distros and to work successfully with Travis CI, which uses Ubuntu 12, which is one such multiarch distro (see GH-32). Fixes GH-33
2012-10-14 02:21:45 +08:00
LIBS
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
ECHO_T
ECHO_N
ECHO_C
DEFS
mandir
localedir
libdir
psdir
pdfdir
dvidir
htmldir
infodir
docdir
oldincludedir
includedir
localstatedir
sharedstatedir
sysconfdir
datadir
datarootdir
libexecdir
sbindir
bindir
program_transform_name
prefix
exec_prefix
PACKAGE_URL
PACKAGE_BUGREPORT
PACKAGE_STRING
PACKAGE_VERSION
PACKAGE_TARNAME
PACKAGE_NAME
PATH_SEPARATOR
SHELL'
ac_subst_files=''
ac_user_opts='
enable_option_checking
with_gcc
enable_universal
with_smi
enable_smb
with_user
with_chroot
Add support for FreeBSD capsicum sandboxing.
2014-07-11 03:19:39 +08:00
with_sandbox_capsicum
Regenerate configure script.
2014-11-06 14:21:33 +08:00
with_system_libpcap
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
with_crypto
configure: add support for cap-ng package It uses '--with-cap-ng', for using libcap-ng [default=yes, if available]
2015-02-15 22:32:23 +08:00
with_cap_ng
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
'
ac_precious_vars='build_alias
host_alias
target_alias
CC
CFLAGS
LDFLAGS
LIBS
CPPFLAGS
CPP'
Simplify the detection of OpenSSL libcrypto by using standard autoconf macros rather than a local copy of AC_LBL_SSLEAY. AC_LBL_SSLEAY is old and has not kept pace with some more recent developments in packaging like Debian and Ubuntu's multiarch support. The autoconf macros have been updated to handle multiarch so using them means that tcpdump gains the ability to be built with libcrypto on these new multiarch distros and to work successfully with Travis CI, which uses Ubuntu 12, which is one such multiarch distro (see GH-32). Fixes GH-33
2012-10-14 02:21:45 +08:00
# Initialize some variables set by options.
ac_init_help=
ac_init_version=false
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
ac_unrecognized_opts=
ac_unrecognized_sep=
Simplify the detection of OpenSSL libcrypto by using standard autoconf macros rather than a local copy of AC_LBL_SSLEAY. AC_LBL_SSLEAY is old and has not kept pace with some more recent developments in packaging like Debian and Ubuntu's multiarch support. The autoconf macros have been updated to handle multiarch so using them means that tcpdump gains the ability to be built with libcrypto on these new multiarch distros and to work successfully with Travis CI, which uses Ubuntu 12, which is one such multiarch distro (see GH-32). Fixes GH-33
2012-10-14 02:21:45 +08:00
# The variables have the same names as the options, with
# dashes changed to underlines.
cache_file=/dev/null
exec_prefix=NONE
no_create=
Initial revision
1999-10-08 07:47:09 +08:00
no_recursion=
prefix=NONE
program_prefix=NONE
program_suffix=NONE
program_transform_name=s,x,x,
silent=
site=
srcdir=
verbose=
x_includes=NONE
x_libraries=NONE
Regenerate with autoconf 2.57.
2004-01-14 11:15:08 +08:00
# Installation directory options.
# These are left unexpanded so users can "make install exec_prefix=/foo"
# and all the variables that are supposed to be based on exec_prefix
# by default will actually change.
# Use braces instead of parens because sh, perl, etc. also accept them.
We support building tcpdump with versions of libpcap other than the one with which it was released, and DLT_BLUETOOTH_HCI_H4_WITH_PHDR might be defined by pcap-bpf.h without pcap/bluetooth.h being present (as appears to be the case on Fedora 9, for example), so check whether <pcap/bluetooth.h> is usable. Update a comment - F9 appears to have a "/usr/include/pcap.h" if you install the libpcap headers. When adding -I flags when running a compiler-based test, add them to CPPFLAGS, not CFLAGS - the latter doesn't work right with AC_CHECK_HEADERS, as the "gcc -E" run doesn't have the -I flags added.
2008-09-26 05:45:50 +08:00
# (The list follows the same order as the GNU Coding Standards.)
Initial revision
1999-10-08 07:47:09 +08:00
bindir='${exec_prefix}/bin'
sbindir='${exec_prefix}/sbin'
libexecdir='${exec_prefix}/libexec'
We support building tcpdump with versions of libpcap other than the one with which it was released, and DLT_BLUETOOTH_HCI_H4_WITH_PHDR might be defined by pcap-bpf.h without pcap/bluetooth.h being present (as appears to be the case on Fedora 9, for example), so check whether <pcap/bluetooth.h> is usable. Update a comment - F9 appears to have a "/usr/include/pcap.h" if you install the libpcap headers. When adding -I flags when running a compiler-based test, add them to CPPFLAGS, not CFLAGS - the latter doesn't work right with AC_CHECK_HEADERS, as the "gcc -E" run doesn't have the -I flags added.
2008-09-26 05:45:50 +08:00
datarootdir='${prefix}/share'
datadir='${datarootdir}'
Initial revision
1999-10-08 07:47:09 +08:00
sysconfdir='${prefix}/etc'
sharedstatedir='${prefix}/com'
localstatedir='${prefix}/var'
includedir='${prefix}/include'
oldincludedir='/usr/include'
Do the version number the way it's now done for libpcap. Use the two-argument version of AC_INIT() - which requires autoconf 2.64 or later, so require that as a minimum - and get the version string from the VERSION file. Use AC_CONFIG_SRCDIR() to say that the source directory needs tcpdump.c; the two-argument version of AC_INIT() doesn't do that. This means that we no longer have a version.c file.
2017-10-17 05:31:14 +08:00
docdir='${datarootdir}/doc/${PACKAGE_TARNAME}'
We support building tcpdump with versions of libpcap other than the one with which it was released, and DLT_BLUETOOTH_HCI_H4_WITH_PHDR might be defined by pcap-bpf.h without pcap/bluetooth.h being present (as appears to be the case on Fedora 9, for example), so check whether <pcap/bluetooth.h> is usable. Update a comment - F9 appears to have a "/usr/include/pcap.h" if you install the libpcap headers. When adding -I flags when running a compiler-based test, add them to CPPFLAGS, not CFLAGS - the latter doesn't work right with AC_CHECK_HEADERS, as the "gcc -E" run doesn't have the -I flags added.
2008-09-26 05:45:50 +08:00
infodir='${datarootdir}/info'
htmldir='${docdir}'
dvidir='${docdir}'
pdfdir='${docdir}'
psdir='${docdir}'
libdir='${exec_prefix}/lib'
localedir='${datarootdir}/locale'
mandir='${datarootdir}/man'
Initial revision
1999-10-08 07:47:09 +08:00
ac_prev=
We support building tcpdump with versions of libpcap other than the one with which it was released, and DLT_BLUETOOTH_HCI_H4_WITH_PHDR might be defined by pcap-bpf.h without pcap/bluetooth.h being present (as appears to be the case on Fedora 9, for example), so check whether <pcap/bluetooth.h> is usable. Update a comment - F9 appears to have a "/usr/include/pcap.h" if you install the libpcap headers. When adding -I flags when running a compiler-based test, add them to CPPFLAGS, not CFLAGS - the latter doesn't work right with AC_CHECK_HEADERS, as the "gcc -E" run doesn't have the -I flags added.
2008-09-26 05:45:50 +08:00
ac_dashdash=
Initial revision
1999-10-08 07:47:09 +08:00
for ac_option
do
# If the previous option needs an argument, assign it.
if test -n "$ac_prev"; then
We support building tcpdump with versions of libpcap other than the one with which it was released, and DLT_BLUETOOTH_HCI_H4_WITH_PHDR might be defined by pcap-bpf.h without pcap/bluetooth.h being present (as appears to be the case on Fedora 9, for example), so check whether <pcap/bluetooth.h> is usable. Update a comment - F9 appears to have a "/usr/include/pcap.h" if you install the libpcap headers. When adding -I flags when running a compiler-based test, add them to CPPFLAGS, not CFLAGS - the latter doesn't work right with AC_CHECK_HEADERS, as the "gcc -E" run doesn't have the -I flags added.
2008-09-26 05:45:50 +08:00
eval $ac_prev=\$ac_option
Initial revision
1999-10-08 07:47:09 +08:00
ac_prev=
continue
fi
We support building tcpdump with versions of libpcap other than the one with which it was released, and DLT_BLUETOOTH_HCI_H4_WITH_PHDR might be defined by pcap-bpf.h without pcap/bluetooth.h being present (as appears to be the case on Fedora 9, for example), so check whether <pcap/bluetooth.h> is usable. Update a comment - F9 appears to have a "/usr/include/pcap.h" if you install the libpcap headers. When adding -I flags when running a compiler-based test, add them to CPPFLAGS, not CFLAGS - the latter doesn't work right with AC_CHECK_HEADERS, as the "gcc -E" run doesn't have the -I flags added.
2008-09-26 05:45:50 +08:00
case $ac_option in
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
*=?*) ac_optarg=`expr "X$ac_option" : '[^=]*=\(.*\)'` ;;
*=) ac_optarg= ;;
*) ac_optarg=yes ;;
We support building tcpdump with versions of libpcap other than the one with which it was released, and DLT_BLUETOOTH_HCI_H4_WITH_PHDR might be defined by pcap-bpf.h without pcap/bluetooth.h being present (as appears to be the case on Fedora 9, for example), so check whether <pcap/bluetooth.h> is usable. Update a comment - F9 appears to have a "/usr/include/pcap.h" if you install the libpcap headers. When adding -I flags when running a compiler-based test, add them to CPPFLAGS, not CFLAGS - the latter doesn't work right with AC_CHECK_HEADERS, as the "gcc -E" run doesn't have the -I flags added.
2008-09-26 05:45:50 +08:00
esac
Initial revision
1999-10-08 07:47:09 +08:00
# Accept the important Cygnus configure options, so we can diagnose typos.
We support building tcpdump with versions of libpcap other than the one with which it was released, and DLT_BLUETOOTH_HCI_H4_WITH_PHDR might be defined by pcap-bpf.h without pcap/bluetooth.h being present (as appears to be the case on Fedora 9, for example), so check whether <pcap/bluetooth.h> is usable. Update a comment - F9 appears to have a "/usr/include/pcap.h" if you install the libpcap headers. When adding -I flags when running a compiler-based test, add them to CPPFLAGS, not CFLAGS - the latter doesn't work right with AC_CHECK_HEADERS, as the "gcc -E" run doesn't have the -I flags added.
2008-09-26 05:45:50 +08:00
case $ac_dashdash$ac_option in
--)
ac_dashdash=yes ;;
Initial revision
1999-10-08 07:47:09 +08:00
-bindir | --bindir | --bindi | --bind | --bin | --bi)
ac_prev=bindir ;;
-bindir=* | --bindir=* | --bindi=* | --bind=* | --bin=* | --bi=*)
Regenerate with autoconf 2.57.
2004-01-14 11:15:08 +08:00
bindir=$ac_optarg ;;
Initial revision
1999-10-08 07:47:09 +08:00
-build | --build | --buil | --bui | --bu)
Regenerate with autoconf 2.57.
2004-01-14 11:15:08 +08:00
ac_prev=build_alias ;;
Initial revision
1999-10-08 07:47:09 +08:00
-build=* | --build=* | --buil=* | --bui=* | --bu=*)
Regenerate with autoconf 2.57.
2004-01-14 11:15:08 +08:00
build_alias=$ac_optarg ;;
Initial revision
1999-10-08 07:47:09 +08:00
-cache-file | --cache-file | --cache-fil | --cache-fi \
| --cache-f | --cache- | --cache | --cach | --cac | --ca | --c)
ac_prev=cache_file ;;
-cache-file=* | --cache-file=* | --cache-fil=* | --cache-fi=* \
| --cache-f=* | --cache-=* | --cache=* | --cach=* | --cac=* | --ca=* | --c=*)
Regenerate with autoconf 2.57.
2004-01-14 11:15:08 +08:00
cache_file=$ac_optarg ;;
--config-cache | -C)
cache_file=config.cache ;;
Initial revision
1999-10-08 07:47:09 +08:00
We support building tcpdump with versions of libpcap other than the one with which it was released, and DLT_BLUETOOTH_HCI_H4_WITH_PHDR might be defined by pcap-bpf.h without pcap/bluetooth.h being present (as appears to be the case on Fedora 9, for example), so check whether <pcap/bluetooth.h> is usable. Update a comment - F9 appears to have a "/usr/include/pcap.h" if you install the libpcap headers. When adding -I flags when running a compiler-based test, add them to CPPFLAGS, not CFLAGS - the latter doesn't work right with AC_CHECK_HEADERS, as the "gcc -E" run doesn't have the -I flags added.
2008-09-26 05:45:50 +08:00
-datadir | --datadir | --datadi | --datad)
Initial revision
1999-10-08 07:47:09 +08:00
ac_prev=datadir ;;
We support building tcpdump with versions of libpcap other than the one with which it was released, and DLT_BLUETOOTH_HCI_H4_WITH_PHDR might be defined by pcap-bpf.h without pcap/bluetooth.h being present (as appears to be the case on Fedora 9, for example), so check whether <pcap/bluetooth.h> is usable. Update a comment - F9 appears to have a "/usr/include/pcap.h" if you install the libpcap headers. When adding -I flags when running a compiler-based test, add them to CPPFLAGS, not CFLAGS - the latter doesn't work right with AC_CHECK_HEADERS, as the "gcc -E" run doesn't have the -I flags added.
2008-09-26 05:45:50 +08:00
-datadir=* | --datadir=* | --datadi=* | --datad=*)
Regenerate with autoconf 2.57.
2004-01-14 11:15:08 +08:00
datadir=$ac_optarg ;;
Initial revision
1999-10-08 07:47:09 +08:00
We support building tcpdump with versions of libpcap other than the one with which it was released, and DLT_BLUETOOTH_HCI_H4_WITH_PHDR might be defined by pcap-bpf.h without pcap/bluetooth.h being present (as appears to be the case on Fedora 9, for example), so check whether <pcap/bluetooth.h> is usable. Update a comment - F9 appears to have a "/usr/include/pcap.h" if you install the libpcap headers. When adding -I flags when running a compiler-based test, add them to CPPFLAGS, not CFLAGS - the latter doesn't work right with AC_CHECK_HEADERS, as the "gcc -E" run doesn't have the -I flags added.
2008-09-26 05:45:50 +08:00
-datarootdir | --datarootdir | --datarootdi | --datarootd | --dataroot \
| --dataroo | --dataro | --datar)
ac_prev=datarootdir ;;
-datarootdir=* | --datarootdir=* | --datarootdi=* | --datarootd=* \
| --dataroot=* | --dataroo=* | --dataro=* | --datar=*)
datarootdir=$ac_optarg ;;
Initial revision
1999-10-08 07:47:09 +08:00
-disable-* | --disable-*)
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
ac_useropt=`expr "x$ac_option" : 'x-*disable-\(.*\)'`
Initial revision
1999-10-08 07:47:09 +08:00
# Reject names that are not valid shell variable names.
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
expr "x$ac_useropt" : ".*[^-+._$as_cr_alnum]" >/dev/null &&
as_fn_error $? "invalid feature name: $ac_useropt"
ac_useropt_orig=$ac_useropt
ac_useropt=`$as_echo "$ac_useropt" | sed 's/[-+.]/_/g'`
case $ac_user_opts in
*"
"enable_$ac_useropt"
"*) ;;
*) ac_unrecognized_opts="$ac_unrecognized_opts$ac_unrecognized_sep--disable-$ac_useropt_orig"
ac_unrecognized_sep=', ';;
esac
eval enable_$ac_useropt=no ;;
We support building tcpdump with versions of libpcap other than the one with which it was released, and DLT_BLUETOOTH_HCI_H4_WITH_PHDR might be defined by pcap-bpf.h without pcap/bluetooth.h being present (as appears to be the case on Fedora 9, for example), so check whether <pcap/bluetooth.h> is usable. Update a comment - F9 appears to have a "/usr/include/pcap.h" if you install the libpcap headers. When adding -I flags when running a compiler-based test, add them to CPPFLAGS, not CFLAGS - the latter doesn't work right with AC_CHECK_HEADERS, as the "gcc -E" run doesn't have the -I flags added.
2008-09-26 05:45:50 +08:00
-docdir | --docdir | --docdi | --doc | --do)
ac_prev=docdir ;;
-docdir=* | --docdir=* | --docdi=* | --doc=* | --do=*)
docdir=$ac_optarg ;;
-dvidir | --dvidir | --dvidi | --dvid | --dvi | --dv)
ac_prev=dvidir ;;
-dvidir=* | --dvidir=* | --dvidi=* | --dvid=* | --dvi=* | --dv=*)
dvidir=$ac_optarg ;;
Initial revision
1999-10-08 07:47:09 +08:00
-enable-* | --enable-*)
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
ac_useropt=`expr "x$ac_option" : 'x-*enable-\([^=]*\)'`
Initial revision
1999-10-08 07:47:09 +08:00
# Reject names that are not valid shell variable names.
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
expr "x$ac_useropt" : ".*[^-+._$as_cr_alnum]" >/dev/null &&
as_fn_error $? "invalid feature name: $ac_useropt"
ac_useropt_orig=$ac_useropt
ac_useropt=`$as_echo "$ac_useropt" | sed 's/[-+.]/_/g'`
case $ac_user_opts in
*"
"enable_$ac_useropt"
"*) ;;
*) ac_unrecognized_opts="$ac_unrecognized_opts$ac_unrecognized_sep--enable-$ac_useropt_orig"
ac_unrecognized_sep=', ';;
esac
eval enable_$ac_useropt=\$ac_optarg ;;
Initial revision
1999-10-08 07:47:09 +08:00
-exec-prefix | --exec_prefix | --exec-prefix | --exec-prefi \
| --exec-pref | --exec-pre | --exec-pr | --exec-p | --exec- \
| --exec | --exe | --ex)
ac_prev=exec_prefix ;;
-exec-prefix=* | --exec_prefix=* | --exec-prefix=* | --exec-prefi=* \
| --exec-pref=* | --exec-pre=* | --exec-pr=* | --exec-p=* | --exec-=* \
| --exec=* | --exe=* | --ex=*)
Regenerate with autoconf 2.57.
2004-01-14 11:15:08 +08:00
exec_prefix=$ac_optarg ;;
Initial revision
1999-10-08 07:47:09 +08:00
-gas | --gas | --ga | --g)
# Obsolete; use --with-gas.
with_gas=yes ;;
Regenerate with autoconf 2.57.
2004-01-14 11:15:08 +08:00
-help | --help | --hel | --he | -h)
ac_init_help=long ;;
-help=r* | --help=r* | --hel=r* | --he=r* | -hr*)
ac_init_help=recursive ;;
-help=s* | --help=s* | --hel=s* | --he=s* | -hs*)
ac_init_help=short ;;
Initial revision
1999-10-08 07:47:09 +08:00
-host | --host | --hos | --ho)
Regenerate with autoconf 2.57.
2004-01-14 11:15:08 +08:00
ac_prev=host_alias ;;
Initial revision
1999-10-08 07:47:09 +08:00
-host=* | --host=* | --hos=* | --ho=*)
Regenerate with autoconf 2.57.
2004-01-14 11:15:08 +08:00
host_alias=$ac_optarg ;;
Initial revision
1999-10-08 07:47:09 +08:00
We support building tcpdump with versions of libpcap other than the one with which it was released, and DLT_BLUETOOTH_HCI_H4_WITH_PHDR might be defined by pcap-bpf.h without pcap/bluetooth.h being present (as appears to be the case on Fedora 9, for example), so check whether <pcap/bluetooth.h> is usable. Update a comment - F9 appears to have a "/usr/include/pcap.h" if you install the libpcap headers. When adding -I flags when running a compiler-based test, add them to CPPFLAGS, not CFLAGS - the latter doesn't work right with AC_CHECK_HEADERS, as the "gcc -E" run doesn't have the -I flags added.
2008-09-26 05:45:50 +08:00
-htmldir | --htmldir | --htmldi | --htmld | --html | --htm | --ht)
ac_prev=htmldir ;;
-htmldir=* | --htmldir=* | --htmldi=* | --htmld=* | --html=* | --htm=* \
| --ht=*)
htmldir=$ac_optarg ;;
Initial revision
1999-10-08 07:47:09 +08:00
-includedir | --includedir | --includedi | --included | --include \
| --includ | --inclu | --incl | --inc)
ac_prev=includedir ;;
-includedir=* | --includedir=* | --includedi=* | --included=* | --include=* \
| --includ=* | --inclu=* | --incl=* | --inc=*)
Regenerate with autoconf 2.57.
2004-01-14 11:15:08 +08:00
includedir=$ac_optarg ;;
Initial revision
1999-10-08 07:47:09 +08:00
-infodir | --infodir | --infodi | --infod | --info | --inf)
ac_prev=infodir ;;
-infodir=* | --infodir=* | --infodi=* | --infod=* | --info=* | --inf=*)
Regenerate with autoconf 2.57.
2004-01-14 11:15:08 +08:00
infodir=$ac_optarg ;;
Initial revision
1999-10-08 07:47:09 +08:00
-libdir | --libdir | --libdi | --libd)
ac_prev=libdir ;;
-libdir=* | --libdir=* | --libdi=* | --libd=*)
Regenerate with autoconf 2.57.
2004-01-14 11:15:08 +08:00
libdir=$ac_optarg ;;
Initial revision
1999-10-08 07:47:09 +08:00
-libexecdir | --libexecdir | --libexecdi | --libexecd | --libexec \
| --libexe | --libex | --libe)
ac_prev=libexecdir ;;
-libexecdir=* | --libexecdir=* | --libexecdi=* | --libexecd=* | --libexec=* \
| --libexe=* | --libex=* | --libe=*)
Regenerate with autoconf 2.57.
2004-01-14 11:15:08 +08:00
libexecdir=$ac_optarg ;;
Initial revision
1999-10-08 07:47:09 +08:00
We support building tcpdump with versions of libpcap other than the one with which it was released, and DLT_BLUETOOTH_HCI_H4_WITH_PHDR might be defined by pcap-bpf.h without pcap/bluetooth.h being present (as appears to be the case on Fedora 9, for example), so check whether <pcap/bluetooth.h> is usable. Update a comment - F9 appears to have a "/usr/include/pcap.h" if you install the libpcap headers. When adding -I flags when running a compiler-based test, add them to CPPFLAGS, not CFLAGS - the latter doesn't work right with AC_CHECK_HEADERS, as the "gcc -E" run doesn't have the -I flags added.
2008-09-26 05:45:50 +08:00
-localedir | --localedir | --localedi | --localed | --locale)
ac_prev=localedir ;;
-localedir=* | --localedir=* | --localedi=* | --localed=* | --locale=*)
localedir=$ac_optarg ;;
Initial revision
1999-10-08 07:47:09 +08:00
-localstatedir | --localstatedir | --localstatedi | --localstated \
We support building tcpdump with versions of libpcap other than the one with which it was released, and DLT_BLUETOOTH_HCI_H4_WITH_PHDR might be defined by pcap-bpf.h without pcap/bluetooth.h being present (as appears to be the case on Fedora 9, for example), so check whether <pcap/bluetooth.h> is usable. Update a comment - F9 appears to have a "/usr/include/pcap.h" if you install the libpcap headers. When adding -I flags when running a compiler-based test, add them to CPPFLAGS, not CFLAGS - the latter doesn't work right with AC_CHECK_HEADERS, as the "gcc -E" run doesn't have the -I flags added.
2008-09-26 05:45:50 +08:00
| --localstate | --localstat | --localsta | --localst | --locals)
Initial revision
1999-10-08 07:47:09 +08:00
ac_prev=localstatedir ;;
-localstatedir=* | --localstatedir=* | --localstatedi=* | --localstated=* \
We support building tcpdump with versions of libpcap other than the one with which it was released, and DLT_BLUETOOTH_HCI_H4_WITH_PHDR might be defined by pcap-bpf.h without pcap/bluetooth.h being present (as appears to be the case on Fedora 9, for example), so check whether <pcap/bluetooth.h> is usable. Update a comment - F9 appears to have a "/usr/include/pcap.h" if you install the libpcap headers. When adding -I flags when running a compiler-based test, add them to CPPFLAGS, not CFLAGS - the latter doesn't work right with AC_CHECK_HEADERS, as the "gcc -E" run doesn't have the -I flags added.
2008-09-26 05:45:50 +08:00
| --localstate=* | --localstat=* | --localsta=* | --localst=* | --locals=*)
Regenerate with autoconf 2.57.
2004-01-14 11:15:08 +08:00
localstatedir=$ac_optarg ;;
Initial revision
1999-10-08 07:47:09 +08:00
-mandir | --mandir | --mandi | --mand | --man | --ma | --m)
ac_prev=mandir ;;
-mandir=* | --mandir=* | --mandi=* | --mand=* | --man=* | --ma=* | --m=*)
Regenerate with autoconf 2.57.
2004-01-14 11:15:08 +08:00
mandir=$ac_optarg ;;
Initial revision
1999-10-08 07:47:09 +08:00
-nfp | --nfp | --nf)
# Obsolete; use --without-fp.
with_fp=no ;;
-no-create | --no-create | --no-creat | --no-crea | --no-cre \
From Andrew Church <andrew@users.sourceforge.net>: when testing for "pcap_version", "pcap_debug", and "yydebug", don't add our own functions referring to those variables - GCC 3.4.1 optimizes the test code out before the link is done, as it's in a function that's not called.
2004-08-27 15:17:03 +08:00
| --no-cr | --no-c | -n)
Initial revision
1999-10-08 07:47:09 +08:00
no_create=yes ;;
-no-recursion | --no-recursion | --no-recursio | --no-recursi \
| --no-recurs | --no-recur | --no-recu | --no-rec | --no-re | --no-r)
no_recursion=yes ;;
-oldincludedir | --oldincludedir | --oldincludedi | --oldincluded \
| --oldinclude | --oldinclud | --oldinclu | --oldincl | --oldinc \
| --oldin | --oldi | --old | --ol | --o)
ac_prev=oldincludedir ;;
-oldincludedir=* | --oldincludedir=* | --oldincludedi=* | --oldincluded=* \
| --oldinclude=* | --oldinclud=* | --oldinclu=* | --oldincl=* | --oldinc=* \
| --oldin=* | --oldi=* | --old=* | --ol=* | --o=*)
Regenerate with autoconf 2.57.
2004-01-14 11:15:08 +08:00
oldincludedir=$ac_optarg ;;
Initial revision
1999-10-08 07:47:09 +08:00
-prefix | --prefix | --prefi | --pref | --pre | --pr | --p)
ac_prev=prefix ;;
-prefix=* | --prefix=* | --prefi=* | --pref=* | --pre=* | --pr=* | --p=*)
Regenerate with autoconf 2.57.
2004-01-14 11:15:08 +08:00
prefix=$ac_optarg ;;
Initial revision
1999-10-08 07:47:09 +08:00
-program-prefix | --program-prefix | --program-prefi | --program-pref \
| --program-pre | --program-pr | --program-p)
ac_prev=program_prefix ;;
-program-prefix=* | --program-prefix=* | --program-prefi=* \
| --program-pref=* | --program-pre=* | --program-pr=* | --program-p=*)
Regenerate with autoconf 2.57.
2004-01-14 11:15:08 +08:00
program_prefix=$ac_optarg ;;
Initial revision
1999-10-08 07:47:09 +08:00
-program-suffix | --program-suffix | --program-suffi | --program-suff \
| --program-suf | --program-su | --program-s)
ac_prev=program_suffix ;;
-program-suffix=* | --program-suffix=* | --program-suffi=* \
| --program-suff=* | --program-suf=* | --program-su=* | --program-s=*)
Regenerate with autoconf 2.57.
2004-01-14 11:15:08 +08:00
program_suffix=$ac_optarg ;;
Initial revision
1999-10-08 07:47:09 +08:00
-program-transform-name | --program-transform-name \
| --program-transform-nam | --program-transform-na \
| --program-transform-n | --program-transform- \
| --program-transform | --program-transfor \
| --program-transfo | --program-transf \
| --program-trans | --program-tran \
| --progr-tra | --program-tr | --program-t)
ac_prev=program_transform_name ;;
-program-transform-name=* | --program-transform-name=* \
| --program-transform-nam=* | --program-transform-na=* \
| --program-transform-n=* | --program-transform-=* \
| --program-transform=* | --program-transfor=* \
| --program-transfo=* | --program-transf=* \
| --program-trans=* | --program-tran=* \
| --progr-tra=* | --program-tr=* | --program-t=*)
Regenerate with autoconf 2.57.
2004-01-14 11:15:08 +08:00
program_transform_name=$ac_optarg ;;
Initial revision
1999-10-08 07:47:09 +08:00
We support building tcpdump with versions of libpcap other than the one with which it was released, and DLT_BLUETOOTH_HCI_H4_WITH_PHDR might be defined by pcap-bpf.h without pcap/bluetooth.h being present (as appears to be the case on Fedora 9, for example), so check whether <pcap/bluetooth.h> is usable. Update a comment - F9 appears to have a "/usr/include/pcap.h" if you install the libpcap headers. When adding -I flags when running a compiler-based test, add them to CPPFLAGS, not CFLAGS - the latter doesn't work right with AC_CHECK_HEADERS, as the "gcc -E" run doesn't have the -I flags added.
2008-09-26 05:45:50 +08:00
-pdfdir | --pdfdir | --pdfdi | --pdfd | --pdf | --pd)
ac_prev=pdfdir ;;
-pdfdir=* | --pdfdir=* | --pdfdi=* | --pdfd=* | --pdf=* | --pd=*)
pdfdir=$ac_optarg ;;
-psdir | --psdir | --psdi | --psd | --ps)
ac_prev=psdir ;;
-psdir=* | --psdir=* | --psdi=* | --psd=* | --ps=*)
psdir=$ac_optarg ;;
Initial revision
1999-10-08 07:47:09 +08:00
-q | -quiet | --quiet | --quie | --qui | --qu | --q \
| -silent | --silent | --silen | --sile | --sil)
silent=yes ;;
-sbindir | --sbindir | --sbindi | --sbind | --sbin | --sbi | --sb)
ac_prev=sbindir ;;
-sbindir=* | --sbindir=* | --sbindi=* | --sbind=* | --sbin=* \
| --sbi=* | --sb=*)
Regenerate with autoconf 2.57.
2004-01-14 11:15:08 +08:00
sbindir=$ac_optarg ;;
Initial revision
1999-10-08 07:47:09 +08:00
-sharedstatedir | --sharedstatedir | --sharedstatedi \
| --sharedstated | --sharedstate | --sharedstat | --sharedsta \
| --sharedst | --shareds | --shared | --share | --shar \
| --sha | --sh)
ac_prev=sharedstatedir ;;
-sharedstatedir=* | --sharedstatedir=* | --sharedstatedi=* \
| --sharedstated=* | --sharedstate=* | --sharedstat=* | --sharedsta=* \
| --sharedst=* | --shareds=* | --shared=* | --share=* | --shar=* \
| --sha=* | --sh=*)
Regenerate with autoconf 2.57.
2004-01-14 11:15:08 +08:00
sharedstatedir=$ac_optarg ;;
Initial revision
1999-10-08 07:47:09 +08:00
-site | --site | --sit)
ac_prev=site ;;
-site=* | --site=* | --sit=*)
Regenerate with autoconf 2.57.
2004-01-14 11:15:08 +08:00
site=$ac_optarg ;;
Initial revision
1999-10-08 07:47:09 +08:00
-srcdir | --srcdir | --srcdi | --srcd | --src | --sr)
ac_prev=srcdir ;;
-srcdir=* | --srcdir=* | --srcdi=* | --srcd=* | --src=* | --sr=*)
Regenerate with autoconf 2.57.
2004-01-14 11:15:08 +08:00
srcdir=$ac_optarg ;;
Initial revision
1999-10-08 07:47:09 +08:00
-sysconfdir | --sysconfdir | --sysconfdi | --sysconfd | --sysconf \
| --syscon | --sysco | --sysc | --sys | --sy)
ac_prev=sysconfdir ;;
-sysconfdir=* | --sysconfdir=* | --sysconfdi=* | --sysconfd=* | --sysconf=* \
| --syscon=* | --sysco=* | --sysc=* | --sys=* | --sy=*)
Regenerate with autoconf 2.57.
2004-01-14 11:15:08 +08:00
sysconfdir=$ac_optarg ;;
Initial revision
1999-10-08 07:47:09 +08:00
-target | --target | --targe | --targ | --tar | --ta | --t)
Regenerate with autoconf 2.57.
2004-01-14 11:15:08 +08:00
ac_prev=target_alias ;;
Initial revision
1999-10-08 07:47:09 +08:00
-target=* | --target=* | --targe=* | --targ=* | --tar=* | --ta=* | --t=*)
Regenerate with autoconf 2.57.
2004-01-14 11:15:08 +08:00
target_alias=$ac_optarg ;;
Initial revision
1999-10-08 07:47:09 +08:00
-v | -verbose | --verbose | --verbos | --verbo | --verb)
verbose=yes ;;
Regenerate with autoconf 2.57.
2004-01-14 11:15:08 +08:00
-version | --version | --versio | --versi | --vers | -V)
ac_init_version=: ;;
Initial revision
1999-10-08 07:47:09 +08:00
-with-* | --with-*)
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
ac_useropt=`expr "x$ac_option" : 'x-*with-\([^=]*\)'`
Initial revision
1999-10-08 07:47:09 +08:00
# Reject names that are not valid shell variable names.
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
expr "x$ac_useropt" : ".*[^-+._$as_cr_alnum]" >/dev/null &&
as_fn_error $? "invalid package name: $ac_useropt"
ac_useropt_orig=$ac_useropt
ac_useropt=`$as_echo "$ac_useropt" | sed 's/[-+.]/_/g'`
case $ac_user_opts in
*"
"with_$ac_useropt"
"*) ;;
*) ac_unrecognized_opts="$ac_unrecognized_opts$ac_unrecognized_sep--with-$ac_useropt_orig"
ac_unrecognized_sep=', ';;
esac
eval with_$ac_useropt=\$ac_optarg ;;
Initial revision
1999-10-08 07:47:09 +08:00
-without-* | --without-*)
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
ac_useropt=`expr "x$ac_option" : 'x-*without-\(.*\)'`
Initial revision
1999-10-08 07:47:09 +08:00
# Reject names that are not valid shell variable names.
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
expr "x$ac_useropt" : ".*[^-+._$as_cr_alnum]" >/dev/null &&
as_fn_error $? "invalid package name: $ac_useropt"
ac_useropt_orig=$ac_useropt
ac_useropt=`$as_echo "$ac_useropt" | sed 's/[-+.]/_/g'`
case $ac_user_opts in
*"
"with_$ac_useropt"
"*) ;;
*) ac_unrecognized_opts="$ac_unrecognized_opts$ac_unrecognized_sep--without-$ac_useropt_orig"
ac_unrecognized_sep=', ';;
esac
eval with_$ac_useropt=no ;;
Initial revision
1999-10-08 07:47:09 +08:00
--x)
# Obsolete; use --with-x.
with_x=yes ;;
-x-includes | --x-includes | --x-include | --x-includ | --x-inclu \
| --x-incl | --x-inc | --x-in | --x-i)
ac_prev=x_includes ;;
-x-includes=* | --x-includes=* | --x-include=* | --x-includ=* | --x-inclu=* \
| --x-incl=* | --x-inc=* | --x-in=* | --x-i=*)
Regenerate with autoconf 2.57.
2004-01-14 11:15:08 +08:00
x_includes=$ac_optarg ;;
Initial revision
1999-10-08 07:47:09 +08:00
-x-libraries | --x-libraries | --x-librarie | --x-librari \
| --x-librar | --x-libra | --x-libr | --x-lib | --x-li | --x-l)
ac_prev=x_libraries ;;
-x-libraries=* | --x-libraries=* | --x-librarie=* | --x-librari=* \
| --x-librar=* | --x-libra=* | --x-libr=* | --x-lib=* | --x-li=* | --x-l=*)
Regenerate with autoconf 2.57.
2004-01-14 11:15:08 +08:00
x_libraries=$ac_optarg ;;
Initial revision
1999-10-08 07:47:09 +08:00
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
-*) as_fn_error $? "unrecognized option: \`$ac_option'
Try \`$0 --help' for more information"
Initial revision
1999-10-08 07:47:09 +08:00
;;
Regenerate with autoconf 2.57.
2004-01-14 11:15:08 +08:00
*=*)
ac_envvar=`expr "x$ac_option" : 'x\([^=]*\)='`
# Reject names that are not valid shell variable names.
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
case $ac_envvar in #(
'' | [0-9]* | *[!_$as_cr_alnum]* )
as_fn_error $? "invalid variable name: \`$ac_envvar'" ;;
esac
We support building tcpdump with versions of libpcap other than the one with which it was released, and DLT_BLUETOOTH_HCI_H4_WITH_PHDR might be defined by pcap-bpf.h without pcap/bluetooth.h being present (as appears to be the case on Fedora 9, for example), so check whether <pcap/bluetooth.h> is usable. Update a comment - F9 appears to have a "/usr/include/pcap.h" if you install the libpcap headers. When adding -I flags when running a compiler-based test, add them to CPPFLAGS, not CFLAGS - the latter doesn't work right with AC_CHECK_HEADERS, as the "gcc -E" run doesn't have the -I flags added.
2008-09-26 05:45:50 +08:00
eval $ac_envvar=\$ac_optarg
Regenerate with autoconf 2.57.
2004-01-14 11:15:08 +08:00
export $ac_envvar ;;
Initial revision
1999-10-08 07:47:09 +08:00
*)
Regenerate with autoconf 2.57.
2004-01-14 11:15:08 +08:00
# FIXME: should be removed in autoconf 3.0.
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
$as_echo "$as_me: WARNING: you should use --build, --host, --target" >&2
Regenerate with autoconf 2.57.
2004-01-14 11:15:08 +08:00
expr "x$ac_option" : ".*[^-._$as_cr_alnum]" >/dev/null &&
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
$as_echo "$as_me: WARNING: invalid host type: $ac_option" >&2
: "${build_alias=$ac_option} ${host_alias=$ac_option} ${target_alias=$ac_option}"
Initial revision
1999-10-08 07:47:09 +08:00
;;
esac
done
if test -n "$ac_prev"; then
Regenerate with autoconf 2.57.
2004-01-14 11:15:08 +08:00
ac_option=--`echo $ac_prev | sed 's/_/-/g'`
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
as_fn_error $? "missing argument to $ac_option"
Simplify the detection of OpenSSL libcrypto by using standard autoconf macros rather than a local copy of AC_LBL_SSLEAY. AC_LBL_SSLEAY is old and has not kept pace with some more recent developments in packaging like Debian and Ubuntu's multiarch support. The autoconf macros have been updated to handle multiarch so using them means that tcpdump gains the ability to be built with libcrypto on these new multiarch distros and to work successfully with Travis CI, which uses Ubuntu 12, which is one such multiarch distro (see GH-32). Fixes GH-33
2012-10-14 02:21:45 +08:00
fi
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
if test -n "$ac_unrecognized_opts"; then
case $enable_option_checking in
no) ;;
fatal) as_fn_error $? "unrecognized options: $ac_unrecognized_opts" ;;
*) $as_echo "$as_me: WARNING: unrecognized options: $ac_unrecognized_opts" >&2 ;;
esac
fi
# Check all directory arguments for consistency.
We support building tcpdump with versions of libpcap other than the one with which it was released, and DLT_BLUETOOTH_HCI_H4_WITH_PHDR might be defined by pcap-bpf.h without pcap/bluetooth.h being present (as appears to be the case on Fedora 9, for example), so check whether <pcap/bluetooth.h> is usable. Update a comment - F9 appears to have a "/usr/include/pcap.h" if you install the libpcap headers. When adding -I flags when running a compiler-based test, add them to CPPFLAGS, not CFLAGS - the latter doesn't work right with AC_CHECK_HEADERS, as the "gcc -E" run doesn't have the -I flags added.
2008-09-26 05:45:50 +08:00
for ac_var in exec_prefix prefix bindir sbindir libexecdir datarootdir \
datadir sysconfdir sharedstatedir localstatedir includedir \
oldincludedir docdir infodir htmldir dvidir pdfdir psdir \
libdir localedir mandir
Run ranlib on libnetdissect.a if necessary. Remove it before building it, so we discard any stuff already in the archive.
2008-02-05 04:42:09 +08:00
do
We support building tcpdump with versions of libpcap other than the one with which it was released, and DLT_BLUETOOTH_HCI_H4_WITH_PHDR might be defined by pcap-bpf.h without pcap/bluetooth.h being present (as appears to be the case on Fedora 9, for example), so check whether <pcap/bluetooth.h> is usable. Update a comment - F9 appears to have a "/usr/include/pcap.h" if you install the libpcap headers. When adding -I flags when running a compiler-based test, add them to CPPFLAGS, not CFLAGS - the latter doesn't work right with AC_CHECK_HEADERS, as the "gcc -E" run doesn't have the -I flags added.
2008-09-26 05:45:50 +08:00
eval ac_val=\$$ac_var
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
# Remove trailing slashes.
case $ac_val in
*/ )
ac_val=`expr "X$ac_val" : 'X\(.*[^/]\)' \| "X$ac_val" : 'X\(.*\)'`
eval $ac_var=\$ac_val;;
esac
# Be sure to have absolute directory names.
Run ranlib on libnetdissect.a if necessary. Remove it before building it, so we discard any stuff already in the archive.
2008-02-05 04:42:09 +08:00
case $ac_val in
We support building tcpdump with versions of libpcap other than the one with which it was released, and DLT_BLUETOOTH_HCI_H4_WITH_PHDR might be defined by pcap-bpf.h without pcap/bluetooth.h being present (as appears to be the case on Fedora 9, for example), so check whether <pcap/bluetooth.h> is usable. Update a comment - F9 appears to have a "/usr/include/pcap.h" if you install the libpcap headers. When adding -I flags when running a compiler-based test, add them to CPPFLAGS, not CFLAGS - the latter doesn't work right with AC_CHECK_HEADERS, as the "gcc -E" run doesn't have the -I flags added.
2008-09-26 05:45:50 +08:00
[\\/$]* | ?:[\\/]* ) continue;;
NONE | '' ) case $ac_var in *prefix ) continue;; esac;;
Initial revision
1999-10-08 07:47:09 +08:00
esac
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
as_fn_error $? "expected an absolute directory name for --$ac_var: $ac_val"
Initial revision
1999-10-08 07:47:09 +08:00
done
Regenerate with autoconf 2.57.
2004-01-14 11:15:08 +08:00
# There might be people who depend on the old broken behavior: `$host'
# used to hold the argument of --host etc.
From Andrew Church <andrew@users.sourceforge.net>: when testing for "pcap_version", "pcap_debug", and "yydebug", don't add our own functions referring to those variables - GCC 3.4.1 optimizes the test code out before the link is done, as it's in a function that's not called.
2004-08-27 15:17:03 +08:00
# FIXME: To remove some day.
Regenerate with autoconf 2.57.
2004-01-14 11:15:08 +08:00
build=$build_alias
host=$host_alias
target=$target_alias
From Andrew Church <andrew@users.sourceforge.net>: when testing for "pcap_version", "pcap_debug", and "yydebug", don't add our own functions referring to those variables - GCC 3.4.1 optimizes the test code out before the link is done, as it's in a function that's not called.
2004-08-27 15:17:03 +08:00
# FIXME: To remove some day.
Regenerate with autoconf 2.57.
2004-01-14 11:15:08 +08:00
if test "x$host_alias" != x; then
if test "x$build_alias" = x; then
cross_compiling=maybe
elif test "x$build_alias" != "x$host_alias"; then
cross_compiling=yes
fi
fi
Initial revision
1999-10-08 07:47:09 +08:00
Regenerate with autoconf 2.57.
2004-01-14 11:15:08 +08:00
ac_tool_prefix=
test -n "$host_alias" && ac_tool_prefix=$host_alias-
test "$silent" = yes && exec 6>/dev/null
Initial revision
1999-10-08 07:47:09 +08:00
From Andrew Church <andrew@users.sourceforge.net>: when testing for "pcap_version", "pcap_debug", and "yydebug", don't add our own functions referring to those variables - GCC 3.4.1 optimizes the test code out before the link is done, as it's in a function that's not called.
2004-08-27 15:17:03 +08:00
We support building tcpdump with versions of libpcap other than the one with which it was released, and DLT_BLUETOOTH_HCI_H4_WITH_PHDR might be defined by pcap-bpf.h without pcap/bluetooth.h being present (as appears to be the case on Fedora 9, for example), so check whether <pcap/bluetooth.h> is usable. Update a comment - F9 appears to have a "/usr/include/pcap.h" if you install the libpcap headers. When adding -I flags when running a compiler-based test, add them to CPPFLAGS, not CFLAGS - the latter doesn't work right with AC_CHECK_HEADERS, as the "gcc -E" run doesn't have the -I flags added.
2008-09-26 05:45:50 +08:00
ac_pwd=`pwd` && test -n "$ac_pwd" &&
ac_ls_di=`ls -di .` &&
ac_pwd_ls_di=`cd "$ac_pwd" && ls -di .` ||
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
as_fn_error $? "working directory cannot be determined"
We support building tcpdump with versions of libpcap other than the one with which it was released, and DLT_BLUETOOTH_HCI_H4_WITH_PHDR might be defined by pcap-bpf.h without pcap/bluetooth.h being present (as appears to be the case on Fedora 9, for example), so check whether <pcap/bluetooth.h> is usable. Update a comment - F9 appears to have a "/usr/include/pcap.h" if you install the libpcap headers. When adding -I flags when running a compiler-based test, add them to CPPFLAGS, not CFLAGS - the latter doesn't work right with AC_CHECK_HEADERS, as the "gcc -E" run doesn't have the -I flags added.
2008-09-26 05:45:50 +08:00
test "X$ac_ls_di" = "X$ac_pwd_ls_di" ||
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
as_fn_error $? "pwd does not report name of working directory"
We support building tcpdump with versions of libpcap other than the one with which it was released, and DLT_BLUETOOTH_HCI_H4_WITH_PHDR might be defined by pcap-bpf.h without pcap/bluetooth.h being present (as appears to be the case on Fedora 9, for example), so check whether <pcap/bluetooth.h> is usable. Update a comment - F9 appears to have a "/usr/include/pcap.h" if you install the libpcap headers. When adding -I flags when running a compiler-based test, add them to CPPFLAGS, not CFLAGS - the latter doesn't work right with AC_CHECK_HEADERS, as the "gcc -E" run doesn't have the -I flags added.
2008-09-26 05:45:50 +08:00
Initial revision
1999-10-08 07:47:09 +08:00
# Find the source files, if location was not specified.
if test -z "$srcdir"; then
ac_srcdir_defaulted=yes
We support building tcpdump with versions of libpcap other than the one with which it was released, and DLT_BLUETOOTH_HCI_H4_WITH_PHDR might be defined by pcap-bpf.h without pcap/bluetooth.h being present (as appears to be the case on Fedora 9, for example), so check whether <pcap/bluetooth.h> is usable. Update a comment - F9 appears to have a "/usr/include/pcap.h" if you install the libpcap headers. When adding -I flags when running a compiler-based test, add them to CPPFLAGS, not CFLAGS - the latter doesn't work right with AC_CHECK_HEADERS, as the "gcc -E" run doesn't have the -I flags added.
2008-09-26 05:45:50 +08:00
# Try the directory containing this script, then the parent directory.
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
ac_confdir=`$as_dirname -- "$as_myself" ||
$as_expr X"$as_myself" : 'X\(.*[^/]\)//*[^/][^/]*/*$' \| \
X"$as_myself" : 'X\(//\)[^/]' \| \
X"$as_myself" : 'X\(//\)$' \| \
X"$as_myself" : 'X\(/\)' \| . 2>/dev/null ||
$as_echo X"$as_myself" |
We support building tcpdump with versions of libpcap other than the one with which it was released, and DLT_BLUETOOTH_HCI_H4_WITH_PHDR might be defined by pcap-bpf.h without pcap/bluetooth.h being present (as appears to be the case on Fedora 9, for example), so check whether <pcap/bluetooth.h> is usable. Update a comment - F9 appears to have a "/usr/include/pcap.h" if you install the libpcap headers. When adding -I flags when running a compiler-based test, add them to CPPFLAGS, not CFLAGS - the latter doesn't work right with AC_CHECK_HEADERS, as the "gcc -E" run doesn't have the -I flags added.
2008-09-26 05:45:50 +08:00
sed '/^X\(.*[^/]\)\/\/*[^/][^/]*\/*$/{
s//\1/
q
}
/^X\(\/\/\)[^/].*/{
s//\1/
q
}
/^X\(\/\/\)$/{
s//\1/
q
}
/^X\(\/\).*/{
s//\1/
q
}
s/.*/./; q'`
Initial revision
1999-10-08 07:47:09 +08:00
srcdir=$ac_confdir
We support building tcpdump with versions of libpcap other than the one with which it was released, and DLT_BLUETOOTH_HCI_H4_WITH_PHDR might be defined by pcap-bpf.h without pcap/bluetooth.h being present (as appears to be the case on Fedora 9, for example), so check whether <pcap/bluetooth.h> is usable. Update a comment - F9 appears to have a "/usr/include/pcap.h" if you install the libpcap headers. When adding -I flags when running a compiler-based test, add them to CPPFLAGS, not CFLAGS - the latter doesn't work right with AC_CHECK_HEADERS, as the "gcc -E" run doesn't have the -I flags added.
2008-09-26 05:45:50 +08:00
if test ! -r "$srcdir/$ac_unique_file"; then
Initial revision
1999-10-08 07:47:09 +08:00
srcdir=..
fi
else
ac_srcdir_defaulted=no
fi
We support building tcpdump with versions of libpcap other than the one with which it was released, and DLT_BLUETOOTH_HCI_H4_WITH_PHDR might be defined by pcap-bpf.h without pcap/bluetooth.h being present (as appears to be the case on Fedora 9, for example), so check whether <pcap/bluetooth.h> is usable. Update a comment - F9 appears to have a "/usr/include/pcap.h" if you install the libpcap headers. When adding -I flags when running a compiler-based test, add them to CPPFLAGS, not CFLAGS - the latter doesn't work right with AC_CHECK_HEADERS, as the "gcc -E" run doesn't have the -I flags added.
2008-09-26 05:45:50 +08:00
if test ! -r "$srcdir/$ac_unique_file"; then
test "$ac_srcdir_defaulted" = yes && srcdir="$ac_confdir or .."
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
as_fn_error $? "cannot find sources ($ac_unique_file) in $srcdir"
Initial revision
1999-10-08 07:47:09 +08:00
fi
We support building tcpdump with versions of libpcap other than the one with which it was released, and DLT_BLUETOOTH_HCI_H4_WITH_PHDR might be defined by pcap-bpf.h without pcap/bluetooth.h being present (as appears to be the case on Fedora 9, for example), so check whether <pcap/bluetooth.h> is usable. Update a comment - F9 appears to have a "/usr/include/pcap.h" if you install the libpcap headers. When adding -I flags when running a compiler-based test, add them to CPPFLAGS, not CFLAGS - the latter doesn't work right with AC_CHECK_HEADERS, as the "gcc -E" run doesn't have the -I flags added.
2008-09-26 05:45:50 +08:00
ac_msg="sources are in $srcdir, but \`cd $srcdir' does not work"
ac_abs_confdir=`(
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
cd "$srcdir" && test -r "./$ac_unique_file" || as_fn_error $? "$ac_msg"
We support building tcpdump with versions of libpcap other than the one with which it was released, and DLT_BLUETOOTH_HCI_H4_WITH_PHDR might be defined by pcap-bpf.h without pcap/bluetooth.h being present (as appears to be the case on Fedora 9, for example), so check whether <pcap/bluetooth.h> is usable. Update a comment - F9 appears to have a "/usr/include/pcap.h" if you install the libpcap headers. When adding -I flags when running a compiler-based test, add them to CPPFLAGS, not CFLAGS - the latter doesn't work right with AC_CHECK_HEADERS, as the "gcc -E" run doesn't have the -I flags added.
2008-09-26 05:45:50 +08:00
pwd)`
# When building in place, set srcdir=.
if test "$ac_abs_confdir" = "$ac_pwd"; then
srcdir=.
fi
# Remove unnecessary trailing slashes from srcdir.
# Double slashes in file names in object file debugging info
# mess up M-x gdb in Emacs.
case $srcdir in
*/) srcdir=`expr "X$srcdir" : 'X\(.*[^/]\)' \| "X$srcdir" : 'X\(.*\)'`;;
esac
for ac_var in $ac_precious_vars; do
eval ac_env_${ac_var}_set=\${${ac_var}+set}
eval ac_env_${ac_var}_value=\$${ac_var}
eval ac_cv_env_${ac_var}_set=\${${ac_var}+set}
eval ac_cv_env_${ac_var}_value=\$${ac_var}
done
Initial revision
1999-10-08 07:47:09 +08:00
Regenerate with autoconf 2.57.
2004-01-14 11:15:08 +08:00
#
# Report the --help message.
#
if test "$ac_init_help" = "long"; then
# Omit some internal or obsolete options to make the list less imposing.
# This message is too long to be a string in the A/UX 3.1 sh.
From Andrew Church <andrew@users.sourceforge.net>: when testing for "pcap_version", "pcap_debug", and "yydebug", don't add our own functions referring to those variables - GCC 3.4.1 optimizes the test code out before the link is done, as it's in a function that's not called.
2004-08-27 15:17:03 +08:00
cat <<_ACEOF
Do the version number the way it's now done for libpcap. Use the two-argument version of AC_INIT() - which requires autoconf 2.64 or later, so require that as a minimum - and get the version string from the VERSION file. Use AC_CONFIG_SRCDIR() to say that the source directory needs tcpdump.c; the two-argument version of AC_INIT() doesn't do that. This means that we no longer have a version.c file.
2017-10-17 05:31:14 +08:00
\`configure' configures tcpdump 4.10.0-PRE-GIT to adapt to many kinds of systems.
Initial revision
1999-10-08 07:47:09 +08:00
Regenerate with autoconf 2.57.
2004-01-14 11:15:08 +08:00
Usage: $0 [OPTION]... [VAR=VALUE]...
Initial revision
1999-10-08 07:47:09 +08:00
Regenerate with autoconf 2.57.
2004-01-14 11:15:08 +08:00
To assign environment variables (e.g., CC, CFLAGS...), specify them as
VAR=VALUE. See below for descriptions of some of the useful variables.
Initial revision
1999-10-08 07:47:09 +08:00
Regenerate with autoconf 2.57.
2004-01-14 11:15:08 +08:00
Defaults for the options are specified in brackets.
Initial revision
1999-10-08 07:47:09 +08:00
Regenerate with autoconf 2.57.
2004-01-14 11:15:08 +08:00
Configuration:
-h, --help display this help and exit
--help=short display options specific to this package
--help=recursive display the short help of all the included packages
-V, --version display version information and exit
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
-q, --quiet, --silent do not print \`checking ...' messages
Regenerate with autoconf 2.57.
2004-01-14 11:15:08 +08:00
--cache-file=FILE cache test results in FILE [disabled]
-C, --config-cache alias for \`--cache-file=config.cache'
-n, --no-create do not create output files
--srcdir=DIR find the sources in DIR [configure dir or \`..']
Installation directories:
--prefix=PREFIX install architecture-independent files in PREFIX
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
[$ac_default_prefix]
Regenerate with autoconf 2.57.
2004-01-14 11:15:08 +08:00
--exec-prefix=EPREFIX install architecture-dependent files in EPREFIX
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
[PREFIX]
Initial revision
1999-10-08 07:47:09 +08:00
Regenerate with autoconf 2.57.
2004-01-14 11:15:08 +08:00
By default, \`make install' will install all the files in
\`$ac_default_prefix/bin', \`$ac_default_prefix/lib' etc. You can specify
an installation prefix other than \`$ac_default_prefix' using \`--prefix',
for instance \`--prefix=\$HOME'.
Initial revision
1999-10-08 07:47:09 +08:00
Regenerate with autoconf 2.57.
2004-01-14 11:15:08 +08:00
For better control, use the options below.
Initial revision
1999-10-08 07:47:09 +08:00
Regenerate with autoconf 2.57.
2004-01-14 11:15:08 +08:00
Fine tuning of the installation directories:
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
--bindir=DIR user executables [EPREFIX/bin]
--sbindir=DIR system admin executables [EPREFIX/sbin]
--libexecdir=DIR program executables [EPREFIX/libexec]
--sysconfdir=DIR read-only single-machine data [PREFIX/etc]
--sharedstatedir=DIR modifiable architecture-independent data [PREFIX/com]
--localstatedir=DIR modifiable single-machine data [PREFIX/var]
--libdir=DIR object code libraries [EPREFIX/lib]
--includedir=DIR C header files [PREFIX/include]
--oldincludedir=DIR C header files for non-gcc [/usr/include]
--datarootdir=DIR read-only arch.-independent data root [PREFIX/share]
--datadir=DIR read-only architecture-independent data [DATAROOTDIR]
--infodir=DIR info documentation [DATAROOTDIR/info]
--localedir=DIR locale-dependent data [DATAROOTDIR/locale]
--mandir=DIR man documentation [DATAROOTDIR/man]
Do the version number the way it's now done for libpcap. Use the two-argument version of AC_INIT() - which requires autoconf 2.64 or later, so require that as a minimum - and get the version string from the VERSION file. Use AC_CONFIG_SRCDIR() to say that the source directory needs tcpdump.c; the two-argument version of AC_INIT() doesn't do that. This means that we no longer have a version.c file.
2017-10-17 05:31:14 +08:00
--docdir=DIR documentation root [DATAROOTDIR/doc/tcpdump]
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
--htmldir=DIR html documentation [DOCDIR]
--dvidir=DIR dvi documentation [DOCDIR]
--pdfdir=DIR pdf documentation [DOCDIR]
--psdir=DIR ps documentation [DOCDIR]
From Andrew Church <andrew@users.sourceforge.net>: when testing for "pcap_version", "pcap_debug", and "yydebug", don't add our own functions referring to those variables - GCC 3.4.1 optimizes the test code out before the link is done, as it's in a function that's not called.
2004-08-27 15:17:03 +08:00
_ACEOF
Regenerate with autoconf 2.57.
2004-01-14 11:15:08 +08:00
From Andrew Church <andrew@users.sourceforge.net>: when testing for "pcap_version", "pcap_debug", and "yydebug", don't add our own functions referring to those variables - GCC 3.4.1 optimizes the test code out before the link is done, as it's in a function that's not called.
2004-08-27 15:17:03 +08:00
cat <<\_ACEOF
Regenerate with autoconf 2.57.
2004-01-14 11:15:08 +08:00
System types:
--build=BUILD configure for building on BUILD [guessed]
From Andrew Church <andrew@users.sourceforge.net>: when testing for "pcap_version", "pcap_debug", and "yydebug", don't add our own functions referring to those variables - GCC 3.4.1 optimizes the test code out before the link is done, as it's in a function that's not called.
2004-08-27 15:17:03 +08:00
--host=HOST cross-compile to build programs to run on HOST [BUILD]
_ACEOF
Initial revision
1999-10-08 07:47:09 +08:00
fi
Regenerate with autoconf 2.57.
2004-01-14 11:15:08 +08:00
if test -n "$ac_init_help"; then
Do the version number the way it's now done for libpcap. Use the two-argument version of AC_INIT() - which requires autoconf 2.64 or later, so require that as a minimum - and get the version string from the VERSION file. Use AC_CONFIG_SRCDIR() to say that the source directory needs tcpdump.c; the two-argument version of AC_INIT() doesn't do that. This means that we no longer have a version.c file.
2017-10-17 05:31:14 +08:00
case $ac_init_help in
short | recursive ) echo "Configuration of tcpdump 4.10.0-PRE-GIT:";;
esac
From Andrew Church <andrew@users.sourceforge.net>: when testing for "pcap_version", "pcap_debug", and "yydebug", don't add our own functions referring to those variables - GCC 3.4.1 optimizes the test code out before the link is done, as it's in a function that's not called.
2004-08-27 15:17:03 +08:00
cat <<\_ACEOF
Regenerate with autoconf 2.57.
2004-01-14 11:15:08 +08:00
Optional Features:
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
--disable-option-checking ignore unrecognized --enable/--with options
Regenerate with autoconf 2.57.
2004-01-14 11:15:08 +08:00
--disable-FEATURE do not include FEATURE (same as --enable-FEATURE=no)
--enable-FEATURE[=ARG] include FEATURE [ARG=yes]
Build universal on OS X by default; add an option to disable that. Instead of requiring the user to specify -arch options on OS X to build a universal version of tcpdump, just default to universal on OS X by default. Pick the particular targets to match the way tcpdump is built for the OS for which we're building.
2010-04-05 03:08:11 +08:00
--disable-universal don't build universal on OS X
Regenerate with autoconf 2.57.
2004-01-14 11:15:08 +08:00
--enable-smb enable possibly-buggy SMB printer default=yes
--disable-smb disable possibly-buggy SMB printer
Initial revision
1999-10-08 07:47:09 +08:00
Regenerate with autoconf 2.57.
2004-01-14 11:15:08 +08:00
Optional Packages:
--with-PACKAGE[=ARG] use PACKAGE [ARG=yes]
--without-PACKAGE do not use PACKAGE (same as --with-PACKAGE=no)
--without-gcc don't use gcc
Propagate from the git tree: Author: Peter Volkov <pva@gentoo.org> Date: Sun Nov 9 20:33:27 2008 -0500 Currently it's impossible to build tcpdump without libsmi on system with libsmi installed. The patch in attachment adds --with{,out}-smi configure switch which allows to disable it.
2008-11-18 15:39:20 +08:00
--with-smi link with libsmi (allows to load MIBs on the fly to decode SNMP packets. default=yes
--without-smi don't link with libsmi
Regenerate.
2004-01-26 08:51:31 +08:00
--with-user=USERNAME drop privileges by default to USERNAME
Regenerate.
2004-03-12 07:53:33 +08:00
--with-chroot=DIRECTORY when dropping privileges, chroot to DIRECTORY
Document --with-sandbox-capsicum.
2014-09-01 04:37:10 +08:00
--with-sandbox-capsicum use Capsicum security functions [default=yes, if
available]
Regenerate configure script.
2014-11-06 14:21:33 +08:00
--with-system-libpcap don't use local pcap library
Allow building with libcrypto not in the default directory. Add support for an argument to --with-crypto, so that if you have one version of libcrypto installed under /usr and another version installed under /usr/local, you can force tcpdump to be built with the /usr/local version. Also, refer both to OpenSSL and libressl in comments and messages.
2016-07-14 08:23:59 +08:00
--with-crypto[=DIR] use OpenSSL/libressl libcrypto (located in directory
DIR, if specified) [default=yes, if available]
configure: add support for cap-ng package It uses '--with-cap-ng', for using libcap-ng [default=yes, if available]
2015-02-15 22:32:23 +08:00
--with-cap-ng use libcap-ng [default=yes, if available]
Initial revision
1999-10-08 07:47:09 +08:00
Regenerate with autoconf 2.57.
2004-01-14 11:15:08 +08:00
Some influential environment variables:
CC C compiler command
CFLAGS C compiler flags
LDFLAGS linker flags, e.g. -L<lib dir> if you have libraries in a
nonstandard directory <lib dir>
We support building tcpdump with versions of libpcap other than the one with which it was released, and DLT_BLUETOOTH_HCI_H4_WITH_PHDR might be defined by pcap-bpf.h without pcap/bluetooth.h being present (as appears to be the case on Fedora 9, for example), so check whether <pcap/bluetooth.h> is usable. Update a comment - F9 appears to have a "/usr/include/pcap.h" if you install the libpcap headers. When adding -I flags when running a compiler-based test, add them to CPPFLAGS, not CFLAGS - the latter doesn't work right with AC_CHECK_HEADERS, as the "gcc -E" run doesn't have the -I flags added.
2008-09-26 05:45:50 +08:00
LIBS libraries to pass to the linker, e.g. -l<library>
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
CPPFLAGS (Objective) C/C++ preprocessor flags, e.g. -I<include dir> if
We support building tcpdump with versions of libpcap other than the one with which it was released, and DLT_BLUETOOTH_HCI_H4_WITH_PHDR might be defined by pcap-bpf.h without pcap/bluetooth.h being present (as appears to be the case on Fedora 9, for example), so check whether <pcap/bluetooth.h> is usable. Update a comment - F9 appears to have a "/usr/include/pcap.h" if you install the libpcap headers. When adding -I flags when running a compiler-based test, add them to CPPFLAGS, not CFLAGS - the latter doesn't work right with AC_CHECK_HEADERS, as the "gcc -E" run doesn't have the -I flags added.
2008-09-26 05:45:50 +08:00
you have headers in a nonstandard directory <include dir>
Regenerate with autoconf 2.57.
2004-01-14 11:15:08 +08:00
CPP C preprocessor
Initial revision
1999-10-08 07:47:09 +08:00
Regenerate with autoconf 2.57.
2004-01-14 11:15:08 +08:00
Use these variables to override the choices made by `configure' or to help
it to find libraries and programs with nonstandard names/locations.
Initial revision
1999-10-08 07:47:09 +08:00
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
Report bugs to the package provider.
From Andrew Church <andrew@users.sourceforge.net>: when testing for "pcap_version", "pcap_debug", and "yydebug", don't add our own functions referring to those variables - GCC 3.4.1 optimizes the test code out before the link is done, as it's in a function that's not called.
2004-08-27 15:17:03 +08:00
_ACEOF
We support building tcpdump with versions of libpcap other than the one with which it was released, and DLT_BLUETOOTH_HCI_H4_WITH_PHDR might be defined by pcap-bpf.h without pcap/bluetooth.h being present (as appears to be the case on Fedora 9, for example), so check whether <pcap/bluetooth.h> is usable. Update a comment - F9 appears to have a "/usr/include/pcap.h" if you install the libpcap headers. When adding -I flags when running a compiler-based test, add them to CPPFLAGS, not CFLAGS - the latter doesn't work right with AC_CHECK_HEADERS, as the "gcc -E" run doesn't have the -I flags added.
2008-09-26 05:45:50 +08:00
ac_status=$?
Initial revision
1999-10-08 07:47:09 +08:00
fi
Regenerate with autoconf 2.57.
2004-01-14 11:15:08 +08:00
if test "$ac_init_help" = "recursive"; then
# If there are subdirs, report their specific --help.
From Andrew Church <andrew@users.sourceforge.net>: when testing for "pcap_version", "pcap_debug", and "yydebug", don't add our own functions referring to those variables - GCC 3.4.1 optimizes the test code out before the link is done, as it's in a function that's not called.
2004-08-27 15:17:03 +08:00
for ac_dir in : $ac_subdirs_all; do test "x$ac_dir" = x: && continue
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
test -d "$ac_dir" ||
{ cd "$srcdir" && ac_pwd=`pwd` && srcdir=. && test -d "$ac_dir"; } ||
continue
From Andrew Church <andrew@users.sourceforge.net>: when testing for "pcap_version", "pcap_debug", and "yydebug", don't add our own functions referring to those variables - GCC 3.4.1 optimizes the test code out before the link is done, as it's in a function that's not called.
2004-08-27 15:17:03 +08:00
ac_builddir=.
We support building tcpdump with versions of libpcap other than the one with which it was released, and DLT_BLUETOOTH_HCI_H4_WITH_PHDR might be defined by pcap-bpf.h without pcap/bluetooth.h being present (as appears to be the case on Fedora 9, for example), so check whether <pcap/bluetooth.h> is usable. Update a comment - F9 appears to have a "/usr/include/pcap.h" if you install the libpcap headers. When adding -I flags when running a compiler-based test, add them to CPPFLAGS, not CFLAGS - the latter doesn't work right with AC_CHECK_HEADERS, as the "gcc -E" run doesn't have the -I flags added.
2008-09-26 05:45:50 +08:00
case "$ac_dir" in
.) ac_dir_suffix= ac_top_builddir_sub=. ac_top_build_prefix= ;;
*)
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
ac_dir_suffix=/`$as_echo "$ac_dir" | sed 's|^\.[\\/]||'`
We support building tcpdump with versions of libpcap other than the one with which it was released, and DLT_BLUETOOTH_HCI_H4_WITH_PHDR might be defined by pcap-bpf.h without pcap/bluetooth.h being present (as appears to be the case on Fedora 9, for example), so check whether <pcap/bluetooth.h> is usable. Update a comment - F9 appears to have a "/usr/include/pcap.h" if you install the libpcap headers. When adding -I flags when running a compiler-based test, add them to CPPFLAGS, not CFLAGS - the latter doesn't work right with AC_CHECK_HEADERS, as the "gcc -E" run doesn't have the -I flags added.
2008-09-26 05:45:50 +08:00
# A ".." for each directory in $ac_dir_suffix.
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
ac_top_builddir_sub=`$as_echo "$ac_dir_suffix" | sed 's|/[^\\/]*|/..|g;s|/||'`
We support building tcpdump with versions of libpcap other than the one with which it was released, and DLT_BLUETOOTH_HCI_H4_WITH_PHDR might be defined by pcap-bpf.h without pcap/bluetooth.h being present (as appears to be the case on Fedora 9, for example), so check whether <pcap/bluetooth.h> is usable. Update a comment - F9 appears to have a "/usr/include/pcap.h" if you install the libpcap headers. When adding -I flags when running a compiler-based test, add them to CPPFLAGS, not CFLAGS - the latter doesn't work right with AC_CHECK_HEADERS, as the "gcc -E" run doesn't have the -I flags added.
2008-09-26 05:45:50 +08:00
case $ac_top_builddir_sub in
"") ac_top_builddir_sub=. ac_top_build_prefix= ;;
*) ac_top_build_prefix=$ac_top_builddir_sub/ ;;
esac ;;
esac
ac_abs_top_builddir=$ac_pwd
ac_abs_builddir=$ac_pwd$ac_dir_suffix
# for backward compatibility:
ac_top_builddir=$ac_top_build_prefix
Initial revision
1999-10-08 07:47:09 +08:00
From Andrew Church <andrew@users.sourceforge.net>: when testing for "pcap_version", "pcap_debug", and "yydebug", don't add our own functions referring to those variables - GCC 3.4.1 optimizes the test code out before the link is done, as it's in a function that's not called.
2004-08-27 15:17:03 +08:00
case $srcdir in
We support building tcpdump with versions of libpcap other than the one with which it was released, and DLT_BLUETOOTH_HCI_H4_WITH_PHDR might be defined by pcap-bpf.h without pcap/bluetooth.h being present (as appears to be the case on Fedora 9, for example), so check whether <pcap/bluetooth.h> is usable. Update a comment - F9 appears to have a "/usr/include/pcap.h" if you install the libpcap headers. When adding -I flags when running a compiler-based test, add them to CPPFLAGS, not CFLAGS - the latter doesn't work right with AC_CHECK_HEADERS, as the "gcc -E" run doesn't have the -I flags added.
2008-09-26 05:45:50 +08:00
.) # We are building in place.
From Andrew Church <andrew@users.sourceforge.net>: when testing for "pcap_version", "pcap_debug", and "yydebug", don't add our own functions referring to those variables - GCC 3.4.1 optimizes the test code out before the link is done, as it's in a function that's not called.
2004-08-27 15:17:03 +08:00
ac_srcdir=.
We support building tcpdump with versions of libpcap other than the one with which it was released, and DLT_BLUETOOTH_HCI_H4_WITH_PHDR might be defined by pcap-bpf.h without pcap/bluetooth.h being present (as appears to be the case on Fedora 9, for example), so check whether <pcap/bluetooth.h> is usable. Update a comment - F9 appears to have a "/usr/include/pcap.h" if you install the libpcap headers. When adding -I flags when running a compiler-based test, add them to CPPFLAGS, not CFLAGS - the latter doesn't work right with AC_CHECK_HEADERS, as the "gcc -E" run doesn't have the -I flags added.
2008-09-26 05:45:50 +08:00
ac_top_srcdir=$ac_top_builddir_sub
ac_abs_top_srcdir=$ac_pwd ;;
[\\/]* | ?:[\\/]* ) # Absolute name.
From Andrew Church <andrew@users.sourceforge.net>: when testing for "pcap_version", "pcap_debug", and "yydebug", don't add our own functions referring to those variables - GCC 3.4.1 optimizes the test code out before the link is done, as it's in a function that's not called.
2004-08-27 15:17:03 +08:00
ac_srcdir=$srcdir$ac_dir_suffix;
We support building tcpdump with versions of libpcap other than the one with which it was released, and DLT_BLUETOOTH_HCI_H4_WITH_PHDR might be defined by pcap-bpf.h without pcap/bluetooth.h being present (as appears to be the case on Fedora 9, for example), so check whether <pcap/bluetooth.h> is usable. Update a comment - F9 appears to have a "/usr/include/pcap.h" if you install the libpcap headers. When adding -I flags when running a compiler-based test, add them to CPPFLAGS, not CFLAGS - the latter doesn't work right with AC_CHECK_HEADERS, as the "gcc -E" run doesn't have the -I flags added.
2008-09-26 05:45:50 +08:00
ac_top_srcdir=$srcdir
ac_abs_top_srcdir=$srcdir ;;
*) # Relative name.
ac_srcdir=$ac_top_build_prefix$srcdir$ac_dir_suffix
ac_top_srcdir=$ac_top_build_prefix$srcdir
ac_abs_top_srcdir=$ac_pwd/$srcdir ;;
Add -Wpointer-arith to the list of warnings we enable with GCC.
2005-11-08 10:59:40 +08:00
esac
We support building tcpdump with versions of libpcap other than the one with which it was released, and DLT_BLUETOOTH_HCI_H4_WITH_PHDR might be defined by pcap-bpf.h without pcap/bluetooth.h being present (as appears to be the case on Fedora 9, for example), so check whether <pcap/bluetooth.h> is usable. Update a comment - F9 appears to have a "/usr/include/pcap.h" if you install the libpcap headers. When adding -I flags when running a compiler-based test, add them to CPPFLAGS, not CFLAGS - the latter doesn't work right with AC_CHECK_HEADERS, as the "gcc -E" run doesn't have the -I flags added.
2008-09-26 05:45:50 +08:00
ac_abs_srcdir=$ac_abs_top_srcdir$ac_dir_suffix
cd "$ac_dir" || { ac_status=$?; continue; }
# Check for guested configure.
if test -f "$ac_srcdir/configure.gnu"; then
echo &&
$SHELL "$ac_srcdir/configure.gnu" --help=recursive
elif test -f "$ac_srcdir/configure"; then
echo &&
$SHELL "$ac_srcdir/configure" --help=recursive
Regenerate with autoconf 2.57.
2004-01-14 11:15:08 +08:00
else
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
$as_echo "$as_me: WARNING: no configuration information is in $ac_dir" >&2
We support building tcpdump with versions of libpcap other than the one with which it was released, and DLT_BLUETOOTH_HCI_H4_WITH_PHDR might be defined by pcap-bpf.h without pcap/bluetooth.h being present (as appears to be the case on Fedora 9, for example), so check whether <pcap/bluetooth.h> is usable. Update a comment - F9 appears to have a "/usr/include/pcap.h" if you install the libpcap headers. When adding -I flags when running a compiler-based test, add them to CPPFLAGS, not CFLAGS - the latter doesn't work right with AC_CHECK_HEADERS, as the "gcc -E" run doesn't have the -I flags added.
2008-09-26 05:45:50 +08:00
fi || ac_status=$?
cd "$ac_pwd" || { ac_status=$?; break; }
Initial revision
1999-10-08 07:47:09 +08:00
done
fi
Regenerate with autoconf 2.57.
2004-01-14 11:15:08 +08:00
We support building tcpdump with versions of libpcap other than the one with which it was released, and DLT_BLUETOOTH_HCI_H4_WITH_PHDR might be defined by pcap-bpf.h without pcap/bluetooth.h being present (as appears to be the case on Fedora 9, for example), so check whether <pcap/bluetooth.h> is usable. Update a comment - F9 appears to have a "/usr/include/pcap.h" if you install the libpcap headers. When adding -I flags when running a compiler-based test, add them to CPPFLAGS, not CFLAGS - the latter doesn't work right with AC_CHECK_HEADERS, as the "gcc -E" run doesn't have the -I flags added.
2008-09-26 05:45:50 +08:00
test -n "$ac_init_help" && exit $ac_status
Regenerate with autoconf 2.57.
2004-01-14 11:15:08 +08:00
if $ac_init_version; then
From Andrew Church <andrew@users.sourceforge.net>: when testing for "pcap_version", "pcap_debug", and "yydebug", don't add our own functions referring to those variables - GCC 3.4.1 optimizes the test code out before the link is done, as it's in a function that's not called.
2004-08-27 15:17:03 +08:00
cat <<\_ACEOF
Do the version number the way it's now done for libpcap. Use the two-argument version of AC_INIT() - which requires autoconf 2.64 or later, so require that as a minimum - and get the version string from the VERSION file. Use AC_CONFIG_SRCDIR() to say that the source directory needs tcpdump.c; the two-argument version of AC_INIT() doesn't do that. This means that we no longer have a version.c file.
2017-10-17 05:31:14 +08:00
tcpdump configure 4.10.0-PRE-GIT
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
generated by GNU Autoconf 2.69
Regenerate with autoconf 2.57.
2004-01-14 11:15:08 +08:00
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
Copyright (C) 2012 Free Software Foundation, Inc.
Regenerate with autoconf 2.57.
2004-01-14 11:15:08 +08:00
This configure script is free software; the Free Software Foundation
gives unlimited permission to copy, distribute and modify it.
From Andrew Church <andrew@users.sourceforge.net>: when testing for "pcap_version", "pcap_debug", and "yydebug", don't add our own functions referring to those variables - GCC 3.4.1 optimizes the test code out before the link is done, as it's in a function that's not called.
2004-08-27 15:17:03 +08:00
_ACEOF
We support building tcpdump with versions of libpcap other than the one with which it was released, and DLT_BLUETOOTH_HCI_H4_WITH_PHDR might be defined by pcap-bpf.h without pcap/bluetooth.h being present (as appears to be the case on Fedora 9, for example), so check whether <pcap/bluetooth.h> is usable. Update a comment - F9 appears to have a "/usr/include/pcap.h" if you install the libpcap headers. When adding -I flags when running a compiler-based test, add them to CPPFLAGS, not CFLAGS - the latter doesn't work right with AC_CHECK_HEADERS, as the "gcc -E" run doesn't have the -I flags added.
2008-09-26 05:45:50 +08:00
exit
Initial revision
1999-10-08 07:47:09 +08:00
fi
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
## ------------------------ ##
## Autoconf initialization. ##
## ------------------------ ##
Regenerate with autoconf 2.57.
2004-01-14 11:15:08 +08:00
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
# ac_fn_c_try_compile LINENO
# --------------------------
# Try to compile conftest.$ac_ext, and return whether this succeeded.
ac_fn_c_try_compile ()
{
as_lineno=${as_lineno-"$1"} as_lineno_stack=as_lineno_stack=$as_lineno_stack
rm -f conftest.$ac_objext
if { { ac_try="$ac_compile"
case "(($ac_try" in
*\"* | *\`* | *\\*) ac_try_echo=\$ac_try;;
*) ac_try_echo=$ac_try;;
esac
eval ac_try_echo="\"\$as_me:${as_lineno-$LINENO}: $ac_try_echo\""
$as_echo "$ac_try_echo"; } >&5
(eval "$ac_compile") 2>conftest.err
ac_status=$?
if test -s conftest.err; then
grep -v '^ *+' conftest.err >conftest.er1
cat conftest.er1 >&5
mv -f conftest.er1 conftest.err
fi
$as_echo "$as_me:${as_lineno-$LINENO}: \$? = $ac_status" >&5
test $ac_status = 0; } && {
test -z "$ac_c_werror_flag" ||
test ! -s conftest.err
} && test -s conftest.$ac_objext; then :
ac_retval=0
else
$as_echo "$as_me: failed program was:" >&5
sed 's/^/| /' conftest.$ac_ext >&5
Regenerate with autoconf 2.57.
2004-01-14 11:15:08 +08:00
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
ac_retval=1
fi
eval $as_lineno_stack; ${as_lineno_stack:+:} unset as_lineno
as_fn_set_status $ac_retval
} # ac_fn_c_try_compile
# ac_fn_c_try_cpp LINENO
# ----------------------
# Try to preprocess conftest.$ac_ext, and return whether this succeeded.
ac_fn_c_try_cpp ()
Simplify the detection of OpenSSL libcrypto by using standard autoconf macros rather than a local copy of AC_LBL_SSLEAY. AC_LBL_SSLEAY is old and has not kept pace with some more recent developments in packaging like Debian and Ubuntu's multiarch support. The autoconf macros have been updated to handle multiarch so using them means that tcpdump gains the ability to be built with libcrypto on these new multiarch distros and to work successfully with Travis CI, which uses Ubuntu 12, which is one such multiarch distro (see GH-32). Fixes GH-33
2012-10-14 02:21:45 +08:00
{
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
as_lineno=${as_lineno-"$1"} as_lineno_stack=as_lineno_stack=$as_lineno_stack
if { { ac_try="$ac_cpp conftest.$ac_ext"
case "(($ac_try" in
*\"* | *\`* | *\\*) ac_try_echo=\$ac_try;;
*) ac_try_echo=$ac_try;;
esac
eval ac_try_echo="\"\$as_me:${as_lineno-$LINENO}: $ac_try_echo\""
$as_echo "$ac_try_echo"; } >&5
(eval "$ac_cpp conftest.$ac_ext") 2>conftest.err
ac_status=$?
if test -s conftest.err; then
grep -v '^ *+' conftest.err >conftest.er1
cat conftest.er1 >&5
mv -f conftest.er1 conftest.err
fi
$as_echo "$as_me:${as_lineno-$LINENO}: \$? = $ac_status" >&5
test $ac_status = 0; } > conftest.i && {
test -z "$ac_c_preproc_warn_flag$ac_c_werror_flag" ||
test ! -s conftest.err
}; then :
ac_retval=0
else
$as_echo "$as_me: failed program was:" >&5
sed 's/^/| /' conftest.$ac_ext >&5
Regenerate with autoconf 2.57.
2004-01-14 11:15:08 +08:00
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
ac_retval=1
fi
eval $as_lineno_stack; ${as_lineno_stack:+:} unset as_lineno
as_fn_set_status $ac_retval
Regenerate with autoconf 2.57.
2004-01-14 11:15:08 +08:00
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
} # ac_fn_c_try_cpp
Simplify the detection of OpenSSL libcrypto by using standard autoconf macros rather than a local copy of AC_LBL_SSLEAY. AC_LBL_SSLEAY is old and has not kept pace with some more recent developments in packaging like Debian and Ubuntu's multiarch support. The autoconf macros have been updated to handle multiarch so using them means that tcpdump gains the ability to be built with libcrypto on these new multiarch distros and to work successfully with Travis CI, which uses Ubuntu 12, which is one such multiarch distro (see GH-32). Fixes GH-33
2012-10-14 02:21:45 +08:00
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
# ac_fn_c_check_header_mongrel LINENO HEADER VAR INCLUDES
# -------------------------------------------------------
# Tests whether HEADER exists, giving a warning if it cannot be compiled using
# the include files in INCLUDES and setting the cache variable VAR
# accordingly.
ac_fn_c_check_header_mongrel ()
{
as_lineno=${as_lineno-"$1"} as_lineno_stack=as_lineno_stack=$as_lineno_stack
if eval \${$3+:} false; then :
{ $as_echo "$as_me:${as_lineno-$LINENO}: checking for $2" >&5
$as_echo_n "checking for $2... " >&6; }
if eval \${$3+:} false; then :
$as_echo_n "(cached) " >&6
fi
eval ac_res=\$$3
{ $as_echo "$as_me:${as_lineno-$LINENO}: result: $ac_res" >&5
$as_echo "$ac_res" >&6; }
else
# Is the header compilable?
{ $as_echo "$as_me:${as_lineno-$LINENO}: checking $2 usability" >&5
$as_echo_n "checking $2 usability... " >&6; }
cat confdefs.h - <<_ACEOF >conftest.$ac_ext
/* end confdefs.h. */
$4
#include <$2>
_ACEOF
if ac_fn_c_try_compile "$LINENO"; then :
ac_header_compiler=yes
else
ac_header_compiler=no
fi
rm -f core conftest.err conftest.$ac_objext conftest.$ac_ext
{ $as_echo "$as_me:${as_lineno-$LINENO}: result: $ac_header_compiler" >&5
$as_echo "$ac_header_compiler" >&6; }
Simplify the detection of OpenSSL libcrypto by using standard autoconf macros rather than a local copy of AC_LBL_SSLEAY. AC_LBL_SSLEAY is old and has not kept pace with some more recent developments in packaging like Debian and Ubuntu's multiarch support. The autoconf macros have been updated to handle multiarch so using them means that tcpdump gains the ability to be built with libcrypto on these new multiarch distros and to work successfully with Travis CI, which uses Ubuntu 12, which is one such multiarch distro (see GH-32). Fixes GH-33
2012-10-14 02:21:45 +08:00
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
# Is the header present?
{ $as_echo "$as_me:${as_lineno-$LINENO}: checking $2 presence" >&5
$as_echo_n "checking $2 presence... " >&6; }
cat confdefs.h - <<_ACEOF >conftest.$ac_ext
/* end confdefs.h. */
#include <$2>
_ACEOF
if ac_fn_c_try_cpp "$LINENO"; then :
ac_header_preproc=yes
else
ac_header_preproc=no
fi
rm -f conftest.err conftest.i conftest.$ac_ext
{ $as_echo "$as_me:${as_lineno-$LINENO}: result: $ac_header_preproc" >&5
$as_echo "$ac_header_preproc" >&6; }
Simplify the detection of OpenSSL libcrypto by using standard autoconf macros rather than a local copy of AC_LBL_SSLEAY. AC_LBL_SSLEAY is old and has not kept pace with some more recent developments in packaging like Debian and Ubuntu's multiarch support. The autoconf macros have been updated to handle multiarch so using them means that tcpdump gains the ability to be built with libcrypto on these new multiarch distros and to work successfully with Travis CI, which uses Ubuntu 12, which is one such multiarch distro (see GH-32). Fixes GH-33
2012-10-14 02:21:45 +08:00
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
# So? What about this header?
case $ac_header_compiler:$ac_header_preproc:$ac_c_preproc_warn_flag in #((
yes:no: )
{ $as_echo "$as_me:${as_lineno-$LINENO}: WARNING: $2: accepted by the compiler, rejected by the preprocessor!" >&5
$as_echo "$as_me: WARNING: $2: accepted by the compiler, rejected by the preprocessor!" >&2;}
{ $as_echo "$as_me:${as_lineno-$LINENO}: WARNING: $2: proceeding with the compiler's result" >&5
$as_echo "$as_me: WARNING: $2: proceeding with the compiler's result" >&2;}
;;
no:yes:* )
{ $as_echo "$as_me:${as_lineno-$LINENO}: WARNING: $2: present but cannot be compiled" >&5
$as_echo "$as_me: WARNING: $2: present but cannot be compiled" >&2;}
{ $as_echo "$as_me:${as_lineno-$LINENO}: WARNING: $2: check for missing prerequisite headers?" >&5
$as_echo "$as_me: WARNING: $2: check for missing prerequisite headers?" >&2;}
{ $as_echo "$as_me:${as_lineno-$LINENO}: WARNING: $2: see the Autoconf documentation" >&5
$as_echo "$as_me: WARNING: $2: see the Autoconf documentation" >&2;}
{ $as_echo "$as_me:${as_lineno-$LINENO}: WARNING: $2: section \"Present But Cannot Be Compiled\"" >&5
$as_echo "$as_me: WARNING: $2: section \"Present But Cannot Be Compiled\"" >&2;}
{ $as_echo "$as_me:${as_lineno-$LINENO}: WARNING: $2: proceeding with the compiler's result" >&5
$as_echo "$as_me: WARNING: $2: proceeding with the compiler's result" >&2;}
;;
esac
{ $as_echo "$as_me:${as_lineno-$LINENO}: checking for $2" >&5
$as_echo_n "checking for $2... " >&6; }
if eval \${$3+:} false; then :
$as_echo_n "(cached) " >&6
else
eval "$3=\$ac_header_compiler"
fi
eval ac_res=\$$3
{ $as_echo "$as_me:${as_lineno-$LINENO}: result: $ac_res" >&5
$as_echo "$ac_res" >&6; }
fi
eval $as_lineno_stack; ${as_lineno_stack:+:} unset as_lineno
Simplify the detection of OpenSSL libcrypto by using standard autoconf macros rather than a local copy of AC_LBL_SSLEAY. AC_LBL_SSLEAY is old and has not kept pace with some more recent developments in packaging like Debian and Ubuntu's multiarch support. The autoconf macros have been updated to handle multiarch so using them means that tcpdump gains the ability to be built with libcrypto on these new multiarch distros and to work successfully with Travis CI, which uses Ubuntu 12, which is one such multiarch distro (see GH-32). Fixes GH-33
2012-10-14 02:21:45 +08:00
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
} # ac_fn_c_check_header_mongrel
Simplify the detection of OpenSSL libcrypto by using standard autoconf macros rather than a local copy of AC_LBL_SSLEAY. AC_LBL_SSLEAY is old and has not kept pace with some more recent developments in packaging like Debian and Ubuntu's multiarch support. The autoconf macros have been updated to handle multiarch so using them means that tcpdump gains the ability to be built with libcrypto on these new multiarch distros and to work successfully with Travis CI, which uses Ubuntu 12, which is one such multiarch distro (see GH-32). Fixes GH-33
2012-10-14 02:21:45 +08:00
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
# ac_fn_c_try_run LINENO
# ----------------------
# Try to link conftest.$ac_ext, and return whether this succeeded. Assumes
# that executables *can* be run.
ac_fn_c_try_run ()
{
as_lineno=${as_lineno-"$1"} as_lineno_stack=as_lineno_stack=$as_lineno_stack
if { { ac_try="$ac_link"
case "(($ac_try" in
*\"* | *\`* | *\\*) ac_try_echo=\$ac_try;;
*) ac_try_echo=$ac_try;;
esac
eval ac_try_echo="\"\$as_me:${as_lineno-$LINENO}: $ac_try_echo\""
$as_echo "$ac_try_echo"; } >&5
(eval "$ac_link") 2>&5
ac_status=$?
$as_echo "$as_me:${as_lineno-$LINENO}: \$? = $ac_status" >&5
test $ac_status = 0; } && { ac_try='./conftest$ac_exeext'
{ { case "(($ac_try" in
*\"* | *\`* | *\\*) ac_try_echo=\$ac_try;;
*) ac_try_echo=$ac_try;;
esac
eval ac_try_echo="\"\$as_me:${as_lineno-$LINENO}: $ac_try_echo\""
$as_echo "$ac_try_echo"; } >&5
(eval "$ac_try") 2>&5
ac_status=$?
$as_echo "$as_me:${as_lineno-$LINENO}: \$? = $ac_status" >&5
test $ac_status = 0; }; }; then :
ac_retval=0
else
$as_echo "$as_me: program exited with status $ac_status" >&5
$as_echo "$as_me: failed program was:" >&5
sed 's/^/| /' conftest.$ac_ext >&5
Simplify the detection of OpenSSL libcrypto by using standard autoconf macros rather than a local copy of AC_LBL_SSLEAY. AC_LBL_SSLEAY is old and has not kept pace with some more recent developments in packaging like Debian and Ubuntu's multiarch support. The autoconf macros have been updated to handle multiarch so using them means that tcpdump gains the ability to be built with libcrypto on these new multiarch distros and to work successfully with Travis CI, which uses Ubuntu 12, which is one such multiarch distro (see GH-32). Fixes GH-33
2012-10-14 02:21:45 +08:00
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
ac_retval=$ac_status
fi
rm -rf conftest.dSYM conftest_ipa8_conftest.oo
eval $as_lineno_stack; ${as_lineno_stack:+:} unset as_lineno
as_fn_set_status $ac_retval
Simplify the detection of OpenSSL libcrypto by using standard autoconf macros rather than a local copy of AC_LBL_SSLEAY. AC_LBL_SSLEAY is old and has not kept pace with some more recent developments in packaging like Debian and Ubuntu's multiarch support. The autoconf macros have been updated to handle multiarch so using them means that tcpdump gains the ability to be built with libcrypto on these new multiarch distros and to work successfully with Travis CI, which uses Ubuntu 12, which is one such multiarch distro (see GH-32). Fixes GH-33
2012-10-14 02:21:45 +08:00
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
} # ac_fn_c_try_run
Simplify the detection of OpenSSL libcrypto by using standard autoconf macros rather than a local copy of AC_LBL_SSLEAY. AC_LBL_SSLEAY is old and has not kept pace with some more recent developments in packaging like Debian and Ubuntu's multiarch support. The autoconf macros have been updated to handle multiarch so using them means that tcpdump gains the ability to be built with libcrypto on these new multiarch distros and to work successfully with Travis CI, which uses Ubuntu 12, which is one such multiarch distro (see GH-32). Fixes GH-33
2012-10-14 02:21:45 +08:00
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
# ac_fn_c_check_header_compile LINENO HEADER VAR INCLUDES
# -------------------------------------------------------
# Tests whether HEADER exists and can be compiled using the include files in
# INCLUDES, setting the cache variable VAR accordingly.
ac_fn_c_check_header_compile ()
{
as_lineno=${as_lineno-"$1"} as_lineno_stack=as_lineno_stack=$as_lineno_stack
{ $as_echo "$as_me:${as_lineno-$LINENO}: checking for $2" >&5
$as_echo_n "checking for $2... " >&6; }
if eval \${$3+:} false; then :
$as_echo_n "(cached) " >&6
else
cat confdefs.h - <<_ACEOF >conftest.$ac_ext
/* end confdefs.h. */
$4
#include <$2>
Simplify the detection of OpenSSL libcrypto by using standard autoconf macros rather than a local copy of AC_LBL_SSLEAY. AC_LBL_SSLEAY is old and has not kept pace with some more recent developments in packaging like Debian and Ubuntu's multiarch support. The autoconf macros have been updated to handle multiarch so using them means that tcpdump gains the ability to be built with libcrypto on these new multiarch distros and to work successfully with Travis CI, which uses Ubuntu 12, which is one such multiarch distro (see GH-32). Fixes GH-33
2012-10-14 02:21:45 +08:00
_ACEOF
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
if ac_fn_c_try_compile "$LINENO"; then :
eval "$3=yes"
else
eval "$3=no"
fi
rm -f core conftest.err conftest.$ac_objext conftest.$ac_ext
fi
eval ac_res=\$$3
{ $as_echo "$as_me:${as_lineno-$LINENO}: result: $ac_res" >&5
$as_echo "$ac_res" >&6; }
eval $as_lineno_stack; ${as_lineno_stack:+:} unset as_lineno
Simplify the detection of OpenSSL libcrypto by using standard autoconf macros rather than a local copy of AC_LBL_SSLEAY. AC_LBL_SSLEAY is old and has not kept pace with some more recent developments in packaging like Debian and Ubuntu's multiarch support. The autoconf macros have been updated to handle multiarch so using them means that tcpdump gains the ability to be built with libcrypto on these new multiarch distros and to work successfully with Travis CI, which uses Ubuntu 12, which is one such multiarch distro (see GH-32). Fixes GH-33
2012-10-14 02:21:45 +08:00
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
} # ac_fn_c_check_header_compile
Simplify the detection of OpenSSL libcrypto by using standard autoconf macros rather than a local copy of AC_LBL_SSLEAY. AC_LBL_SSLEAY is old and has not kept pace with some more recent developments in packaging like Debian and Ubuntu's multiarch support. The autoconf macros have been updated to handle multiarch so using them means that tcpdump gains the ability to be built with libcrypto on these new multiarch distros and to work successfully with Travis CI, which uses Ubuntu 12, which is one such multiarch distro (see GH-32). Fixes GH-33
2012-10-14 02:21:45 +08:00
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
# ac_fn_c_try_link LINENO
# -----------------------
# Try to link conftest.$ac_ext, and return whether this succeeded.
ac_fn_c_try_link ()
{
as_lineno=${as_lineno-"$1"} as_lineno_stack=as_lineno_stack=$as_lineno_stack
rm -f conftest.$ac_objext conftest$ac_exeext
if { { ac_try="$ac_link"
case "(($ac_try" in
*\"* | *\`* | *\\*) ac_try_echo=\$ac_try;;
*) ac_try_echo=$ac_try;;
esac
eval ac_try_echo="\"\$as_me:${as_lineno-$LINENO}: $ac_try_echo\""
$as_echo "$ac_try_echo"; } >&5
(eval "$ac_link") 2>conftest.err
ac_status=$?
if test -s conftest.err; then
grep -v '^ *+' conftest.err >conftest.er1
cat conftest.er1 >&5
mv -f conftest.er1 conftest.err
fi
$as_echo "$as_me:${as_lineno-$LINENO}: \$? = $ac_status" >&5
test $ac_status = 0; } && {
test -z "$ac_c_werror_flag" ||
test ! -s conftest.err
} && test -s conftest$ac_exeext && {
test "$cross_compiling" = yes ||
test -x conftest$ac_exeext
}; then :
ac_retval=0
else
$as_echo "$as_me: failed program was:" >&5
sed 's/^/| /' conftest.$ac_ext >&5
Simplify the detection of OpenSSL libcrypto by using standard autoconf macros rather than a local copy of AC_LBL_SSLEAY. AC_LBL_SSLEAY is old and has not kept pace with some more recent developments in packaging like Debian and Ubuntu's multiarch support. The autoconf macros have been updated to handle multiarch so using them means that tcpdump gains the ability to be built with libcrypto on these new multiarch distros and to work successfully with Travis CI, which uses Ubuntu 12, which is one such multiarch distro (see GH-32). Fixes GH-33
2012-10-14 02:21:45 +08:00
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
ac_retval=1
fi
# Delete the IPA/IPO (Inter Procedural Analysis/Optimization) information
# created by the PGI compiler (conftest_ipa8_conftest.oo), as it would
# interfere with the next link command; also delete a directory that is
# left behind by Apple's compiler. We do this before executing the actions.
rm -rf conftest.dSYM conftest_ipa8_conftest.oo
eval $as_lineno_stack; ${as_lineno_stack:+:} unset as_lineno
as_fn_set_status $ac_retval
From Andrew Church <andrew@users.sourceforge.net>: when testing for "pcap_version", "pcap_debug", and "yydebug", don't add our own functions referring to those variables - GCC 3.4.1 optimizes the test code out before the link is done, as it's in a function that's not called.
2004-08-27 15:17:03 +08:00
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
} # ac_fn_c_try_link
From Andrew Church <andrew@users.sourceforge.net>: when testing for "pcap_version", "pcap_debug", and "yydebug", don't add our own functions referring to those variables - GCC 3.4.1 optimizes the test code out before the link is done, as it's in a function that's not called.
2004-08-27 15:17:03 +08:00
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
# ac_fn_c_check_func LINENO FUNC VAR
# ----------------------------------
# Tests whether FUNC exists, setting the cache variable VAR accordingly
ac_fn_c_check_func ()
{
as_lineno=${as_lineno-"$1"} as_lineno_stack=as_lineno_stack=$as_lineno_stack
{ $as_echo "$as_me:${as_lineno-$LINENO}: checking for $2" >&5
$as_echo_n "checking for $2... " >&6; }
if eval \${$3+:} false; then :
$as_echo_n "(cached) " >&6
else
cat confdefs.h - <<_ACEOF >conftest.$ac_ext
/* end confdefs.h. */
/* Define $2 to an innocuous variant, in case <limits.h> declares $2.
For example, HP-UX 11i <limits.h> declares gettimeofday. */
#define $2 innocuous_$2
From Andrew Church <andrew@users.sourceforge.net>: when testing for "pcap_version", "pcap_debug", and "yydebug", don't add our own functions referring to those variables - GCC 3.4.1 optimizes the test code out before the link is done, as it's in a function that's not called.
2004-08-27 15:17:03 +08:00
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
/* System header to define __stub macros and hopefully few prototypes,
which can conflict with char $2 (); below.
Prefer <limits.h> to <assert.h> if __STDC__ is defined, since
<limits.h> exists even on freestanding compilers. */
From Andrew Church <andrew@users.sourceforge.net>: when testing for "pcap_version", "pcap_debug", and "yydebug", don't add our own functions referring to those variables - GCC 3.4.1 optimizes the test code out before the link is done, as it's in a function that's not called.
2004-08-27 15:17:03 +08:00
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
#ifdef __STDC__
# include <limits.h>
#else
# include <assert.h>
#endif
Regenerate with autoconf 2.57.
2004-01-14 11:15:08 +08:00
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
#undef $2
Regenerate with autoconf 2.57.
2004-01-14 11:15:08 +08:00
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
/* Override any GCC internal prototype to avoid an error.
Use char because int might match the return type of a GCC
builtin and then its argument prototype would still apply. */
#ifdef __cplusplus
extern "C"
#endif
char $2 ();
/* The GNU C library defines this for functions which it implements
to always fail with ENOSYS. Some functions are actually named
something starting with __ and the normal name is an alias. */
#if defined __stub_$2 || defined __stub___$2
choke me
#endif
From Andrew Church <andrew@users.sourceforge.net>: when testing for "pcap_version", "pcap_debug", and "yydebug", don't add our own functions referring to those variables - GCC 3.4.1 optimizes the test code out before the link is done, as it's in a function that's not called.
2004-08-27 15:17:03 +08:00
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
int
main ()
{
return $2 ();
;
return 0;
}
From Andrew Church <andrew@users.sourceforge.net>: when testing for "pcap_version", "pcap_debug", and "yydebug", don't add our own functions referring to those variables - GCC 3.4.1 optimizes the test code out before the link is done, as it's in a function that's not called.
2004-08-27 15:17:03 +08:00
_ACEOF
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
if ac_fn_c_try_link "$LINENO"; then :
eval "$3=yes"
else
eval "$3=no"
fi
rm -f core conftest.err conftest.$ac_objext \
conftest$ac_exeext conftest.$ac_ext
fi
eval ac_res=\$$3
{ $as_echo "$as_me:${as_lineno-$LINENO}: result: $ac_res" >&5
$as_echo "$ac_res" >&6; }
eval $as_lineno_stack; ${as_lineno_stack:+:} unset as_lineno
From Andrew Church <andrew@users.sourceforge.net>: when testing for "pcap_version", "pcap_debug", and "yydebug", don't add our own functions referring to those variables - GCC 3.4.1 optimizes the test code out before the link is done, as it's in a function that's not called.
2004-08-27 15:17:03 +08:00
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
} # ac_fn_c_check_func
Check for extra networking libraries before checking for IPv6. On some platforms, such as SunOS 5.x, building the "do we have IPv6 support?" test program requires the extra networking libraries, so we need to know what extra networking libraries are required before doing that test.
2013-04-07 04:03:58 +08:00
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
# ac_fn_c_check_decl LINENO SYMBOL VAR INCLUDES
# ---------------------------------------------
# Tests whether SYMBOL is declared in INCLUDES, setting cache variable VAR
# accordingly.
ac_fn_c_check_decl ()
{
as_lineno=${as_lineno-"$1"} as_lineno_stack=as_lineno_stack=$as_lineno_stack
as_decl_name=`echo $2|sed 's/ *(.*//'`
as_decl_use=`echo $2|sed -e 's/(/((/' -e 's/)/) 0&/' -e 's/,/) 0& (/g'`
{ $as_echo "$as_me:${as_lineno-$LINENO}: checking whether $as_decl_name is declared" >&5
$as_echo_n "checking whether $as_decl_name is declared... " >&6; }
if eval \${$3+:} false; then :
$as_echo_n "(cached) " >&6
else
cat confdefs.h - <<_ACEOF >conftest.$ac_ext
/* end confdefs.h. */
$4
int
main ()
{
#ifndef $as_decl_name
#ifdef __cplusplus
(void) $as_decl_use;
#else
(void) $as_decl_name;
#endif
#endif
;
return 0;
}
From Andrew Church <andrew@users.sourceforge.net>: when testing for "pcap_version", "pcap_debug", and "yydebug", don't add our own functions referring to those variables - GCC 3.4.1 optimizes the test code out before the link is done, as it's in a function that's not called.
2004-08-27 15:17:03 +08:00
_ACEOF
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
if ac_fn_c_try_compile "$LINENO"; then :
eval "$3=yes"
else
eval "$3=no"
fi
rm -f core conftest.err conftest.$ac_objext conftest.$ac_ext
fi
eval ac_res=\$$3
{ $as_echo "$as_me:${as_lineno-$LINENO}: result: $ac_res" >&5
$as_echo "$ac_res" >&6; }
eval $as_lineno_stack; ${as_lineno_stack:+:} unset as_lineno
From Andrew Church <andrew@users.sourceforge.net>: when testing for "pcap_version", "pcap_debug", and "yydebug", don't add our own functions referring to those variables - GCC 3.4.1 optimizes the test code out before the link is done, as it's in a function that's not called.
2004-08-27 15:17:03 +08:00
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
} # ac_fn_c_check_decl
Check for extra networking libraries before checking for IPv6. On some platforms, such as SunOS 5.x, building the "do we have IPv6 support?" test program requires the extra networking libraries, so we need to know what extra networking libraries are required before doing that test.
2013-04-07 04:03:58 +08:00
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
# ac_fn_c_check_type LINENO TYPE VAR INCLUDES
# -------------------------------------------
# Tests whether TYPE exists after having included INCLUDES, setting cache
# variable VAR accordingly.
ac_fn_c_check_type ()
{
as_lineno=${as_lineno-"$1"} as_lineno_stack=as_lineno_stack=$as_lineno_stack
{ $as_echo "$as_me:${as_lineno-$LINENO}: checking for $2" >&5
$as_echo_n "checking for $2... " >&6; }
if eval \${$3+:} false; then :
$as_echo_n "(cached) " >&6
else
eval "$3=no"
cat confdefs.h - <<_ACEOF >conftest.$ac_ext
/* end confdefs.h. */
$4
int
main ()
{
if (sizeof ($2))
return 0;
;
return 0;
}
From Andrew Church <andrew@users.sourceforge.net>: when testing for "pcap_version", "pcap_debug", and "yydebug", don't add our own functions referring to those variables - GCC 3.4.1 optimizes the test code out before the link is done, as it's in a function that's not called.
2004-08-27 15:17:03 +08:00
_ACEOF
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
if ac_fn_c_try_compile "$LINENO"; then :
cat confdefs.h - <<_ACEOF >conftest.$ac_ext
/* end confdefs.h. */
$4
int
main ()
{
if (sizeof (($2)))
return 0;
;
return 0;
}
_ACEOF
if ac_fn_c_try_compile "$LINENO"; then :
From Andrew Church <andrew@users.sourceforge.net>: when testing for "pcap_version", "pcap_debug", and "yydebug", don't add our own functions referring to those variables - GCC 3.4.1 optimizes the test code out before the link is done, as it's in a function that's not called.
2004-08-27 15:17:03 +08:00
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
else
eval "$3=yes"
fi
rm -f core conftest.err conftest.$ac_objext conftest.$ac_ext
fi
rm -f core conftest.err conftest.$ac_objext conftest.$ac_ext
fi
eval ac_res=\$$3
{ $as_echo "$as_me:${as_lineno-$LINENO}: result: $ac_res" >&5
$as_echo "$ac_res" >&6; }
eval $as_lineno_stack; ${as_lineno_stack:+:} unset as_lineno
Check for extra networking libraries before checking for IPv6. On some platforms, such as SunOS 5.x, building the "do we have IPv6 support?" test program requires the extra networking libraries, so we need to know what extra networking libraries are required before doing that test.
2013-04-07 04:03:58 +08:00
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
} # ac_fn_c_check_type
cat >config.log <<_ACEOF
This file contains any messages produced by compilers while
running configure, to aid debugging if configure makes a mistake.
Check for extra networking libraries before checking for IPv6. On some platforms, such as SunOS 5.x, building the "do we have IPv6 support?" test program requires the extra networking libraries, so we need to know what extra networking libraries are required before doing that test.
2013-04-07 04:03:58 +08:00
Do the version number the way it's now done for libpcap. Use the two-argument version of AC_INIT() - which requires autoconf 2.64 or later, so require that as a minimum - and get the version string from the VERSION file. Use AC_CONFIG_SRCDIR() to say that the source directory needs tcpdump.c; the two-argument version of AC_INIT() doesn't do that. This means that we no longer have a version.c file.
2017-10-17 05:31:14 +08:00
It was created by tcpdump $as_me 4.10.0-PRE-GIT, which was
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
generated by GNU Autoconf 2.69. Invocation command line was
Check for extra networking libraries before checking for IPv6. On some platforms, such as SunOS 5.x, building the "do we have IPv6 support?" test program requires the extra networking libraries, so we need to know what extra networking libraries are required before doing that test.
2013-04-07 04:03:58 +08:00
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
$ $0 $@
Check for extra networking libraries before checking for IPv6. On some platforms, such as SunOS 5.x, building the "do we have IPv6 support?" test program requires the extra networking libraries, so we need to know what extra networking libraries are required before doing that test.
2013-04-07 04:03:58 +08:00
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
_ACEOF
exec 5>>config.log
{
cat <<_ASUNAME
## --------- ##
## Platform. ##
## --------- ##
Check for extra networking libraries before checking for IPv6. On some platforms, such as SunOS 5.x, building the "do we have IPv6 support?" test program requires the extra networking libraries, so we need to know what extra networking libraries are required before doing that test.
2013-04-07 04:03:58 +08:00
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
hostname = `(hostname || uname -n) 2>/dev/null | sed 1q`
uname -m = `(uname -m) 2>/dev/null || echo unknown`
uname -r = `(uname -r) 2>/dev/null || echo unknown`
uname -s = `(uname -s) 2>/dev/null || echo unknown`
uname -v = `(uname -v) 2>/dev/null || echo unknown`
Check for extra networking libraries before checking for IPv6. On some platforms, such as SunOS 5.x, building the "do we have IPv6 support?" test program requires the extra networking libraries, so we need to know what extra networking libraries are required before doing that test.
2013-04-07 04:03:58 +08:00
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
/usr/bin/uname -p = `(/usr/bin/uname -p) 2>/dev/null || echo unknown`
/bin/uname -X = `(/bin/uname -X) 2>/dev/null || echo unknown`
Check for extra networking libraries before checking for IPv6. On some platforms, such as SunOS 5.x, building the "do we have IPv6 support?" test program requires the extra networking libraries, so we need to know what extra networking libraries are required before doing that test.
2013-04-07 04:03:58 +08:00
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
/bin/arch = `(/bin/arch) 2>/dev/null || echo unknown`
/usr/bin/arch -k = `(/usr/bin/arch -k) 2>/dev/null || echo unknown`
/usr/convex/getsysinfo = `(/usr/convex/getsysinfo) 2>/dev/null || echo unknown`
/usr/bin/hostinfo = `(/usr/bin/hostinfo) 2>/dev/null || echo unknown`
/bin/machine = `(/bin/machine) 2>/dev/null || echo unknown`
/usr/bin/oslevel = `(/usr/bin/oslevel) 2>/dev/null || echo unknown`
/bin/universe = `(/bin/universe) 2>/dev/null || echo unknown`
Check for extra networking libraries before checking for IPv6. On some platforms, such as SunOS 5.x, building the "do we have IPv6 support?" test program requires the extra networking libraries, so we need to know what extra networking libraries are required before doing that test.
2013-04-07 04:03:58 +08:00
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
_ASUNAME
Check for extra networking libraries before checking for IPv6. On some platforms, such as SunOS 5.x, building the "do we have IPv6 support?" test program requires the extra networking libraries, so we need to know what extra networking libraries are required before doing that test.
2013-04-07 04:03:58 +08:00
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
as_save_IFS=$IFS; IFS=$PATH_SEPARATOR
for as_dir in $PATH
do
IFS=$as_save_IFS
test -z "$as_dir" && as_dir=.
$as_echo "PATH: $as_dir"
done
IFS=$as_save_IFS
Check for extra networking libraries before checking for IPv6. On some platforms, such as SunOS 5.x, building the "do we have IPv6 support?" test program requires the extra networking libraries, so we need to know what extra networking libraries are required before doing that test.
2013-04-07 04:03:58 +08:00
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
} >&5
Check for extra networking libraries before checking for IPv6. On some platforms, such as SunOS 5.x, building the "do we have IPv6 support?" test program requires the extra networking libraries, so we need to know what extra networking libraries are required before doing that test.
2013-04-07 04:03:58 +08:00
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
cat >&5 <<_ACEOF
Check for extra networking libraries before checking for IPv6. On some platforms, such as SunOS 5.x, building the "do we have IPv6 support?" test program requires the extra networking libraries, so we need to know what extra networking libraries are required before doing that test.
2013-04-07 04:03:58 +08:00
From Andrew Church <andrew@users.sourceforge.net>: when testing for "pcap_version", "pcap_debug", and "yydebug", don't add our own functions referring to those variables - GCC 3.4.1 optimizes the test code out before the link is done, as it's in a function that's not called.
2004-08-27 15:17:03 +08:00
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
## ----------- ##
## Core tests. ##
## ----------- ##
_ACEOF
# Keep a trace of the command line.
# Strip out --no-create and --no-recursion so they do not pile up.
# Strip out --silent because we don't want to record it for future runs.
# Also quote any args containing shell meta-characters.
# Make two passes to allow for proper duplicate-argument suppression.
ac_configure_args=
ac_configure_args0=
ac_configure_args1=
ac_must_keep_next=false
for ac_pass in 1 2
do
for ac_arg
do
case $ac_arg in
-no-create | --no-c* | -n | -no-recursion | --no-r*) continue ;;
-q | -quiet | --quiet | --quie | --qui | --qu | --q \
| -silent | --silent | --silen | --sile | --sil)
continue ;;
*\'*)
ac_arg=`$as_echo "$ac_arg" | sed "s/'/'\\\\\\\\''/g"` ;;
esac
case $ac_pass in
1) as_fn_append ac_configure_args0 " '$ac_arg'" ;;
2)
as_fn_append ac_configure_args1 " '$ac_arg'"
if test $ac_must_keep_next = true; then
ac_must_keep_next=false # Got value, back to normal.
else
case $ac_arg in
*=* | --config-cache | -C | -disable-* | --disable-* \
| -enable-* | --enable-* | -gas | --g* | -nfp | --nf* \
| -q | -quiet | --q* | -silent | --sil* | -v | -verb* \
| -with-* | --with-* | -without-* | --without-* | --x)
case "$ac_configure_args0 " in
"$ac_configure_args1"*" '$ac_arg' "* ) continue ;;
esac
;;
-* ) ac_must_keep_next=true ;;
esac
fi
as_fn_append ac_configure_args " '$ac_arg'"
;;
esac
done
done
{ ac_configure_args0=; unset ac_configure_args0;}
{ ac_configure_args1=; unset ac_configure_args1;}
# When interrupted or exit'd, cleanup temporary files, and complete
# config.log. We remove comments because anyway the quotes in there
# would cause problems or look ugly.
# WARNING: Use '\'' to represent an apostrophe within the trap.
# WARNING: Do not start the trap code with a newline, due to a FreeBSD 4.0 bug.
trap 'exit_status=$?
# Save into config.log some information that might help in debugging.
{
echo
$as_echo "## ---------------- ##
## Cache variables. ##
## ---------------- ##"
echo
# The following way of writing the cache mishandles newlines in values,
(
for ac_var in `(set) 2>&1 | sed -n '\''s/^\([a-zA-Z_][a-zA-Z0-9_]*\)=.*/\1/p'\''`; do
eval ac_val=\$$ac_var
case $ac_val in #(
*${as_nl}*)
case $ac_var in #(
*_cv_*) { $as_echo "$as_me:${as_lineno-$LINENO}: WARNING: cache variable $ac_var contains a newline" >&5
$as_echo "$as_me: WARNING: cache variable $ac_var contains a newline" >&2;} ;;
esac
case $ac_var in #(
_ | IFS | as_nl) ;; #(
BASH_ARGV | BASH_SOURCE) eval $ac_var= ;; #(
*) { eval $ac_var=; unset $ac_var;} ;;
esac ;;
esac
done
(set) 2>&1 |
case $as_nl`(ac_space='\'' '\''; set) 2>&1` in #(
*${as_nl}ac_space=\ *)
sed -n \
"s/'\''/'\''\\\\'\'''\''/g;
s/^\\([_$as_cr_alnum]*_cv_[_$as_cr_alnum]*\\)=\\(.*\\)/\\1='\''\\2'\''/p"
;; #(
*)
sed -n "/^[_$as_cr_alnum]*_cv_[_$as_cr_alnum]*=/p"
;;
esac |
sort
)
echo
$as_echo "## ----------------- ##
## Output variables. ##
## ----------------- ##"
echo
for ac_var in $ac_subst_vars
do
eval ac_val=\$$ac_var
case $ac_val in
*\'\''*) ac_val=`$as_echo "$ac_val" | sed "s/'\''/'\''\\\\\\\\'\'''\''/g"`;;
esac
$as_echo "$ac_var='\''$ac_val'\''"
done | sort
echo
if test -n "$ac_subst_files"; then
$as_echo "## ------------------- ##
## File substitutions. ##
## ------------------- ##"
echo
for ac_var in $ac_subst_files
do
eval ac_val=\$$ac_var
case $ac_val in
*\'\''*) ac_val=`$as_echo "$ac_val" | sed "s/'\''/'\''\\\\\\\\'\'''\''/g"`;;
esac
$as_echo "$ac_var='\''$ac_val'\''"
done | sort
echo
fi
if test -s confdefs.h; then
$as_echo "## ----------- ##
## confdefs.h. ##
## ----------- ##"
echo
cat confdefs.h
echo
fi
test "$ac_signal" != 0 &&
$as_echo "$as_me: caught signal $ac_signal"
$as_echo "$as_me: exit $exit_status"
} >&5
rm -f core *.core core.conftest.* &&
rm -f -r conftest* confdefs* conf$$* $ac_clean_files &&
exit $exit_status
' 0
for ac_signal in 1 2 13 15; do
trap 'ac_signal='$ac_signal'; as_fn_exit 1' $ac_signal
done
ac_signal=0
# confdefs.h avoids OS command line length limits that DEFS can exceed.
rm -f -r conftest* confdefs.h
$as_echo "/* confdefs.h */" > confdefs.h
# Predefined preprocessor variables.
cat >>confdefs.h <<_ACEOF
#define PACKAGE_NAME "$PACKAGE_NAME"
_ACEOF
cat >>confdefs.h <<_ACEOF
#define PACKAGE_TARNAME "$PACKAGE_TARNAME"
_ACEOF
cat >>confdefs.h <<_ACEOF
#define PACKAGE_VERSION "$PACKAGE_VERSION"
_ACEOF
cat >>confdefs.h <<_ACEOF
#define PACKAGE_STRING "$PACKAGE_STRING"
_ACEOF
cat >>confdefs.h <<_ACEOF
#define PACKAGE_BUGREPORT "$PACKAGE_BUGREPORT"
_ACEOF
cat >>confdefs.h <<_ACEOF
#define PACKAGE_URL "$PACKAGE_URL"
_ACEOF
# Let the site file select an alternate cache file if it wants to.
# Prefer an explicitly selected file to automatically selected ones.
ac_site_file1=NONE
ac_site_file2=NONE
if test -n "$CONFIG_SITE"; then
# We do not want a PATH search for config.site.
case $CONFIG_SITE in #((
-*) ac_site_file1=./$CONFIG_SITE;;
*/*) ac_site_file1=$CONFIG_SITE;;
*) ac_site_file1=./$CONFIG_SITE;;
esac
elif test "x$prefix" != xNONE; then
ac_site_file1=$prefix/share/config.site
ac_site_file2=$prefix/etc/config.site
else
ac_site_file1=$ac_default_prefix/share/config.site
ac_site_file2=$ac_default_prefix/etc/config.site
fi
for ac_site_file in "$ac_site_file1" "$ac_site_file2"
do
test "x$ac_site_file" = xNONE && continue
if test /dev/null != "$ac_site_file" && test -r "$ac_site_file"; then
{ $as_echo "$as_me:${as_lineno-$LINENO}: loading site script $ac_site_file" >&5
$as_echo "$as_me: loading site script $ac_site_file" >&6;}
sed 's/^/| /' "$ac_site_file" >&5
. "$ac_site_file" \
|| { { $as_echo "$as_me:${as_lineno-$LINENO}: error: in \`$ac_pwd':" >&5
$as_echo "$as_me: error: in \`$ac_pwd':" >&2;}
as_fn_error $? "failed to load site script $ac_site_file
See \`config.log' for more details" "$LINENO" 5; }
fi
done
if test -r "$cache_file"; then
# Some versions of bash will fail to source /dev/null (special files
# actually), so we avoid doing that. DJGPP emulates it as a regular file.
if test /dev/null != "$cache_file" && test -f "$cache_file"; then
{ $as_echo "$as_me:${as_lineno-$LINENO}: loading cache $cache_file" >&5
$as_echo "$as_me: loading cache $cache_file" >&6;}
case $cache_file in
[\\/]* | ?:[\\/]* ) . "$cache_file";;
*) . "./$cache_file";;
esac
fi
else
{ $as_echo "$as_me:${as_lineno-$LINENO}: creating cache $cache_file" >&5
$as_echo "$as_me: creating cache $cache_file" >&6;}
>$cache_file
fi
# Check that the precious variables saved in the cache have kept the same
# value.
ac_cache_corrupted=false
for ac_var in $ac_precious_vars; do
eval ac_old_set=\$ac_cv_env_${ac_var}_set
eval ac_new_set=\$ac_env_${ac_var}_set
eval ac_old_val=\$ac_cv_env_${ac_var}_value
eval ac_new_val=\$ac_env_${ac_var}_value
case $ac_old_set,$ac_new_set in
set,)
{ $as_echo "$as_me:${as_lineno-$LINENO}: error: \`$ac_var' was set to \`$ac_old_val' in the previous run" >&5
$as_echo "$as_me: error: \`$ac_var' was set to \`$ac_old_val' in the previous run" >&2;}
ac_cache_corrupted=: ;;
,set)
{ $as_echo "$as_me:${as_lineno-$LINENO}: error: \`$ac_var' was not set in the previous run" >&5
$as_echo "$as_me: error: \`$ac_var' was not set in the previous run" >&2;}
ac_cache_corrupted=: ;;
,);;
*)
if test "x$ac_old_val" != "x$ac_new_val"; then
# differences in whitespace do not lead to failure.
ac_old_val_w=`echo x $ac_old_val`
ac_new_val_w=`echo x $ac_new_val`
if test "$ac_old_val_w" != "$ac_new_val_w"; then
{ $as_echo "$as_me:${as_lineno-$LINENO}: error: \`$ac_var' has changed since the previous run:" >&5
$as_echo "$as_me: error: \`$ac_var' has changed since the previous run:" >&2;}
ac_cache_corrupted=:
else
{ $as_echo "$as_me:${as_lineno-$LINENO}: warning: ignoring whitespace changes in \`$ac_var' since the previous run:" >&5
$as_echo "$as_me: warning: ignoring whitespace changes in \`$ac_var' since the previous run:" >&2;}
eval $ac_var=\$ac_old_val
fi
{ $as_echo "$as_me:${as_lineno-$LINENO}: former value: \`$ac_old_val'" >&5
$as_echo "$as_me: former value: \`$ac_old_val'" >&2;}
{ $as_echo "$as_me:${as_lineno-$LINENO}: current value: \`$ac_new_val'" >&5
$as_echo "$as_me: current value: \`$ac_new_val'" >&2;}
fi;;
esac
# Pass precious variables to config.status.
if test "$ac_new_set" = set; then
case $ac_new_val in
*\'*) ac_arg=$ac_var=`$as_echo "$ac_new_val" | sed "s/'/'\\\\\\\\''/g"` ;;
*) ac_arg=$ac_var=$ac_new_val ;;
esac
case " $ac_configure_args " in
*" '$ac_arg' "*) ;; # Avoid dups. Use of quotes ensures accuracy.
*) as_fn_append ac_configure_args " '$ac_arg'" ;;
esac
fi
done
if $ac_cache_corrupted; then
{ $as_echo "$as_me:${as_lineno-$LINENO}: error: in \`$ac_pwd':" >&5
$as_echo "$as_me: error: in \`$ac_pwd':" >&2;}
{ $as_echo "$as_me:${as_lineno-$LINENO}: error: changes in the environment can compromise the build" >&5
$as_echo "$as_me: error: changes in the environment can compromise the build" >&2;}
as_fn_error $? "run \`make distclean' and/or \`rm $cache_file' and start over" "$LINENO" 5
fi
## -------------------- ##
## Main body of script. ##
## -------------------- ##
We support building tcpdump with versions of libpcap other than the one with which it was released, and DLT_BLUETOOTH_HCI_H4_WITH_PHDR might be defined by pcap-bpf.h without pcap/bluetooth.h being present (as appears to be the case on Fedora 9, for example), so check whether <pcap/bluetooth.h> is usable. Update a comment - F9 appears to have a "/usr/include/pcap.h" if you install the libpcap headers. When adding -I flags when running a compiler-based test, add them to CPPFLAGS, not CFLAGS - the latter doesn't work right with AC_CHECK_HEADERS, as the "gcc -E" run doesn't have the -I flags added.
2008-09-26 05:45:50 +08:00
ac_ext=c
ac_cpp='$CPP $CPPFLAGS'
ac_compile='$CC -c $CFLAGS $CPPFLAGS conftest.$ac_ext >&5'
ac_link='$CC -o conftest$ac_exeext $CFLAGS $CPPFLAGS $LDFLAGS conftest.$ac_ext $LIBS >&5'
ac_compiler_gnu=$ac_cv_c_compiler_gnu
From Andrew Church <andrew@users.sourceforge.net>: when testing for "pcap_version", "pcap_debug", and "yydebug", don't add our own functions referring to those variables - GCC 3.4.1 optimizes the test code out before the link is done, as it's in a function that's not called.
2004-08-27 15:17:03 +08:00
Regenerate with autoconf 2.57.
2004-01-14 11:15:08 +08:00
Do the version number the way it's now done for libpcap. Use the two-argument version of AC_INIT() - which requires autoconf 2.64 or later, so require that as a minimum - and get the version string from the VERSION file. Use AC_CONFIG_SRCDIR() to say that the source directory needs tcpdump.c; the two-argument version of AC_INIT() doesn't do that. This means that we no longer have a version.c file.
2017-10-17 05:31:14 +08:00
Regenerate with autoconf 2.57.
2004-01-14 11:15:08 +08:00
ac_aux_dir=
We support building tcpdump with versions of libpcap other than the one with which it was released, and DLT_BLUETOOTH_HCI_H4_WITH_PHDR might be defined by pcap-bpf.h without pcap/bluetooth.h being present (as appears to be the case on Fedora 9, for example), so check whether <pcap/bluetooth.h> is usable. Update a comment - F9 appears to have a "/usr/include/pcap.h" if you install the libpcap headers. When adding -I flags when running a compiler-based test, add them to CPPFLAGS, not CFLAGS - the latter doesn't work right with AC_CHECK_HEADERS, as the "gcc -E" run doesn't have the -I flags added.
2008-09-26 05:45:50 +08:00
for ac_dir in "$srcdir" "$srcdir/.." "$srcdir/../.."; do
if test -f "$ac_dir/install-sh"; then
Regenerate with autoconf 2.57.
2004-01-14 11:15:08 +08:00
ac_aux_dir=$ac_dir
ac_install_sh="$ac_aux_dir/install-sh -c"
break
We support building tcpdump with versions of libpcap other than the one with which it was released, and DLT_BLUETOOTH_HCI_H4_WITH_PHDR might be defined by pcap-bpf.h without pcap/bluetooth.h being present (as appears to be the case on Fedora 9, for example), so check whether <pcap/bluetooth.h> is usable. Update a comment - F9 appears to have a "/usr/include/pcap.h" if you install the libpcap headers. When adding -I flags when running a compiler-based test, add them to CPPFLAGS, not CFLAGS - the latter doesn't work right with AC_CHECK_HEADERS, as the "gcc -E" run doesn't have the -I flags added.
2008-09-26 05:45:50 +08:00
elif test -f "$ac_dir/install.sh"; then
Regenerate with autoconf 2.57.
2004-01-14 11:15:08 +08:00
ac_aux_dir=$ac_dir
ac_install_sh="$ac_aux_dir/install.sh -c"
break
We support building tcpdump with versions of libpcap other than the one with which it was released, and DLT_BLUETOOTH_HCI_H4_WITH_PHDR might be defined by pcap-bpf.h without pcap/bluetooth.h being present (as appears to be the case on Fedora 9, for example), so check whether <pcap/bluetooth.h> is usable. Update a comment - F9 appears to have a "/usr/include/pcap.h" if you install the libpcap headers. When adding -I flags when running a compiler-based test, add them to CPPFLAGS, not CFLAGS - the latter doesn't work right with AC_CHECK_HEADERS, as the "gcc -E" run doesn't have the -I flags added.
2008-09-26 05:45:50 +08:00
elif test -f "$ac_dir/shtool"; then
Regenerate with autoconf 2.57.
2004-01-14 11:15:08 +08:00
ac_aux_dir=$ac_dir
ac_install_sh="$ac_aux_dir/shtool install -c"
break
fi
done
if test -z "$ac_aux_dir"; then
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
as_fn_error $? "cannot find install-sh, install.sh, or shtool in \"$srcdir\" \"$srcdir/..\" \"$srcdir/../..\"" "$LINENO" 5
Regenerate with autoconf 2.57.
2004-01-14 11:15:08 +08:00
fi
We support building tcpdump with versions of libpcap other than the one with which it was released, and DLT_BLUETOOTH_HCI_H4_WITH_PHDR might be defined by pcap-bpf.h without pcap/bluetooth.h being present (as appears to be the case on Fedora 9, for example), so check whether <pcap/bluetooth.h> is usable. Update a comment - F9 appears to have a "/usr/include/pcap.h" if you install the libpcap headers. When adding -I flags when running a compiler-based test, add them to CPPFLAGS, not CFLAGS - the latter doesn't work right with AC_CHECK_HEADERS, as the "gcc -E" run doesn't have the -I flags added.
2008-09-26 05:45:50 +08:00
# These three variables are undocumented and unsupported,
# and are intended to be withdrawn in a future Autoconf release.
# They can cause serious problems if a builder's source tree is in a directory
# whose full name contains unusual characters.
ac_config_guess="$SHELL $ac_aux_dir/config.guess" # Please don't use this var.
ac_config_sub="$SHELL $ac_aux_dir/config.sub" # Please don't use this var.
ac_configure="$SHELL $ac_aux_dir/configure" # Please don't use this var.
Regenerate with autoconf 2.57.
2004-01-14 11:15:08 +08:00
# Make sure we can run config.sub.
We support building tcpdump with versions of libpcap other than the one with which it was released, and DLT_BLUETOOTH_HCI_H4_WITH_PHDR might be defined by pcap-bpf.h without pcap/bluetooth.h being present (as appears to be the case on Fedora 9, for example), so check whether <pcap/bluetooth.h> is usable. Update a comment - F9 appears to have a "/usr/include/pcap.h" if you install the libpcap headers. When adding -I flags when running a compiler-based test, add them to CPPFLAGS, not CFLAGS - the latter doesn't work right with AC_CHECK_HEADERS, as the "gcc -E" run doesn't have the -I flags added.
2008-09-26 05:45:50 +08:00
$SHELL "$ac_aux_dir/config.sub" sun4 >/dev/null 2>&1 ||
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
as_fn_error $? "cannot run $SHELL $ac_aux_dir/config.sub" "$LINENO" 5
Regenerate with autoconf 2.57.
2004-01-14 11:15:08 +08:00
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
{ $as_echo "$as_me:${as_lineno-$LINENO}: checking build system type" >&5
$as_echo_n "checking build system type... " >&6; }
if ${ac_cv_build+:} false; then :
$as_echo_n "(cached) " >&6
Regenerate with autoconf 2.57.
2004-01-14 11:15:08 +08:00
else
We support building tcpdump with versions of libpcap other than the one with which it was released, and DLT_BLUETOOTH_HCI_H4_WITH_PHDR might be defined by pcap-bpf.h without pcap/bluetooth.h being present (as appears to be the case on Fedora 9, for example), so check whether <pcap/bluetooth.h> is usable. Update a comment - F9 appears to have a "/usr/include/pcap.h" if you install the libpcap headers. When adding -I flags when running a compiler-based test, add them to CPPFLAGS, not CFLAGS - the latter doesn't work right with AC_CHECK_HEADERS, as the "gcc -E" run doesn't have the -I flags added.
2008-09-26 05:45:50 +08:00
ac_build_alias=$build_alias
test "x$ac_build_alias" = x &&
ac_build_alias=`$SHELL "$ac_aux_dir/config.guess"`
test "x$ac_build_alias" = x &&
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
as_fn_error $? "cannot guess build type; you must specify one" "$LINENO" 5
We support building tcpdump with versions of libpcap other than the one with which it was released, and DLT_BLUETOOTH_HCI_H4_WITH_PHDR might be defined by pcap-bpf.h without pcap/bluetooth.h being present (as appears to be the case on Fedora 9, for example), so check whether <pcap/bluetooth.h> is usable. Update a comment - F9 appears to have a "/usr/include/pcap.h" if you install the libpcap headers. When adding -I flags when running a compiler-based test, add them to CPPFLAGS, not CFLAGS - the latter doesn't work right with AC_CHECK_HEADERS, as the "gcc -E" run doesn't have the -I flags added.
2008-09-26 05:45:50 +08:00
ac_cv_build=`$SHELL "$ac_aux_dir/config.sub" $ac_build_alias` ||
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
as_fn_error $? "$SHELL $ac_aux_dir/config.sub $ac_build_alias failed" "$LINENO" 5
Regenerate with autoconf 2.57.
2004-01-14 11:15:08 +08:00
fi
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
{ $as_echo "$as_me:${as_lineno-$LINENO}: result: $ac_cv_build" >&5
$as_echo "$ac_cv_build" >&6; }
We support building tcpdump with versions of libpcap other than the one with which it was released, and DLT_BLUETOOTH_HCI_H4_WITH_PHDR might be defined by pcap-bpf.h without pcap/bluetooth.h being present (as appears to be the case on Fedora 9, for example), so check whether <pcap/bluetooth.h> is usable. Update a comment - F9 appears to have a "/usr/include/pcap.h" if you install the libpcap headers. When adding -I flags when running a compiler-based test, add them to CPPFLAGS, not CFLAGS - the latter doesn't work right with AC_CHECK_HEADERS, as the "gcc -E" run doesn't have the -I flags added.
2008-09-26 05:45:50 +08:00
case $ac_cv_build in
*-*-*) ;;
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
*) as_fn_error $? "invalid value of canonical build" "$LINENO" 5;;
We support building tcpdump with versions of libpcap other than the one with which it was released, and DLT_BLUETOOTH_HCI_H4_WITH_PHDR might be defined by pcap-bpf.h without pcap/bluetooth.h being present (as appears to be the case on Fedora 9, for example), so check whether <pcap/bluetooth.h> is usable. Update a comment - F9 appears to have a "/usr/include/pcap.h" if you install the libpcap headers. When adding -I flags when running a compiler-based test, add them to CPPFLAGS, not CFLAGS - the latter doesn't work right with AC_CHECK_HEADERS, as the "gcc -E" run doesn't have the -I flags added.
2008-09-26 05:45:50 +08:00
esac
Regenerate with autoconf 2.57.
2004-01-14 11:15:08 +08:00
build=$ac_cv_build
We support building tcpdump with versions of libpcap other than the one with which it was released, and DLT_BLUETOOTH_HCI_H4_WITH_PHDR might be defined by pcap-bpf.h without pcap/bluetooth.h being present (as appears to be the case on Fedora 9, for example), so check whether <pcap/bluetooth.h> is usable. Update a comment - F9 appears to have a "/usr/include/pcap.h" if you install the libpcap headers. When adding -I flags when running a compiler-based test, add them to CPPFLAGS, not CFLAGS - the latter doesn't work right with AC_CHECK_HEADERS, as the "gcc -E" run doesn't have the -I flags added.
2008-09-26 05:45:50 +08:00
ac_save_IFS=$IFS; IFS='-'
set x $ac_cv_build
shift
build_cpu=$1
build_vendor=$2
shift; shift
# Remember, the first character of IFS is used to create $*,
# except with old shells:
build_os=$*
IFS=$ac_save_IFS
case $build_os in *\ *) build_os=`echo "$build_os" | sed 's/ /-/g'`;; esac
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
{ $as_echo "$as_me:${as_lineno-$LINENO}: checking host system type" >&5
$as_echo_n "checking host system type... " >&6; }
if ${ac_cv_host+:} false; then :
$as_echo_n "(cached) " >&6
Regenerate with autoconf 2.57.
2004-01-14 11:15:08 +08:00
else
We support building tcpdump with versions of libpcap other than the one with which it was released, and DLT_BLUETOOTH_HCI_H4_WITH_PHDR might be defined by pcap-bpf.h without pcap/bluetooth.h being present (as appears to be the case on Fedora 9, for example), so check whether <pcap/bluetooth.h> is usable. Update a comment - F9 appears to have a "/usr/include/pcap.h" if you install the libpcap headers. When adding -I flags when running a compiler-based test, add them to CPPFLAGS, not CFLAGS - the latter doesn't work right with AC_CHECK_HEADERS, as the "gcc -E" run doesn't have the -I flags added.
2008-09-26 05:45:50 +08:00
if test "x$host_alias" = x; then
ac_cv_host=$ac_cv_build
else
ac_cv_host=`$SHELL "$ac_aux_dir/config.sub" $host_alias` ||
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
as_fn_error $? "$SHELL $ac_aux_dir/config.sub $host_alias failed" "$LINENO" 5
We support building tcpdump with versions of libpcap other than the one with which it was released, and DLT_BLUETOOTH_HCI_H4_WITH_PHDR might be defined by pcap-bpf.h without pcap/bluetooth.h being present (as appears to be the case on Fedora 9, for example), so check whether <pcap/bluetooth.h> is usable. Update a comment - F9 appears to have a "/usr/include/pcap.h" if you install the libpcap headers. When adding -I flags when running a compiler-based test, add them to CPPFLAGS, not CFLAGS - the latter doesn't work right with AC_CHECK_HEADERS, as the "gcc -E" run doesn't have the -I flags added.
2008-09-26 05:45:50 +08:00
fi
Regenerate with autoconf 2.57.
2004-01-14 11:15:08 +08:00
fi
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
{ $as_echo "$as_me:${as_lineno-$LINENO}: result: $ac_cv_host" >&5
$as_echo "$ac_cv_host" >&6; }
We support building tcpdump with versions of libpcap other than the one with which it was released, and DLT_BLUETOOTH_HCI_H4_WITH_PHDR might be defined by pcap-bpf.h without pcap/bluetooth.h being present (as appears to be the case on Fedora 9, for example), so check whether <pcap/bluetooth.h> is usable. Update a comment - F9 appears to have a "/usr/include/pcap.h" if you install the libpcap headers. When adding -I flags when running a compiler-based test, add them to CPPFLAGS, not CFLAGS - the latter doesn't work right with AC_CHECK_HEADERS, as the "gcc -E" run doesn't have the -I flags added.
2008-09-26 05:45:50 +08:00
case $ac_cv_host in
*-*-*) ;;
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
*) as_fn_error $? "invalid value of canonical host" "$LINENO" 5;;
We support building tcpdump with versions of libpcap other than the one with which it was released, and DLT_BLUETOOTH_HCI_H4_WITH_PHDR might be defined by pcap-bpf.h without pcap/bluetooth.h being present (as appears to be the case on Fedora 9, for example), so check whether <pcap/bluetooth.h> is usable. Update a comment - F9 appears to have a "/usr/include/pcap.h" if you install the libpcap headers. When adding -I flags when running a compiler-based test, add them to CPPFLAGS, not CFLAGS - the latter doesn't work right with AC_CHECK_HEADERS, as the "gcc -E" run doesn't have the -I flags added.
2008-09-26 05:45:50 +08:00
esac
Regenerate with autoconf 2.57.
2004-01-14 11:15:08 +08:00
host=$ac_cv_host
We support building tcpdump with versions of libpcap other than the one with which it was released, and DLT_BLUETOOTH_HCI_H4_WITH_PHDR might be defined by pcap-bpf.h without pcap/bluetooth.h being present (as appears to be the case on Fedora 9, for example), so check whether <pcap/bluetooth.h> is usable. Update a comment - F9 appears to have a "/usr/include/pcap.h" if you install the libpcap headers. When adding -I flags when running a compiler-based test, add them to CPPFLAGS, not CFLAGS - the latter doesn't work right with AC_CHECK_HEADERS, as the "gcc -E" run doesn't have the -I flags added.
2008-09-26 05:45:50 +08:00
ac_save_IFS=$IFS; IFS='-'
set x $ac_cv_host
shift
host_cpu=$1
host_vendor=$2
shift; shift
# Remember, the first character of IFS is used to create $*,
# except with old shells:
host_os=$*
IFS=$ac_save_IFS
case $host_os in *\ *) host_os=`echo "$host_os" | sed 's/ /-/g'`;; esac
Regenerate with autoconf 2.57.
2004-01-14 11:15:08 +08:00
From Andrew Church <andrew@users.sourceforge.net>: when testing for "pcap_version", "pcap_debug", and "yydebug", don't add our own functions referring to those variables - GCC 3.4.1 optimizes the test code out before the link is done, as it's in a function that's not called.
2004-08-27 15:17:03 +08:00
Fix some problems that show up in autoconf 2.64 and later.
2010-01-03 07:29:06 +08:00
We support building tcpdump with versions of libpcap other than the one with which it was released, and DLT_BLUETOOTH_HCI_H4_WITH_PHDR might be defined by pcap-bpf.h without pcap/bluetooth.h being present (as appears to be the case on Fedora 9, for example), so check whether <pcap/bluetooth.h> is usable. Update a comment - F9 appears to have a "/usr/include/pcap.h" if you install the libpcap headers. When adding -I flags when running a compiler-based test, add them to CPPFLAGS, not CFLAGS - the latter doesn't work right with AC_CHECK_HEADERS, as the "gcc -E" run doesn't have the -I flags added.
2008-09-26 05:45:50 +08:00
# Check whether --with-gcc was given.
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
if test "${with_gcc+set}" = set; then :
We support building tcpdump with versions of libpcap other than the one with which it was released, and DLT_BLUETOOTH_HCI_H4_WITH_PHDR might be defined by pcap-bpf.h without pcap/bluetooth.h being present (as appears to be the case on Fedora 9, for example), so check whether <pcap/bluetooth.h> is usable. Update a comment - F9 appears to have a "/usr/include/pcap.h" if you install the libpcap headers. When adding -I flags when running a compiler-based test, add them to CPPFLAGS, not CFLAGS - the latter doesn't work right with AC_CHECK_HEADERS, as the "gcc -E" run doesn't have the -I flags added.
2008-09-26 05:45:50 +08:00
withval=$with_gcc;
fi
Regenerate with autoconf 2.57.
2004-01-14 11:15:08 +08:00
V_INCLS=""
if test "${srcdir}" != "." ; then
Expand srcdir in V_INCLS at configure time, not make time. That way, if we temporarily set CPPFLAGS to include V_INCLS, it'll work correctly.
2011-04-05 02:49:41 +08:00
V_INCLS="-I$srcdir"
Regenerate with autoconf 2.57.
2004-01-14 11:15:08 +08:00
fi
if test "${CFLAGS+set}" = set; then
LBL_CFLAGS="$CFLAGS"
fi
if test -z "$CC" ; then
case "$host_os" in
bsdi*)
# Extract the first word of "shlicc2", so it can be a program name with args.
set dummy shlicc2; ac_word=$2
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
{ $as_echo "$as_me:${as_lineno-$LINENO}: checking for $ac_word" >&5
$as_echo_n "checking for $ac_word... " >&6; }
if ${ac_cv_prog_SHLICC2+:} false; then :
$as_echo_n "(cached) " >&6
Regenerate with autoconf 2.57.
2004-01-14 11:15:08 +08:00
else
if test -n "$SHLICC2"; then
ac_cv_prog_SHLICC2="$SHLICC2" # Let the user override the test.
else
From Andrew Church <andrew@users.sourceforge.net>: when testing for "pcap_version", "pcap_debug", and "yydebug", don't add our own functions referring to those variables - GCC 3.4.1 optimizes the test code out before the link is done, as it's in a function that's not called.
2004-08-27 15:17:03 +08:00
as_save_IFS=$IFS; IFS=$PATH_SEPARATOR
for as_dir in $PATH
do
IFS=$as_save_IFS
test -z "$as_dir" && as_dir=.
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
for ac_exec_ext in '' $ac_executable_extensions; do
if as_fn_executable_p "$as_dir/$ac_word$ac_exec_ext"; then
From Andrew Church <andrew@users.sourceforge.net>: when testing for "pcap_version", "pcap_debug", and "yydebug", don't add our own functions referring to those variables - GCC 3.4.1 optimizes the test code out before the link is done, as it's in a function that's not called.
2004-08-27 15:17:03 +08:00
ac_cv_prog_SHLICC2="yes"
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
$as_echo "$as_me:${as_lineno-$LINENO}: found $as_dir/$ac_word$ac_exec_ext" >&5
From Andrew Church <andrew@users.sourceforge.net>: when testing for "pcap_version", "pcap_debug", and "yydebug", don't add our own functions referring to those variables - GCC 3.4.1 optimizes the test code out before the link is done, as it's in a function that's not called.
2004-08-27 15:17:03 +08:00
break 2
fi
done
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
done
We support building tcpdump with versions of libpcap other than the one with which it was released, and DLT_BLUETOOTH_HCI_H4_WITH_PHDR might be defined by pcap-bpf.h without pcap/bluetooth.h being present (as appears to be the case on Fedora 9, for example), so check whether <pcap/bluetooth.h> is usable. Update a comment - F9 appears to have a "/usr/include/pcap.h" if you install the libpcap headers. When adding -I flags when running a compiler-based test, add them to CPPFLAGS, not CFLAGS - the latter doesn't work right with AC_CHECK_HEADERS, as the "gcc -E" run doesn't have the -I flags added.
2008-09-26 05:45:50 +08:00
IFS=$as_save_IFS
Regenerate with autoconf 2.57.
2004-01-14 11:15:08 +08:00
test -z "$ac_cv_prog_SHLICC2" && ac_cv_prog_SHLICC2="no"
fi
fi
SHLICC2=$ac_cv_prog_SHLICC2
if test -n "$SHLICC2"; then
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
{ $as_echo "$as_me:${as_lineno-$LINENO}: result: $SHLICC2" >&5
$as_echo "$SHLICC2" >&6; }
Regenerate with autoconf 2.57.
2004-01-14 11:15:08 +08:00
else
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
{ $as_echo "$as_me:${as_lineno-$LINENO}: result: no" >&5
$as_echo "no" >&6; }
Regenerate with autoconf 2.57.
2004-01-14 11:15:08 +08:00
fi
We support building tcpdump with versions of libpcap other than the one with which it was released, and DLT_BLUETOOTH_HCI_H4_WITH_PHDR might be defined by pcap-bpf.h without pcap/bluetooth.h being present (as appears to be the case on Fedora 9, for example), so check whether <pcap/bluetooth.h> is usable. Update a comment - F9 appears to have a "/usr/include/pcap.h" if you install the libpcap headers. When adding -I flags when running a compiler-based test, add them to CPPFLAGS, not CFLAGS - the latter doesn't work right with AC_CHECK_HEADERS, as the "gcc -E" run doesn't have the -I flags added.
2008-09-26 05:45:50 +08:00
Regenerate with autoconf 2.57.
2004-01-14 11:15:08 +08:00
if test $SHLICC2 = yes ; then
CC=shlicc2
export CC
fi
;;
esac
fi
if test -z "$CC" -a "$with_gcc" = no ; then
CC=cc
export CC
fi
Fix some problems that show up in autoconf 2.64 and later.
2010-01-03 07:29:06 +08:00
ac_ext=c
Regenerate with autoconf 2.57.
2004-01-14 11:15:08 +08:00
ac_cpp='$CPP $CPPFLAGS'
ac_compile='$CC -c $CFLAGS $CPPFLAGS conftest.$ac_ext >&5'
ac_link='$CC -o conftest$ac_exeext $CFLAGS $CPPFLAGS $LDFLAGS conftest.$ac_ext $LIBS >&5'
ac_compiler_gnu=$ac_cv_c_compiler_gnu
if test -n "$ac_tool_prefix"; then
# Extract the first word of "${ac_tool_prefix}gcc", so it can be a program name with args.
set dummy ${ac_tool_prefix}gcc; ac_word=$2
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
{ $as_echo "$as_me:${as_lineno-$LINENO}: checking for $ac_word" >&5
$as_echo_n "checking for $ac_word... " >&6; }
if ${ac_cv_prog_CC+:} false; then :
$as_echo_n "(cached) " >&6
Regenerate with autoconf 2.57.
2004-01-14 11:15:08 +08:00
else
if test -n "$CC"; then
ac_cv_prog_CC="$CC" # Let the user override the test.
else
From Andrew Church <andrew@users.sourceforge.net>: when testing for "pcap_version", "pcap_debug", and "yydebug", don't add our own functions referring to those variables - GCC 3.4.1 optimizes the test code out before the link is done, as it's in a function that's not called.
2004-08-27 15:17:03 +08:00
as_save_IFS=$IFS; IFS=$PATH_SEPARATOR
for as_dir in $PATH
do
IFS=$as_save_IFS
test -z "$as_dir" && as_dir=.
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
for ac_exec_ext in '' $ac_executable_extensions; do
if as_fn_executable_p "$as_dir/$ac_word$ac_exec_ext"; then
From Andrew Church <andrew@users.sourceforge.net>: when testing for "pcap_version", "pcap_debug", and "yydebug", don't add our own functions referring to those variables - GCC 3.4.1 optimizes the test code out before the link is done, as it's in a function that's not called.
2004-08-27 15:17:03 +08:00
ac_cv_prog_CC="${ac_tool_prefix}gcc"
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
$as_echo "$as_me:${as_lineno-$LINENO}: found $as_dir/$ac_word$ac_exec_ext" >&5
From Andrew Church <andrew@users.sourceforge.net>: when testing for "pcap_version", "pcap_debug", and "yydebug", don't add our own functions referring to those variables - GCC 3.4.1 optimizes the test code out before the link is done, as it's in a function that's not called.
2004-08-27 15:17:03 +08:00
break 2
fi
done
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
done
We support building tcpdump with versions of libpcap other than the one with which it was released, and DLT_BLUETOOTH_HCI_H4_WITH_PHDR might be defined by pcap-bpf.h without pcap/bluetooth.h being present (as appears to be the case on Fedora 9, for example), so check whether <pcap/bluetooth.h> is usable. Update a comment - F9 appears to have a "/usr/include/pcap.h" if you install the libpcap headers. When adding -I flags when running a compiler-based test, add them to CPPFLAGS, not CFLAGS - the latter doesn't work right with AC_CHECK_HEADERS, as the "gcc -E" run doesn't have the -I flags added.
2008-09-26 05:45:50 +08:00
IFS=$as_save_IFS
Regenerate with autoconf 2.57.
2004-01-14 11:15:08 +08:00
fi
fi
CC=$ac_cv_prog_CC
if test -n "$CC"; then
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
{ $as_echo "$as_me:${as_lineno-$LINENO}: result: $CC" >&5
$as_echo "$CC" >&6; }
Regenerate with autoconf 2.57.
2004-01-14 11:15:08 +08:00
else
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
{ $as_echo "$as_me:${as_lineno-$LINENO}: result: no" >&5
$as_echo "no" >&6; }
Regenerate with autoconf 2.57.
2004-01-14 11:15:08 +08:00
fi
We support building tcpdump with versions of libpcap other than the one with which it was released, and DLT_BLUETOOTH_HCI_H4_WITH_PHDR might be defined by pcap-bpf.h without pcap/bluetooth.h being present (as appears to be the case on Fedora 9, for example), so check whether <pcap/bluetooth.h> is usable. Update a comment - F9 appears to have a "/usr/include/pcap.h" if you install the libpcap headers. When adding -I flags when running a compiler-based test, add them to CPPFLAGS, not CFLAGS - the latter doesn't work right with AC_CHECK_HEADERS, as the "gcc -E" run doesn't have the -I flags added.
2008-09-26 05:45:50 +08:00
Regenerate with autoconf 2.57.
2004-01-14 11:15:08 +08:00
fi
if test -z "$ac_cv_prog_CC"; then
ac_ct_CC=$CC
# Extract the first word of "gcc", so it can be a program name with args.
set dummy gcc; ac_word=$2
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
{ $as_echo "$as_me:${as_lineno-$LINENO}: checking for $ac_word" >&5
$as_echo_n "checking for $ac_word... " >&6; }
if ${ac_cv_prog_ac_ct_CC+:} false; then :
$as_echo_n "(cached) " >&6
Regenerate with autoconf 2.57.
2004-01-14 11:15:08 +08:00
else
if test -n "$ac_ct_CC"; then
ac_cv_prog_ac_ct_CC="$ac_ct_CC" # Let the user override the test.
else
From Andrew Church <andrew@users.sourceforge.net>: when testing for "pcap_version", "pcap_debug", and "yydebug", don't add our own functions referring to those variables - GCC 3.4.1 optimizes the test code out before the link is done, as it's in a function that's not called.
2004-08-27 15:17:03 +08:00
as_save_IFS=$IFS; IFS=$PATH_SEPARATOR
for as_dir in $PATH
do
IFS=$as_save_IFS
test -z "$as_dir" && as_dir=.
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
for ac_exec_ext in '' $ac_executable_extensions; do
if as_fn_executable_p "$as_dir/$ac_word$ac_exec_ext"; then
From Andrew Church <andrew@users.sourceforge.net>: when testing for "pcap_version", "pcap_debug", and "yydebug", don't add our own functions referring to those variables - GCC 3.4.1 optimizes the test code out before the link is done, as it's in a function that's not called.
2004-08-27 15:17:03 +08:00
ac_cv_prog_ac_ct_CC="gcc"
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
$as_echo "$as_me:${as_lineno-$LINENO}: found $as_dir/$ac_word$ac_exec_ext" >&5
From Andrew Church <andrew@users.sourceforge.net>: when testing for "pcap_version", "pcap_debug", and "yydebug", don't add our own functions referring to those variables - GCC 3.4.1 optimizes the test code out before the link is done, as it's in a function that's not called.
2004-08-27 15:17:03 +08:00
break 2
fi
done
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
done
We support building tcpdump with versions of libpcap other than the one with which it was released, and DLT_BLUETOOTH_HCI_H4_WITH_PHDR might be defined by pcap-bpf.h without pcap/bluetooth.h being present (as appears to be the case on Fedora 9, for example), so check whether <pcap/bluetooth.h> is usable. Update a comment - F9 appears to have a "/usr/include/pcap.h" if you install the libpcap headers. When adding -I flags when running a compiler-based test, add them to CPPFLAGS, not CFLAGS - the latter doesn't work right with AC_CHECK_HEADERS, as the "gcc -E" run doesn't have the -I flags added.
2008-09-26 05:45:50 +08:00
IFS=$as_save_IFS
Regenerate with autoconf 2.57.
2004-01-14 11:15:08 +08:00
fi
fi
ac_ct_CC=$ac_cv_prog_ac_ct_CC
if test -n "$ac_ct_CC"; then
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
{ $as_echo "$as_me:${as_lineno-$LINENO}: result: $ac_ct_CC" >&5
$as_echo "$ac_ct_CC" >&6; }
Regenerate with autoconf 2.57.
2004-01-14 11:15:08 +08:00
else
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
{ $as_echo "$as_me:${as_lineno-$LINENO}: result: no" >&5
$as_echo "no" >&6; }
Regenerate with autoconf 2.57.
2004-01-14 11:15:08 +08:00
fi
We support building tcpdump with versions of libpcap other than the one with which it was released, and DLT_BLUETOOTH_HCI_H4_WITH_PHDR might be defined by pcap-bpf.h without pcap/bluetooth.h being present (as appears to be the case on Fedora 9, for example), so check whether <pcap/bluetooth.h> is usable. Update a comment - F9 appears to have a "/usr/include/pcap.h" if you install the libpcap headers. When adding -I flags when running a compiler-based test, add them to CPPFLAGS, not CFLAGS - the latter doesn't work right with AC_CHECK_HEADERS, as the "gcc -E" run doesn't have the -I flags added.
2008-09-26 05:45:50 +08:00
if test "x$ac_ct_CC" = x; then
CC=""
else
case $cross_compiling:$ac_tool_warned in
yes:)
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
{ $as_echo "$as_me:${as_lineno-$LINENO}: WARNING: using cross tools not prefixed with host triplet" >&5
$as_echo "$as_me: WARNING: using cross tools not prefixed with host triplet" >&2;}
We support building tcpdump with versions of libpcap other than the one with which it was released, and DLT_BLUETOOTH_HCI_H4_WITH_PHDR might be defined by pcap-bpf.h without pcap/bluetooth.h being present (as appears to be the case on Fedora 9, for example), so check whether <pcap/bluetooth.h> is usable. Update a comment - F9 appears to have a "/usr/include/pcap.h" if you install the libpcap headers. When adding -I flags when running a compiler-based test, add them to CPPFLAGS, not CFLAGS - the latter doesn't work right with AC_CHECK_HEADERS, as the "gcc -E" run doesn't have the -I flags added.
2008-09-26 05:45:50 +08:00
ac_tool_warned=yes ;;
esac
CC=$ac_ct_CC
fi
Regenerate with autoconf 2.57.
2004-01-14 11:15:08 +08:00
else
CC="$ac_cv_prog_CC"
fi
if test -z "$CC"; then
We support building tcpdump with versions of libpcap other than the one with which it was released, and DLT_BLUETOOTH_HCI_H4_WITH_PHDR might be defined by pcap-bpf.h without pcap/bluetooth.h being present (as appears to be the case on Fedora 9, for example), so check whether <pcap/bluetooth.h> is usable. Update a comment - F9 appears to have a "/usr/include/pcap.h" if you install the libpcap headers. When adding -I flags when running a compiler-based test, add them to CPPFLAGS, not CFLAGS - the latter doesn't work right with AC_CHECK_HEADERS, as the "gcc -E" run doesn't have the -I flags added.
2008-09-26 05:45:50 +08:00
if test -n "$ac_tool_prefix"; then
# Extract the first word of "${ac_tool_prefix}cc", so it can be a program name with args.
Regenerate with autoconf 2.57.
2004-01-14 11:15:08 +08:00
set dummy ${ac_tool_prefix}cc; ac_word=$2
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
{ $as_echo "$as_me:${as_lineno-$LINENO}: checking for $ac_word" >&5
$as_echo_n "checking for $ac_word... " >&6; }
if ${ac_cv_prog_CC+:} false; then :
$as_echo_n "(cached) " >&6
Regenerate with autoconf 2.57.
2004-01-14 11:15:08 +08:00
else
if test -n "$CC"; then
ac_cv_prog_CC="$CC" # Let the user override the test.
else
From Andrew Church <andrew@users.sourceforge.net>: when testing for "pcap_version", "pcap_debug", and "yydebug", don't add our own functions referring to those variables - GCC 3.4.1 optimizes the test code out before the link is done, as it's in a function that's not called.
2004-08-27 15:17:03 +08:00
as_save_IFS=$IFS; IFS=$PATH_SEPARATOR
for as_dir in $PATH
do
IFS=$as_save_IFS
test -z "$as_dir" && as_dir=.
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
for ac_exec_ext in '' $ac_executable_extensions; do
if as_fn_executable_p "$as_dir/$ac_word$ac_exec_ext"; then
From Andrew Church <andrew@users.sourceforge.net>: when testing for "pcap_version", "pcap_debug", and "yydebug", don't add our own functions referring to those variables - GCC 3.4.1 optimizes the test code out before the link is done, as it's in a function that's not called.
2004-08-27 15:17:03 +08:00
ac_cv_prog_CC="${ac_tool_prefix}cc"
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
$as_echo "$as_me:${as_lineno-$LINENO}: found $as_dir/$ac_word$ac_exec_ext" >&5
From Andrew Church <andrew@users.sourceforge.net>: when testing for "pcap_version", "pcap_debug", and "yydebug", don't add our own functions referring to those variables - GCC 3.4.1 optimizes the test code out before the link is done, as it's in a function that's not called.
2004-08-27 15:17:03 +08:00
break 2
fi
done
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
done
We support building tcpdump with versions of libpcap other than the one with which it was released, and DLT_BLUETOOTH_HCI_H4_WITH_PHDR might be defined by pcap-bpf.h without pcap/bluetooth.h being present (as appears to be the case on Fedora 9, for example), so check whether <pcap/bluetooth.h> is usable. Update a comment - F9 appears to have a "/usr/include/pcap.h" if you install the libpcap headers. When adding -I flags when running a compiler-based test, add them to CPPFLAGS, not CFLAGS - the latter doesn't work right with AC_CHECK_HEADERS, as the "gcc -E" run doesn't have the -I flags added.
2008-09-26 05:45:50 +08:00
IFS=$as_save_IFS
Regenerate with autoconf 2.57.
2004-01-14 11:15:08 +08:00
fi
fi
CC=$ac_cv_prog_CC
if test -n "$CC"; then
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
{ $as_echo "$as_me:${as_lineno-$LINENO}: result: $CC" >&5
$as_echo "$CC" >&6; }
Run ranlib on libnetdissect.a if necessary. Remove it before building it, so we discard any stuff already in the archive.
2008-02-05 04:42:09 +08:00
else
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
{ $as_echo "$as_me:${as_lineno-$LINENO}: result: no" >&5
$as_echo "no" >&6; }
Run ranlib on libnetdissect.a if necessary. Remove it before building it, so we discard any stuff already in the archive.
2008-02-05 04:42:09 +08:00
fi
We support building tcpdump with versions of libpcap other than the one with which it was released, and DLT_BLUETOOTH_HCI_H4_WITH_PHDR might be defined by pcap-bpf.h without pcap/bluetooth.h being present (as appears to be the case on Fedora 9, for example), so check whether <pcap/bluetooth.h> is usable. Update a comment - F9 appears to have a "/usr/include/pcap.h" if you install the libpcap headers. When adding -I flags when running a compiler-based test, add them to CPPFLAGS, not CFLAGS - the latter doesn't work right with AC_CHECK_HEADERS, as the "gcc -E" run doesn't have the -I flags added.
2008-09-26 05:45:50 +08:00
fi
Regenerate with autoconf 2.57.
2004-01-14 11:15:08 +08:00
fi
if test -z "$CC"; then
# Extract the first word of "cc", so it can be a program name with args.
set dummy cc; ac_word=$2
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
{ $as_echo "$as_me:${as_lineno-$LINENO}: checking for $ac_word" >&5
$as_echo_n "checking for $ac_word... " >&6; }
if ${ac_cv_prog_CC+:} false; then :
$as_echo_n "(cached) " >&6
Regenerate with autoconf 2.57.
2004-01-14 11:15:08 +08:00
else
if test -n "$CC"; then
ac_cv_prog_CC="$CC" # Let the user override the test.
else
ac_prog_rejected=no
From Andrew Church <andrew@users.sourceforge.net>: when testing for "pcap_version", "pcap_debug", and "yydebug", don't add our own functions referring to those variables - GCC 3.4.1 optimizes the test code out before the link is done, as it's in a function that's not called.
2004-08-27 15:17:03 +08:00
as_save_IFS=$IFS; IFS=$PATH_SEPARATOR
for as_dir in $PATH
do
IFS=$as_save_IFS
test -z "$as_dir" && as_dir=.
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
for ac_exec_ext in '' $ac_executable_extensions; do
if as_fn_executable_p "$as_dir/$ac_word$ac_exec_ext"; then
From Andrew Church <andrew@users.sourceforge.net>: when testing for "pcap_version", "pcap_debug", and "yydebug", don't add our own functions referring to those variables - GCC 3.4.1 optimizes the test code out before the link is done, as it's in a function that's not called.
2004-08-27 15:17:03 +08:00
if test "$as_dir/$ac_word$ac_exec_ext" = "/usr/ucb/cc"; then
ac_prog_rejected=yes
continue
fi
ac_cv_prog_CC="cc"
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
$as_echo "$as_me:${as_lineno-$LINENO}: found $as_dir/$ac_word$ac_exec_ext" >&5
From Andrew Church <andrew@users.sourceforge.net>: when testing for "pcap_version", "pcap_debug", and "yydebug", don't add our own functions referring to those variables - GCC 3.4.1 optimizes the test code out before the link is done, as it's in a function that's not called.
2004-08-27 15:17:03 +08:00
break 2
fi
done
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
done
We support building tcpdump with versions of libpcap other than the one with which it was released, and DLT_BLUETOOTH_HCI_H4_WITH_PHDR might be defined by pcap-bpf.h without pcap/bluetooth.h being present (as appears to be the case on Fedora 9, for example), so check whether <pcap/bluetooth.h> is usable. Update a comment - F9 appears to have a "/usr/include/pcap.h" if you install the libpcap headers. When adding -I flags when running a compiler-based test, add them to CPPFLAGS, not CFLAGS - the latter doesn't work right with AC_CHECK_HEADERS, as the "gcc -E" run doesn't have the -I flags added.
2008-09-26 05:45:50 +08:00
IFS=$as_save_IFS
Regenerate with autoconf 2.57.
2004-01-14 11:15:08 +08:00
Initial revision
1999-10-08 07:47:09 +08:00
if test $ac_prog_rejected = yes; then
# We found a bogon in the path, so make sure we never use it.
set dummy $ac_cv_prog_CC
shift
Regenerate with autoconf 2.57.
2004-01-14 11:15:08 +08:00
if test $# != 0; then
Initial revision
1999-10-08 07:47:09 +08:00
# We chose a different compiler from the bogus one.
# However, it has the same basename, so the bogon will be chosen
# first if we set CC to just the basename; use the full file name.
shift
From Andrew Church <andrew@users.sourceforge.net>: when testing for "pcap_version", "pcap_debug", and "yydebug", don't add our own functions referring to those variables - GCC 3.4.1 optimizes the test code out before the link is done, as it's in a function that's not called.
2004-08-27 15:17:03 +08:00
ac_cv_prog_CC="$as_dir/$ac_word${1+' '}$@"
Initial revision
1999-10-08 07:47:09 +08:00
fi
fi
fi
fi
Regenerate with autoconf 2.57.
2004-01-14 11:15:08 +08:00
CC=$ac_cv_prog_CC
Initial revision
1999-10-08 07:47:09 +08:00
if test -n "$CC"; then
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
{ $as_echo "$as_me:${as_lineno-$LINENO}: result: $CC" >&5
$as_echo "$CC" >&6; }
Initial revision
1999-10-08 07:47:09 +08:00
else
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
{ $as_echo "$as_me:${as_lineno-$LINENO}: result: no" >&5
$as_echo "no" >&6; }
Initial revision
1999-10-08 07:47:09 +08:00
fi
We support building tcpdump with versions of libpcap other than the one with which it was released, and DLT_BLUETOOTH_HCI_H4_WITH_PHDR might be defined by pcap-bpf.h without pcap/bluetooth.h being present (as appears to be the case on Fedora 9, for example), so check whether <pcap/bluetooth.h> is usable. Update a comment - F9 appears to have a "/usr/include/pcap.h" if you install the libpcap headers. When adding -I flags when running a compiler-based test, add them to CPPFLAGS, not CFLAGS - the latter doesn't work right with AC_CHECK_HEADERS, as the "gcc -E" run doesn't have the -I flags added.
2008-09-26 05:45:50 +08:00
Regenerate with autoconf 2.57.
2004-01-14 11:15:08 +08:00
fi
if test -z "$CC"; then
if test -n "$ac_tool_prefix"; then
We support building tcpdump with versions of libpcap other than the one with which it was released, and DLT_BLUETOOTH_HCI_H4_WITH_PHDR might be defined by pcap-bpf.h without pcap/bluetooth.h being present (as appears to be the case on Fedora 9, for example), so check whether <pcap/bluetooth.h> is usable. Update a comment - F9 appears to have a "/usr/include/pcap.h" if you install the libpcap headers. When adding -I flags when running a compiler-based test, add them to CPPFLAGS, not CFLAGS - the latter doesn't work right with AC_CHECK_HEADERS, as the "gcc -E" run doesn't have the -I flags added.
2008-09-26 05:45:50 +08:00
for ac_prog in cl.exe
Regenerate with autoconf 2.57.
2004-01-14 11:15:08 +08:00
do
# Extract the first word of "$ac_tool_prefix$ac_prog", so it can be a program name with args.
set dummy $ac_tool_prefix$ac_prog; ac_word=$2
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
{ $as_echo "$as_me:${as_lineno-$LINENO}: checking for $ac_word" >&5
$as_echo_n "checking for $ac_word... " >&6; }
if ${ac_cv_prog_CC+:} false; then :
$as_echo_n "(cached) " >&6
Bring in KAME IPv6 tcpdump. replaces esp/ah/isakmp decoder. Hope I did not break anything. Portability on IPv4-only node needs checking, I'll do this very soon. (sorry for rather jumbo commit) XXx what is _FAVOR_BSD?
1999-10-30 13:11:06 +08:00
else
if test -n "$CC"; then
ac_cv_prog_CC="$CC" # Let the user override the test.
else
From Andrew Church <andrew@users.sourceforge.net>: when testing for "pcap_version", "pcap_debug", and "yydebug", don't add our own functions referring to those variables - GCC 3.4.1 optimizes the test code out before the link is done, as it's in a function that's not called.
2004-08-27 15:17:03 +08:00
as_save_IFS=$IFS; IFS=$PATH_SEPARATOR
for as_dir in $PATH
do
IFS=$as_save_IFS
test -z "$as_dir" && as_dir=.
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
for ac_exec_ext in '' $ac_executable_extensions; do
if as_fn_executable_p "$as_dir/$ac_word$ac_exec_ext"; then
From Andrew Church <andrew@users.sourceforge.net>: when testing for "pcap_version", "pcap_debug", and "yydebug", don't add our own functions referring to those variables - GCC 3.4.1 optimizes the test code out before the link is done, as it's in a function that's not called.
2004-08-27 15:17:03 +08:00
ac_cv_prog_CC="$ac_tool_prefix$ac_prog"
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
$as_echo "$as_me:${as_lineno-$LINENO}: found $as_dir/$ac_word$ac_exec_ext" >&5
From Andrew Church <andrew@users.sourceforge.net>: when testing for "pcap_version", "pcap_debug", and "yydebug", don't add our own functions referring to those variables - GCC 3.4.1 optimizes the test code out before the link is done, as it's in a function that's not called.
2004-08-27 15:17:03 +08:00
break 2
fi
done
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
done
We support building tcpdump with versions of libpcap other than the one with which it was released, and DLT_BLUETOOTH_HCI_H4_WITH_PHDR might be defined by pcap-bpf.h without pcap/bluetooth.h being present (as appears to be the case on Fedora 9, for example), so check whether <pcap/bluetooth.h> is usable. Update a comment - F9 appears to have a "/usr/include/pcap.h" if you install the libpcap headers. When adding -I flags when running a compiler-based test, add them to CPPFLAGS, not CFLAGS - the latter doesn't work right with AC_CHECK_HEADERS, as the "gcc -E" run doesn't have the -I flags added.
2008-09-26 05:45:50 +08:00
IFS=$as_save_IFS
Regenerate with autoconf 2.57.
2004-01-14 11:15:08 +08:00
Bring in KAME IPv6 tcpdump. replaces esp/ah/isakmp decoder. Hope I did not break anything. Portability on IPv4-only node needs checking, I'll do this very soon. (sorry for rather jumbo commit) XXx what is _FAVOR_BSD?
1999-10-30 13:11:06 +08:00
fi
fi
Regenerate with autoconf 2.57.
2004-01-14 11:15:08 +08:00
CC=$ac_cv_prog_CC
Bring in KAME IPv6 tcpdump. replaces esp/ah/isakmp decoder. Hope I did not break anything. Portability on IPv4-only node needs checking, I'll do this very soon. (sorry for rather jumbo commit) XXx what is _FAVOR_BSD?
1999-10-30 13:11:06 +08:00
if test -n "$CC"; then
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
{ $as_echo "$as_me:${as_lineno-$LINENO}: result: $CC" >&5
$as_echo "$CC" >&6; }
Bring in KAME IPv6 tcpdump. replaces esp/ah/isakmp decoder. Hope I did not break anything. Portability on IPv4-only node needs checking, I'll do this very soon. (sorry for rather jumbo commit) XXx what is _FAVOR_BSD?
1999-10-30 13:11:06 +08:00
else
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
{ $as_echo "$as_me:${as_lineno-$LINENO}: result: no" >&5
$as_echo "no" >&6; }
Bring in KAME IPv6 tcpdump. replaces esp/ah/isakmp decoder. Hope I did not break anything. Portability on IPv4-only node needs checking, I'll do this very soon. (sorry for rather jumbo commit) XXx what is _FAVOR_BSD?
1999-10-30 13:11:06 +08:00
fi
Regenerate with autoconf 2.57.
2004-01-14 11:15:08 +08:00
We support building tcpdump with versions of libpcap other than the one with which it was released, and DLT_BLUETOOTH_HCI_H4_WITH_PHDR might be defined by pcap-bpf.h without pcap/bluetooth.h being present (as appears to be the case on Fedora 9, for example), so check whether <pcap/bluetooth.h> is usable. Update a comment - F9 appears to have a "/usr/include/pcap.h" if you install the libpcap headers. When adding -I flags when running a compiler-based test, add them to CPPFLAGS, not CFLAGS - the latter doesn't work right with AC_CHECK_HEADERS, as the "gcc -E" run doesn't have the -I flags added.
2008-09-26 05:45:50 +08:00
Regenerate with autoconf 2.57.
2004-01-14 11:15:08 +08:00
test -n "$CC" && break
done
Initial revision
1999-10-08 07:47:09 +08:00
fi
Regenerate with autoconf 2.57.
2004-01-14 11:15:08 +08:00
if test -z "$CC"; then
ac_ct_CC=$CC
We support building tcpdump with versions of libpcap other than the one with which it was released, and DLT_BLUETOOTH_HCI_H4_WITH_PHDR might be defined by pcap-bpf.h without pcap/bluetooth.h being present (as appears to be the case on Fedora 9, for example), so check whether <pcap/bluetooth.h> is usable. Update a comment - F9 appears to have a "/usr/include/pcap.h" if you install the libpcap headers. When adding -I flags when running a compiler-based test, add them to CPPFLAGS, not CFLAGS - the latter doesn't work right with AC_CHECK_HEADERS, as the "gcc -E" run doesn't have the -I flags added.
2008-09-26 05:45:50 +08:00
for ac_prog in cl.exe
Regenerate with autoconf 2.57.
2004-01-14 11:15:08 +08:00
do
# Extract the first word of "$ac_prog", so it can be a program name with args.
set dummy $ac_prog; ac_word=$2
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
{ $as_echo "$as_me:${as_lineno-$LINENO}: checking for $ac_word" >&5
$as_echo_n "checking for $ac_word... " >&6; }
if ${ac_cv_prog_ac_ct_CC+:} false; then :
$as_echo_n "(cached) " >&6
Regenerate with autoconf 2.57.
2004-01-14 11:15:08 +08:00
else
if test -n "$ac_ct_CC"; then
ac_cv_prog_ac_ct_CC="$ac_ct_CC" # Let the user override the test.
else
From Andrew Church <andrew@users.sourceforge.net>: when testing for "pcap_version", "pcap_debug", and "yydebug", don't add our own functions referring to those variables - GCC 3.4.1 optimizes the test code out before the link is done, as it's in a function that's not called.
2004-08-27 15:17:03 +08:00
as_save_IFS=$IFS; IFS=$PATH_SEPARATOR
for as_dir in $PATH
do
IFS=$as_save_IFS
test -z "$as_dir" && as_dir=.
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
for ac_exec_ext in '' $ac_executable_extensions; do
if as_fn_executable_p "$as_dir/$ac_word$ac_exec_ext"; then
From Andrew Church <andrew@users.sourceforge.net>: when testing for "pcap_version", "pcap_debug", and "yydebug", don't add our own functions referring to those variables - GCC 3.4.1 optimizes the test code out before the link is done, as it's in a function that's not called.
2004-08-27 15:17:03 +08:00
ac_cv_prog_ac_ct_CC="$ac_prog"
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
$as_echo "$as_me:${as_lineno-$LINENO}: found $as_dir/$ac_word$ac_exec_ext" >&5
From Andrew Church <andrew@users.sourceforge.net>: when testing for "pcap_version", "pcap_debug", and "yydebug", don't add our own functions referring to those variables - GCC 3.4.1 optimizes the test code out before the link is done, as it's in a function that's not called.
2004-08-27 15:17:03 +08:00
break 2
fi
done
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
done
We support building tcpdump with versions of libpcap other than the one with which it was released, and DLT_BLUETOOTH_HCI_H4_WITH_PHDR might be defined by pcap-bpf.h without pcap/bluetooth.h being present (as appears to be the case on Fedora 9, for example), so check whether <pcap/bluetooth.h> is usable. Update a comment - F9 appears to have a "/usr/include/pcap.h" if you install the libpcap headers. When adding -I flags when running a compiler-based test, add them to CPPFLAGS, not CFLAGS - the latter doesn't work right with AC_CHECK_HEADERS, as the "gcc -E" run doesn't have the -I flags added.
2008-09-26 05:45:50 +08:00
IFS=$as_save_IFS
Initial revision
1999-10-08 07:47:09 +08:00
Regenerate with autoconf 2.57.
2004-01-14 11:15:08 +08:00
fi
fi
ac_ct_CC=$ac_cv_prog_ac_ct_CC
if test -n "$ac_ct_CC"; then
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
{ $as_echo "$as_me:${as_lineno-$LINENO}: result: $ac_ct_CC" >&5
$as_echo "$ac_ct_CC" >&6; }
Regenerate with autoconf 2.57.
2004-01-14 11:15:08 +08:00
else
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
{ $as_echo "$as_me:${as_lineno-$LINENO}: result: no" >&5
$as_echo "no" >&6; }
Regenerate with autoconf 2.57.
2004-01-14 11:15:08 +08:00
fi
Initial revision
1999-10-08 07:47:09 +08:00
We support building tcpdump with versions of libpcap other than the one with which it was released, and DLT_BLUETOOTH_HCI_H4_WITH_PHDR might be defined by pcap-bpf.h without pcap/bluetooth.h being present (as appears to be the case on Fedora 9, for example), so check whether <pcap/bluetooth.h> is usable. Update a comment - F9 appears to have a "/usr/include/pcap.h" if you install the libpcap headers. When adding -I flags when running a compiler-based test, add them to CPPFLAGS, not CFLAGS - the latter doesn't work right with AC_CHECK_HEADERS, as the "gcc -E" run doesn't have the -I flags added.
2008-09-26 05:45:50 +08:00
Regenerate with autoconf 2.57.
2004-01-14 11:15:08 +08:00
test -n "$ac_ct_CC" && break
done
Initial revision
1999-10-08 07:47:09 +08:00
We support building tcpdump with versions of libpcap other than the one with which it was released, and DLT_BLUETOOTH_HCI_H4_WITH_PHDR might be defined by pcap-bpf.h without pcap/bluetooth.h being present (as appears to be the case on Fedora 9, for example), so check whether <pcap/bluetooth.h> is usable. Update a comment - F9 appears to have a "/usr/include/pcap.h" if you install the libpcap headers. When adding -I flags when running a compiler-based test, add them to CPPFLAGS, not CFLAGS - the latter doesn't work right with AC_CHECK_HEADERS, as the "gcc -E" run doesn't have the -I flags added.
2008-09-26 05:45:50 +08:00
if test "x$ac_ct_CC" = x; then
CC=""
else
case $cross_compiling:$ac_tool_warned in
yes:)
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
{ $as_echo "$as_me:${as_lineno-$LINENO}: WARNING: using cross tools not prefixed with host triplet" >&5
$as_echo "$as_me: WARNING: using cross tools not prefixed with host triplet" >&2;}
We support building tcpdump with versions of libpcap other than the one with which it was released, and DLT_BLUETOOTH_HCI_H4_WITH_PHDR might be defined by pcap-bpf.h without pcap/bluetooth.h being present (as appears to be the case on Fedora 9, for example), so check whether <pcap/bluetooth.h> is usable. Update a comment - F9 appears to have a "/usr/include/pcap.h" if you install the libpcap headers. When adding -I flags when running a compiler-based test, add them to CPPFLAGS, not CFLAGS - the latter doesn't work right with AC_CHECK_HEADERS, as the "gcc -E" run doesn't have the -I flags added.
2008-09-26 05:45:50 +08:00
ac_tool_warned=yes ;;
esac
CC=$ac_ct_CC
fi
Regenerate with autoconf 2.57.
2004-01-14 11:15:08 +08:00
fi
fi
From Andrew Church <andrew@users.sourceforge.net>: when testing for "pcap_version", "pcap_debug", and "yydebug", don't add our own functions referring to those variables - GCC 3.4.1 optimizes the test code out before the link is done, as it's in a function that's not called.
2004-08-27 15:17:03 +08:00
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
test -z "$CC" && { { $as_echo "$as_me:${as_lineno-$LINENO}: error: in \`$ac_pwd':" >&5
$as_echo "$as_me: error: in \`$ac_pwd':" >&2;}
as_fn_error $? "no acceptable C compiler found in \$PATH
See \`config.log' for more details" "$LINENO" 5; }
Regenerate with autoconf 2.57.
2004-01-14 11:15:08 +08:00
# Provide some information about the compiler.
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
$as_echo "$as_me:${as_lineno-$LINENO}: checking for C compiler version" >&5
set X $ac_compile
ac_compiler=$2
for ac_option in --version -v -V -qversion; do
{ { ac_try="$ac_compiler $ac_option >&5"
Check for extra networking libraries before checking for IPv6. On some platforms, such as SunOS 5.x, building the "do we have IPv6 support?" test program requires the extra networking libraries, so we need to know what extra networking libraries are required before doing that test.
2013-04-07 04:03:58 +08:00
case "(($ac_try" in
*\"* | *\`* | *\\*) ac_try_echo=\$ac_try;;
*) ac_try_echo=$ac_try;;
esac
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
eval ac_try_echo="\"\$as_me:${as_lineno-$LINENO}: $ac_try_echo\""
$as_echo "$ac_try_echo"; } >&5
(eval "$ac_compiler $ac_option >&5") 2>conftest.err
Check for extra networking libraries before checking for IPv6. On some platforms, such as SunOS 5.x, building the "do we have IPv6 support?" test program requires the extra networking libraries, so we need to know what extra networking libraries are required before doing that test.
2013-04-07 04:03:58 +08:00
ac_status=$?
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
if test -s conftest.err; then
sed '10a\
... rest of stderr output deleted ...
10q' conftest.err >conftest.er1
cat conftest.er1 >&5
fi
rm -f conftest.er1 conftest.err
$as_echo "$as_me:${as_lineno-$LINENO}: \$? = $ac_status" >&5
test $ac_status = 0; }
done
Regenerate with autoconf 2.57.
2004-01-14 11:15:08 +08:00
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
cat confdefs.h - <<_ACEOF >conftest.$ac_ext
From Andrew Church <andrew@users.sourceforge.net>: when testing for "pcap_version", "pcap_debug", and "yydebug", don't add our own functions referring to those variables - GCC 3.4.1 optimizes the test code out before the link is done, as it's in a function that's not called.
2004-08-27 15:17:03 +08:00
/* end confdefs.h. */
Bring in KAME IPv6 tcpdump. replaces esp/ah/isakmp decoder. Hope I did not break anything. Portability on IPv4-only node needs checking, I'll do this very soon. (sorry for rather jumbo commit) XXx what is _FAVOR_BSD?
1999-10-30 13:11:06 +08:00
Regenerate with autoconf 2.57.
2004-01-14 11:15:08 +08:00
int
main ()
{
Bring in KAME IPv6 tcpdump. replaces esp/ah/isakmp decoder. Hope I did not break anything. Portability on IPv4-only node needs checking, I'll do this very soon. (sorry for rather jumbo commit) XXx what is _FAVOR_BSD?
1999-10-30 13:11:06 +08:00
Regenerate with autoconf 2.57.
2004-01-14 11:15:08 +08:00
;
return 0;
}
_ACEOF
ac_clean_files_save=$ac_clean_files
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
ac_clean_files="$ac_clean_files a.out a.out.dSYM a.exe b.out"
Regenerate with autoconf 2.57.
2004-01-14 11:15:08 +08:00
# Try to create an executable without -o first, disregard a.out.
# It will help us diagnose broken compilers, and finding out an intuition
# of exeext.
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
{ $as_echo "$as_me:${as_lineno-$LINENO}: checking whether the C compiler works" >&5
$as_echo_n "checking whether the C compiler works... " >&6; }
ac_link_default=`$as_echo "$ac_link" | sed 's/ -o *conftest[^ ]*//'`
# The possible output files:
ac_files="a.out conftest.exe conftest a.exe a_out.exe b.out conftest.*"
We support building tcpdump with versions of libpcap other than the one with which it was released, and DLT_BLUETOOTH_HCI_H4_WITH_PHDR might be defined by pcap-bpf.h without pcap/bluetooth.h being present (as appears to be the case on Fedora 9, for example), so check whether <pcap/bluetooth.h> is usable. Update a comment - F9 appears to have a "/usr/include/pcap.h" if you install the libpcap headers. When adding -I flags when running a compiler-based test, add them to CPPFLAGS, not CFLAGS - the latter doesn't work right with AC_CHECK_HEADERS, as the "gcc -E" run doesn't have the -I flags added.
2008-09-26 05:45:50 +08:00
ac_rmfiles=
for ac_file in $ac_files
do
case $ac_file in
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
*.$ac_ext | *.xcoff | *.tds | *.d | *.pdb | *.xSYM | *.bb | *.bbg | *.map | *.inf | *.dSYM | *.o | *.obj ) ;;
We support building tcpdump with versions of libpcap other than the one with which it was released, and DLT_BLUETOOTH_HCI_H4_WITH_PHDR might be defined by pcap-bpf.h without pcap/bluetooth.h being present (as appears to be the case on Fedora 9, for example), so check whether <pcap/bluetooth.h> is usable. Update a comment - F9 appears to have a "/usr/include/pcap.h" if you install the libpcap headers. When adding -I flags when running a compiler-based test, add them to CPPFLAGS, not CFLAGS - the latter doesn't work right with AC_CHECK_HEADERS, as the "gcc -E" run doesn't have the -I flags added.
2008-09-26 05:45:50 +08:00
* ) ac_rmfiles="$ac_rmfiles $ac_file";;
esac
done
rm -f $ac_rmfiles
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
if { { ac_try="$ac_link_default"
We support building tcpdump with versions of libpcap other than the one with which it was released, and DLT_BLUETOOTH_HCI_H4_WITH_PHDR might be defined by pcap-bpf.h without pcap/bluetooth.h being present (as appears to be the case on Fedora 9, for example), so check whether <pcap/bluetooth.h> is usable. Update a comment - F9 appears to have a "/usr/include/pcap.h" if you install the libpcap headers. When adding -I flags when running a compiler-based test, add them to CPPFLAGS, not CFLAGS - the latter doesn't work right with AC_CHECK_HEADERS, as the "gcc -E" run doesn't have the -I flags added.
2008-09-26 05:45:50 +08:00
case "(($ac_try" in
*\"* | *\`* | *\\*) ac_try_echo=\$ac_try;;
*) ac_try_echo=$ac_try;;
esac
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
eval ac_try_echo="\"\$as_me:${as_lineno-$LINENO}: $ac_try_echo\""
$as_echo "$ac_try_echo"; } >&5
We support building tcpdump with versions of libpcap other than the one with which it was released, and DLT_BLUETOOTH_HCI_H4_WITH_PHDR might be defined by pcap-bpf.h without pcap/bluetooth.h being present (as appears to be the case on Fedora 9, for example), so check whether <pcap/bluetooth.h> is usable. Update a comment - F9 appears to have a "/usr/include/pcap.h" if you install the libpcap headers. When adding -I flags when running a compiler-based test, add them to CPPFLAGS, not CFLAGS - the latter doesn't work right with AC_CHECK_HEADERS, as the "gcc -E" run doesn't have the -I flags added.
2008-09-26 05:45:50 +08:00
(eval "$ac_link_default") 2>&5
Regenerate with autoconf 2.57.
2004-01-14 11:15:08 +08:00
ac_status=$?
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
$as_echo "$as_me:${as_lineno-$LINENO}: \$? = $ac_status" >&5
test $ac_status = 0; }; then :
We support building tcpdump with versions of libpcap other than the one with which it was released, and DLT_BLUETOOTH_HCI_H4_WITH_PHDR might be defined by pcap-bpf.h without pcap/bluetooth.h being present (as appears to be the case on Fedora 9, for example), so check whether <pcap/bluetooth.h> is usable. Update a comment - F9 appears to have a "/usr/include/pcap.h" if you install the libpcap headers. When adding -I flags when running a compiler-based test, add them to CPPFLAGS, not CFLAGS - the latter doesn't work right with AC_CHECK_HEADERS, as the "gcc -E" run doesn't have the -I flags added.
2008-09-26 05:45:50 +08:00
# Autoconf-2.13 could set the ac_cv_exeext variable to `no'.
# So ignore a value of `no', otherwise this would lead to `EXEEXT = no'
# in a Makefile. We should not override ac_cv_exeext if it was cached,
# so that the user can short-circuit this test for compilers unknown to
# Autoconf.
for ac_file in $ac_files ''
From Andrew Church <andrew@users.sourceforge.net>: when testing for "pcap_version", "pcap_debug", and "yydebug", don't add our own functions referring to those variables - GCC 3.4.1 optimizes the test code out before the link is done, as it's in a function that's not called.
2004-08-27 15:17:03 +08:00
do
test -f "$ac_file" || continue
Regenerate with autoconf 2.57.
2004-01-14 11:15:08 +08:00
case $ac_file in
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
*.$ac_ext | *.xcoff | *.tds | *.d | *.pdb | *.xSYM | *.bb | *.bbg | *.map | *.inf | *.dSYM | *.o | *.obj )
Add -Wpointer-arith to the list of warnings we enable with GCC.
2005-11-08 10:59:40 +08:00
;;
From Andrew Church <andrew@users.sourceforge.net>: when testing for "pcap_version", "pcap_debug", and "yydebug", don't add our own functions referring to those variables - GCC 3.4.1 optimizes the test code out before the link is done, as it's in a function that's not called.
2004-08-27 15:17:03 +08:00
[ab].out )
Add -Wpointer-arith to the list of warnings we enable with GCC.
2005-11-08 10:59:40 +08:00
# We found the default executable, but exeext='' is most
# certainly right.
break;;
From Andrew Church <andrew@users.sourceforge.net>: when testing for "pcap_version", "pcap_debug", and "yydebug", don't add our own functions referring to those variables - GCC 3.4.1 optimizes the test code out before the link is done, as it's in a function that's not called.
2004-08-27 15:17:03 +08:00
*.* )
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
if test "${ac_cv_exeext+set}" = set && test "$ac_cv_exeext" != no;
We support building tcpdump with versions of libpcap other than the one with which it was released, and DLT_BLUETOOTH_HCI_H4_WITH_PHDR might be defined by pcap-bpf.h without pcap/bluetooth.h being present (as appears to be the case on Fedora 9, for example), so check whether <pcap/bluetooth.h> is usable. Update a comment - F9 appears to have a "/usr/include/pcap.h" if you install the libpcap headers. When adding -I flags when running a compiler-based test, add them to CPPFLAGS, not CFLAGS - the latter doesn't work right with AC_CHECK_HEADERS, as the "gcc -E" run doesn't have the -I flags added.
2008-09-26 05:45:50 +08:00
then :; else
ac_cv_exeext=`expr "$ac_file" : '[^.]*\(\..*\)'`
fi
# We set ac_cv_exeext here because the later test for it is not
# safe: cross compilers may not add the suffix if given an `-o'
# argument, so we may need to know it at that point already.
# Even if this section looks crufty: it has the advantage of
# actually working.
Add -Wpointer-arith to the list of warnings we enable with GCC.
2005-11-08 10:59:40 +08:00
break;;
From Andrew Church <andrew@users.sourceforge.net>: when testing for "pcap_version", "pcap_debug", and "yydebug", don't add our own functions referring to those variables - GCC 3.4.1 optimizes the test code out before the link is done, as it's in a function that's not called.
2004-08-27 15:17:03 +08:00
* )
Add -Wpointer-arith to the list of warnings we enable with GCC.
2005-11-08 10:59:40 +08:00
break;;
First stage of adding support for 64-bit integral data types - this causes "int64_t" and "u_int64_t" to be defined by the configure script, and causes "missing/bittypes.h" to attempt to define "u_int64_t" in a fashion that should, with any luck, work on MSVC++ and various flavors of GNU C on Windows.
2004-04-17 12:33:16 +08:00
esac
Regenerate with autoconf 2.57.
2004-01-14 11:15:08 +08:00
done
We support building tcpdump with versions of libpcap other than the one with which it was released, and DLT_BLUETOOTH_HCI_H4_WITH_PHDR might be defined by pcap-bpf.h without pcap/bluetooth.h being present (as appears to be the case on Fedora 9, for example), so check whether <pcap/bluetooth.h> is usable. Update a comment - F9 appears to have a "/usr/include/pcap.h" if you install the libpcap headers. When adding -I flags when running a compiler-based test, add them to CPPFLAGS, not CFLAGS - the latter doesn't work right with AC_CHECK_HEADERS, as the "gcc -E" run doesn't have the -I flags added.
2008-09-26 05:45:50 +08:00
test "$ac_cv_exeext" = no && ac_cv_exeext=
Regenerate with autoconf 2.57.
2004-01-14 11:15:08 +08:00
else
We support building tcpdump with versions of libpcap other than the one with which it was released, and DLT_BLUETOOTH_HCI_H4_WITH_PHDR might be defined by pcap-bpf.h without pcap/bluetooth.h being present (as appears to be the case on Fedora 9, for example), so check whether <pcap/bluetooth.h> is usable. Update a comment - F9 appears to have a "/usr/include/pcap.h" if you install the libpcap headers. When adding -I flags when running a compiler-based test, add them to CPPFLAGS, not CFLAGS - the latter doesn't work right with AC_CHECK_HEADERS, as the "gcc -E" run doesn't have the -I flags added.
2008-09-26 05:45:50 +08:00
ac_file=''
fi
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
if test -z "$ac_file"; then :
{ $as_echo "$as_me:${as_lineno-$LINENO}: result: no" >&5
$as_echo "no" >&6; }
$as_echo "$as_me: failed program was:" >&5
From Andrew Church <andrew@users.sourceforge.net>: when testing for "pcap_version", "pcap_debug", and "yydebug", don't add our own functions referring to those variables - GCC 3.4.1 optimizes the test code out before the link is done, as it's in a function that's not called.
2004-08-27 15:17:03 +08:00
sed 's/^/| /' conftest.$ac_ext >&5
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
{ { $as_echo "$as_me:${as_lineno-$LINENO}: error: in \`$ac_pwd':" >&5
$as_echo "$as_me: error: in \`$ac_pwd':" >&2;}
as_fn_error 77 "C compiler cannot create executables
See \`config.log' for more details" "$LINENO" 5; }
else
{ $as_echo "$as_me:${as_lineno-$LINENO}: result: yes" >&5
$as_echo "yes" >&6; }
Regenerate with autoconf 2.57.
2004-01-14 11:15:08 +08:00
fi
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
{ $as_echo "$as_me:${as_lineno-$LINENO}: checking for C compiler default output file name" >&5
$as_echo_n "checking for C compiler default output file name... " >&6; }
{ $as_echo "$as_me:${as_lineno-$LINENO}: result: $ac_file" >&5
$as_echo "$ac_file" >&6; }
Regenerate with autoconf 2.57.
2004-01-14 11:15:08 +08:00
ac_exeext=$ac_cv_exeext
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
rm -f -r a.out a.out.dSYM a.exe conftest$ac_cv_exeext b.out
ac_clean_files=$ac_clean_files_save
{ $as_echo "$as_me:${as_lineno-$LINENO}: checking for suffix of executables" >&5
$as_echo_n "checking for suffix of executables... " >&6; }
if { { ac_try="$ac_link"
case "(($ac_try" in
Check for extra networking libraries before checking for IPv6. On some platforms, such as SunOS 5.x, building the "do we have IPv6 support?" test program requires the extra networking libraries, so we need to know what extra networking libraries are required before doing that test.
2013-04-07 04:03:58 +08:00
*\"* | *\`* | *\\*) ac_try_echo=\$ac_try;;
*) ac_try_echo=$ac_try;;
esac
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
eval ac_try_echo="\"\$as_me:${as_lineno-$LINENO}: $ac_try_echo\""
$as_echo "$ac_try_echo"; } >&5
(eval "$ac_link") 2>&5
Check for extra networking libraries before checking for IPv6. On some platforms, such as SunOS 5.x, building the "do we have IPv6 support?" test program requires the extra networking libraries, so we need to know what extra networking libraries are required before doing that test.
2013-04-07 04:03:58 +08:00
ac_status=$?
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
$as_echo "$as_me:${as_lineno-$LINENO}: \$? = $ac_status" >&5
test $ac_status = 0; }; then :
Regenerate with autoconf 2.57.
2004-01-14 11:15:08 +08:00
# If both `conftest.exe' and `conftest' are `present' (well, observable)
# catch `conftest.exe'. For instance with Cygwin, `ls conftest' will
# work properly (i.e., refer to `conftest.exe'), while it won't with
# `rm'.
From Andrew Church <andrew@users.sourceforge.net>: when testing for "pcap_version", "pcap_debug", and "yydebug", don't add our own functions referring to those variables - GCC 3.4.1 optimizes the test code out before the link is done, as it's in a function that's not called.
2004-08-27 15:17:03 +08:00
for ac_file in conftest.exe conftest conftest.*; do
test -f "$ac_file" || continue
Regenerate with autoconf 2.57.
2004-01-14 11:15:08 +08:00
case $ac_file in
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
*.$ac_ext | *.xcoff | *.tds | *.d | *.pdb | *.xSYM | *.bb | *.bbg | *.map | *.inf | *.dSYM | *.o | *.obj ) ;;
Regenerate with autoconf 2.57.
2004-01-14 11:15:08 +08:00
*.* ) ac_cv_exeext=`expr "$ac_file" : '[^.]*\(\..*\)'`
Add -Wpointer-arith to the list of warnings we enable with GCC.
2005-11-08 10:59:40 +08:00
break;;
Regenerate with autoconf 2.57.
2004-01-14 11:15:08 +08:00
* ) break;;
esac
done
Initial revision
1999-10-08 07:47:09 +08:00
else
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
{ { $as_echo "$as_me:${as_lineno-$LINENO}: error: in \`$ac_pwd':" >&5
$as_echo "$as_me: error: in \`$ac_pwd':" >&2;}
as_fn_error $? "cannot compute suffix of executables: cannot compile and link
See \`config.log' for more details" "$LINENO" 5; }
Regenerate with autoconf 2.57.
2004-01-14 11:15:08 +08:00
fi
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
rm -f conftest conftest$ac_cv_exeext
{ $as_echo "$as_me:${as_lineno-$LINENO}: result: $ac_cv_exeext" >&5
$as_echo "$ac_cv_exeext" >&6; }
Regenerate with autoconf 2.57.
2004-01-14 11:15:08 +08:00
rm -f conftest.$ac_ext
EXEEXT=$ac_cv_exeext
ac_exeext=$EXEEXT
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
cat confdefs.h - <<_ACEOF >conftest.$ac_ext
/* end confdefs.h. */
#include <stdio.h>
int
main ()
{
FILE *f = fopen ("conftest.out", "w");
return ferror (f) || fclose (f) != 0;
;
return 0;
}
Check for extra networking libraries before checking for IPv6. On some platforms, such as SunOS 5.x, building the "do we have IPv6 support?" test program requires the extra networking libraries, so we need to know what extra networking libraries are required before doing that test.
2013-04-07 04:03:58 +08:00
_ACEOF
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
ac_clean_files="$ac_clean_files conftest.out"
# Check that the compiler produces executables we can run. If not, either
# the compiler is broken, or we cross compile.
{ $as_echo "$as_me:${as_lineno-$LINENO}: checking whether we are cross compiling" >&5
$as_echo_n "checking whether we are cross compiling... " >&6; }
if test "$cross_compiling" != yes; then
{ { ac_try="$ac_link"
case "(($ac_try" in
*\"* | *\`* | *\\*) ac_try_echo=\$ac_try;;
*) ac_try_echo=$ac_try;;
esac
eval ac_try_echo="\"\$as_me:${as_lineno-$LINENO}: $ac_try_echo\""
$as_echo "$ac_try_echo"; } >&5
(eval "$ac_link") 2>&5
ac_status=$?
$as_echo "$as_me:${as_lineno-$LINENO}: \$? = $ac_status" >&5
test $ac_status = 0; }
if { ac_try='./conftest$ac_cv_exeext'
{ { case "(($ac_try" in
*\"* | *\`* | *\\*) ac_try_echo=\$ac_try;;
*) ac_try_echo=$ac_try;;
esac
eval ac_try_echo="\"\$as_me:${as_lineno-$LINENO}: $ac_try_echo\""
$as_echo "$ac_try_echo"; } >&5
(eval "$ac_try") 2>&5
ac_status=$?
$as_echo "$as_me:${as_lineno-$LINENO}: \$? = $ac_status" >&5
test $ac_status = 0; }; }; then
cross_compiling=no
else
if test "$cross_compiling" = maybe; then
cross_compiling=yes
else
{ { $as_echo "$as_me:${as_lineno-$LINENO}: error: in \`$ac_pwd':" >&5
$as_echo "$as_me: error: in \`$ac_pwd':" >&2;}
as_fn_error $? "cannot run C compiled programs.
If you meant to cross compile, use \`--host'.
See \`config.log' for more details" "$LINENO" 5; }
fi
fi
fi
{ $as_echo "$as_me:${as_lineno-$LINENO}: result: $cross_compiling" >&5
$as_echo "$cross_compiling" >&6; }
rm -f conftest.$ac_ext conftest$ac_cv_exeext conftest.out
ac_clean_files=$ac_clean_files_save
{ $as_echo "$as_me:${as_lineno-$LINENO}: checking for suffix of object files" >&5
$as_echo_n "checking for suffix of object files... " >&6; }
if ${ac_cv_objext+:} false; then :
$as_echo_n "(cached) " >&6
else
cat confdefs.h - <<_ACEOF >conftest.$ac_ext
From Andrew Church <andrew@users.sourceforge.net>: when testing for "pcap_version", "pcap_debug", and "yydebug", don't add our own functions referring to those variables - GCC 3.4.1 optimizes the test code out before the link is done, as it's in a function that's not called.
2004-08-27 15:17:03 +08:00
/* end confdefs.h. */
Initial revision
1999-10-08 07:47:09 +08:00
Regenerate with autoconf 2.57.
2004-01-14 11:15:08 +08:00
int
main ()
{
Initial revision
1999-10-08 07:47:09 +08:00
Regenerate with autoconf 2.57.
2004-01-14 11:15:08 +08:00
;
return 0;
}
_ACEOF
rm -f conftest.o conftest.obj
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
if { { ac_try="$ac_compile"
We support building tcpdump with versions of libpcap other than the one with which it was released, and DLT_BLUETOOTH_HCI_H4_WITH_PHDR might be defined by pcap-bpf.h without pcap/bluetooth.h being present (as appears to be the case on Fedora 9, for example), so check whether <pcap/bluetooth.h> is usable. Update a comment - F9 appears to have a "/usr/include/pcap.h" if you install the libpcap headers. When adding -I flags when running a compiler-based test, add them to CPPFLAGS, not CFLAGS - the latter doesn't work right with AC_CHECK_HEADERS, as the "gcc -E" run doesn't have the -I flags added.
2008-09-26 05:45:50 +08:00
case "(($ac_try" in
*\"* | *\`* | *\\*) ac_try_echo=\$ac_try;;
*) ac_try_echo=$ac_try;;
esac
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
eval ac_try_echo="\"\$as_me:${as_lineno-$LINENO}: $ac_try_echo\""
$as_echo "$ac_try_echo"; } >&5
We support building tcpdump with versions of libpcap other than the one with which it was released, and DLT_BLUETOOTH_HCI_H4_WITH_PHDR might be defined by pcap-bpf.h without pcap/bluetooth.h being present (as appears to be the case on Fedora 9, for example), so check whether <pcap/bluetooth.h> is usable. Update a comment - F9 appears to have a "/usr/include/pcap.h" if you install the libpcap headers. When adding -I flags when running a compiler-based test, add them to CPPFLAGS, not CFLAGS - the latter doesn't work right with AC_CHECK_HEADERS, as the "gcc -E" run doesn't have the -I flags added.
2008-09-26 05:45:50 +08:00
(eval "$ac_compile") 2>&5
Regenerate with autoconf 2.57.
2004-01-14 11:15:08 +08:00
ac_status=$?
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
$as_echo "$as_me:${as_lineno-$LINENO}: \$? = $ac_status" >&5
test $ac_status = 0; }; then :
We support building tcpdump with versions of libpcap other than the one with which it was released, and DLT_BLUETOOTH_HCI_H4_WITH_PHDR might be defined by pcap-bpf.h without pcap/bluetooth.h being present (as appears to be the case on Fedora 9, for example), so check whether <pcap/bluetooth.h> is usable. Update a comment - F9 appears to have a "/usr/include/pcap.h" if you install the libpcap headers. When adding -I flags when running a compiler-based test, add them to CPPFLAGS, not CFLAGS - the latter doesn't work right with AC_CHECK_HEADERS, as the "gcc -E" run doesn't have the -I flags added.
2008-09-26 05:45:50 +08:00
for ac_file in conftest.o conftest.obj conftest.*; do
test -f "$ac_file" || continue;
Regenerate with autoconf 2.57.
2004-01-14 11:15:08 +08:00
case $ac_file in
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
*.$ac_ext | *.xcoff | *.tds | *.d | *.pdb | *.xSYM | *.bb | *.bbg | *.map | *.inf | *.dSYM ) ;;
Regenerate with autoconf 2.57.
2004-01-14 11:15:08 +08:00
*) ac_cv_objext=`expr "$ac_file" : '.*\.\(.*\)'`
break;;
esac
done
Bring in KAME IPv6 tcpdump. replaces esp/ah/isakmp decoder. Hope I did not break anything. Portability on IPv4-only node needs checking, I'll do this very soon. (sorry for rather jumbo commit) XXx what is _FAVOR_BSD?
1999-10-30 13:11:06 +08:00
else
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
$as_echo "$as_me: failed program was:" >&5
From Andrew Church <andrew@users.sourceforge.net>: when testing for "pcap_version", "pcap_debug", and "yydebug", don't add our own functions referring to those variables - GCC 3.4.1 optimizes the test code out before the link is done, as it's in a function that's not called.
2004-08-27 15:17:03 +08:00
sed 's/^/| /' conftest.$ac_ext >&5
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
{ { $as_echo "$as_me:${as_lineno-$LINENO}: error: in \`$ac_pwd':" >&5
$as_echo "$as_me: error: in \`$ac_pwd':" >&2;}
as_fn_error $? "cannot compute suffix of object files: cannot compile
See \`config.log' for more details" "$LINENO" 5; }
Bring in KAME IPv6 tcpdump. replaces esp/ah/isakmp decoder. Hope I did not break anything. Portability on IPv4-only node needs checking, I'll do this very soon. (sorry for rather jumbo commit) XXx what is _FAVOR_BSD?
1999-10-30 13:11:06 +08:00
fi
Regenerate with autoconf 2.57.
2004-01-14 11:15:08 +08:00
rm -f conftest.$ac_cv_objext conftest.$ac_ext
fi
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
{ $as_echo "$as_me:${as_lineno-$LINENO}: result: $ac_cv_objext" >&5
$as_echo "$ac_cv_objext" >&6; }
Regenerate with autoconf 2.57.
2004-01-14 11:15:08 +08:00
OBJEXT=$ac_cv_objext
ac_objext=$OBJEXT
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
{ $as_echo "$as_me:${as_lineno-$LINENO}: checking whether we are using the GNU C compiler" >&5
$as_echo_n "checking whether we are using the GNU C compiler... " >&6; }
if ${ac_cv_c_compiler_gnu+:} false; then :
$as_echo_n "(cached) " >&6
Initial revision
1999-10-08 07:47:09 +08:00
else
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
cat confdefs.h - <<_ACEOF >conftest.$ac_ext
From Andrew Church <andrew@users.sourceforge.net>: when testing for "pcap_version", "pcap_debug", and "yydebug", don't add our own functions referring to those variables - GCC 3.4.1 optimizes the test code out before the link is done, as it's in a function that's not called.
2004-08-27 15:17:03 +08:00
/* end confdefs.h. */
Regenerate with autoconf 2.57.
2004-01-14 11:15:08 +08:00
int
main ()
{
#ifndef __GNUC__
choke me
#endif
;
return 0;
}
_ACEOF
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
if ac_fn_c_try_compile "$LINENO"; then :
Regenerate with autoconf 2.57.
2004-01-14 11:15:08 +08:00
ac_compiler_gnu=yes
else
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
ac_compiler_gnu=no
Regenerate with autoconf 2.57.
2004-01-14 11:15:08 +08:00
fi
We support building tcpdump with versions of libpcap other than the one with which it was released, and DLT_BLUETOOTH_HCI_H4_WITH_PHDR might be defined by pcap-bpf.h without pcap/bluetooth.h being present (as appears to be the case on Fedora 9, for example), so check whether <pcap/bluetooth.h> is usable. Update a comment - F9 appears to have a "/usr/include/pcap.h" if you install the libpcap headers. When adding -I flags when running a compiler-based test, add them to CPPFLAGS, not CFLAGS - the latter doesn't work right with AC_CHECK_HEADERS, as the "gcc -E" run doesn't have the -I flags added.
2008-09-26 05:45:50 +08:00
rm -f core conftest.err conftest.$ac_objext conftest.$ac_ext
Regenerate with autoconf 2.57.
2004-01-14 11:15:08 +08:00
ac_cv_c_compiler_gnu=$ac_compiler_gnu
fi
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
{ $as_echo "$as_me:${as_lineno-$LINENO}: result: $ac_cv_c_compiler_gnu" >&5
$as_echo "$ac_cv_c_compiler_gnu" >&6; }
if test $ac_compiler_gnu = yes; then
GCC=yes
else
GCC=
fi
Regenerate with autoconf 2.57.
2004-01-14 11:15:08 +08:00
ac_test_CFLAGS=${CFLAGS+set}
ac_save_CFLAGS=$CFLAGS
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
{ $as_echo "$as_me:${as_lineno-$LINENO}: checking whether $CC accepts -g" >&5
$as_echo_n "checking whether $CC accepts -g... " >&6; }
if ${ac_cv_prog_cc_g+:} false; then :
$as_echo_n "(cached) " >&6
Regenerate with autoconf 2.57.
2004-01-14 11:15:08 +08:00
else
We support building tcpdump with versions of libpcap other than the one with which it was released, and DLT_BLUETOOTH_HCI_H4_WITH_PHDR might be defined by pcap-bpf.h without pcap/bluetooth.h being present (as appears to be the case on Fedora 9, for example), so check whether <pcap/bluetooth.h> is usable. Update a comment - F9 appears to have a "/usr/include/pcap.h" if you install the libpcap headers. When adding -I flags when running a compiler-based test, add them to CPPFLAGS, not CFLAGS - the latter doesn't work right with AC_CHECK_HEADERS, as the "gcc -E" run doesn't have the -I flags added.
2008-09-26 05:45:50 +08:00
ac_save_c_werror_flag=$ac_c_werror_flag
ac_c_werror_flag=yes
ac_cv_prog_cc_g=no
CFLAGS="-g"
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
cat confdefs.h - <<_ACEOF >conftest.$ac_ext
From Andrew Church <andrew@users.sourceforge.net>: when testing for "pcap_version", "pcap_debug", and "yydebug", don't add our own functions referring to those variables - GCC 3.4.1 optimizes the test code out before the link is done, as it's in a function that's not called.
2004-08-27 15:17:03 +08:00
/* end confdefs.h. */
Regenerate with autoconf 2.57.
2004-01-14 11:15:08 +08:00
int
main ()
{
;
return 0;
}
_ACEOF
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
if ac_fn_c_try_compile "$LINENO"; then :
We support building tcpdump with versions of libpcap other than the one with which it was released, and DLT_BLUETOOTH_HCI_H4_WITH_PHDR might be defined by pcap-bpf.h without pcap/bluetooth.h being present (as appears to be the case on Fedora 9, for example), so check whether <pcap/bluetooth.h> is usable. Update a comment - F9 appears to have a "/usr/include/pcap.h" if you install the libpcap headers. When adding -I flags when running a compiler-based test, add them to CPPFLAGS, not CFLAGS - the latter doesn't work right with AC_CHECK_HEADERS, as the "gcc -E" run doesn't have the -I flags added.
2008-09-26 05:45:50 +08:00
ac_cv_prog_cc_g=yes
else
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
CFLAGS=""
cat confdefs.h - <<_ACEOF >conftest.$ac_ext
We support building tcpdump with versions of libpcap other than the one with which it was released, and DLT_BLUETOOTH_HCI_H4_WITH_PHDR might be defined by pcap-bpf.h without pcap/bluetooth.h being present (as appears to be the case on Fedora 9, for example), so check whether <pcap/bluetooth.h> is usable. Update a comment - F9 appears to have a "/usr/include/pcap.h" if you install the libpcap headers. When adding -I flags when running a compiler-based test, add them to CPPFLAGS, not CFLAGS - the latter doesn't work right with AC_CHECK_HEADERS, as the "gcc -E" run doesn't have the -I flags added.
2008-09-26 05:45:50 +08:00
/* end confdefs.h. */
int
main ()
{
;
return 0;
}
_ACEOF
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
if ac_fn_c_try_compile "$LINENO"; then :
Check for extra networking libraries before checking for IPv6. On some platforms, such as SunOS 5.x, building the "do we have IPv6 support?" test program requires the extra networking libraries, so we need to know what extra networking libraries are required before doing that test.
2013-04-07 04:03:58 +08:00
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
else
ac_c_werror_flag=$ac_save_c_werror_flag
Check for extra networking libraries before checking for IPv6. On some platforms, such as SunOS 5.x, building the "do we have IPv6 support?" test program requires the extra networking libraries, so we need to know what extra networking libraries are required before doing that test.
2013-04-07 04:03:58 +08:00
CFLAGS="-g"
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
cat confdefs.h - <<_ACEOF >conftest.$ac_ext
Check for extra networking libraries before checking for IPv6. On some platforms, such as SunOS 5.x, building the "do we have IPv6 support?" test program requires the extra networking libraries, so we need to know what extra networking libraries are required before doing that test.
2013-04-07 04:03:58 +08:00
/* end confdefs.h. */
int
main ()
{
We support building tcpdump with versions of libpcap other than the one with which it was released, and DLT_BLUETOOTH_HCI_H4_WITH_PHDR might be defined by pcap-bpf.h without pcap/bluetooth.h being present (as appears to be the case on Fedora 9, for example), so check whether <pcap/bluetooth.h> is usable. Update a comment - F9 appears to have a "/usr/include/pcap.h" if you install the libpcap headers. When adding -I flags when running a compiler-based test, add them to CPPFLAGS, not CFLAGS - the latter doesn't work right with AC_CHECK_HEADERS, as the "gcc -E" run doesn't have the -I flags added.
2008-09-26 05:45:50 +08:00
;
return 0;
}
_ACEOF
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
if ac_fn_c_try_compile "$LINENO"; then :
Initial revision
1999-10-08 07:47:09 +08:00
ac_cv_prog_cc_g=yes
We support building tcpdump with versions of libpcap other than the one with which it was released, and DLT_BLUETOOTH_HCI_H4_WITH_PHDR might be defined by pcap-bpf.h without pcap/bluetooth.h being present (as appears to be the case on Fedora 9, for example), so check whether <pcap/bluetooth.h> is usable. Update a comment - F9 appears to have a "/usr/include/pcap.h" if you install the libpcap headers. When adding -I flags when running a compiler-based test, add them to CPPFLAGS, not CFLAGS - the latter doesn't work right with AC_CHECK_HEADERS, as the "gcc -E" run doesn't have the -I flags added.
2008-09-26 05:45:50 +08:00
fi
rm -f core conftest.err conftest.$ac_objext conftest.$ac_ext
fi
rm -f core conftest.err conftest.$ac_objext conftest.$ac_ext
Initial revision
1999-10-08 07:47:09 +08:00
fi
We support building tcpdump with versions of libpcap other than the one with which it was released, and DLT_BLUETOOTH_HCI_H4_WITH_PHDR might be defined by pcap-bpf.h without pcap/bluetooth.h being present (as appears to be the case on Fedora 9, for example), so check whether <pcap/bluetooth.h> is usable. Update a comment - F9 appears to have a "/usr/include/pcap.h" if you install the libpcap headers. When adding -I flags when running a compiler-based test, add them to CPPFLAGS, not CFLAGS - the latter doesn't work right with AC_CHECK_HEADERS, as the "gcc -E" run doesn't have the -I flags added.
2008-09-26 05:45:50 +08:00
rm -f core conftest.err conftest.$ac_objext conftest.$ac_ext
ac_c_werror_flag=$ac_save_c_werror_flag
Regenerate with autoconf 2.57.
2004-01-14 11:15:08 +08:00
fi
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
{ $as_echo "$as_me:${as_lineno-$LINENO}: result: $ac_cv_prog_cc_g" >&5
$as_echo "$ac_cv_prog_cc_g" >&6; }
Bring in KAME IPv6 tcpdump. replaces esp/ah/isakmp decoder. Hope I did not break anything. Portability on IPv4-only node needs checking, I'll do this very soon. (sorry for rather jumbo commit) XXx what is _FAVOR_BSD?
1999-10-30 13:11:06 +08:00
if test "$ac_test_CFLAGS" = set; then
Regenerate with autoconf 2.57.
2004-01-14 11:15:08 +08:00
CFLAGS=$ac_save_CFLAGS
Bring in KAME IPv6 tcpdump. replaces esp/ah/isakmp decoder. Hope I did not break anything. Portability on IPv4-only node needs checking, I'll do this very soon. (sorry for rather jumbo commit) XXx what is _FAVOR_BSD?
1999-10-30 13:11:06 +08:00
elif test $ac_cv_prog_cc_g = yes; then
if test "$GCC" = yes; then
Initial revision
1999-10-08 07:47:09 +08:00
CFLAGS="-g -O2"
else
Bring in KAME IPv6 tcpdump. replaces esp/ah/isakmp decoder. Hope I did not break anything. Portability on IPv4-only node needs checking, I'll do this very soon. (sorry for rather jumbo commit) XXx what is _FAVOR_BSD?
1999-10-30 13:11:06 +08:00
CFLAGS="-g"
Initial revision
1999-10-08 07:47:09 +08:00
fi
else
Bring in KAME IPv6 tcpdump. replaces esp/ah/isakmp decoder. Hope I did not break anything. Portability on IPv4-only node needs checking, I'll do this very soon. (sorry for rather jumbo commit) XXx what is _FAVOR_BSD?
1999-10-30 13:11:06 +08:00
if test "$GCC" = yes; then
CFLAGS="-O2"
else
CFLAGS=
fi
Initial revision
1999-10-08 07:47:09 +08:00
fi
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
{ $as_echo "$as_me:${as_lineno-$LINENO}: checking for $CC option to accept ISO C89" >&5
$as_echo_n "checking for $CC option to accept ISO C89... " >&6; }
if ${ac_cv_prog_cc_c89+:} false; then :
$as_echo_n "(cached) " >&6
From Andrew Church <andrew@users.sourceforge.net>: when testing for "pcap_version", "pcap_debug", and "yydebug", don't add our own functions referring to those variables - GCC 3.4.1 optimizes the test code out before the link is done, as it's in a function that's not called.
2004-08-27 15:17:03 +08:00
else
We support building tcpdump with versions of libpcap other than the one with which it was released, and DLT_BLUETOOTH_HCI_H4_WITH_PHDR might be defined by pcap-bpf.h without pcap/bluetooth.h being present (as appears to be the case on Fedora 9, for example), so check whether <pcap/bluetooth.h> is usable. Update a comment - F9 appears to have a "/usr/include/pcap.h" if you install the libpcap headers. When adding -I flags when running a compiler-based test, add them to CPPFLAGS, not CFLAGS - the latter doesn't work right with AC_CHECK_HEADERS, as the "gcc -E" run doesn't have the -I flags added.
2008-09-26 05:45:50 +08:00
ac_cv_prog_cc_c89=no
From Andrew Church <andrew@users.sourceforge.net>: when testing for "pcap_version", "pcap_debug", and "yydebug", don't add our own functions referring to those variables - GCC 3.4.1 optimizes the test code out before the link is done, as it's in a function that's not called.
2004-08-27 15:17:03 +08:00
ac_save_CC=$CC
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
cat confdefs.h - <<_ACEOF >conftest.$ac_ext
From Andrew Church <andrew@users.sourceforge.net>: when testing for "pcap_version", "pcap_debug", and "yydebug", don't add our own functions referring to those variables - GCC 3.4.1 optimizes the test code out before the link is done, as it's in a function that's not called.
2004-08-27 15:17:03 +08:00
/* end confdefs.h. */
#include <stdarg.h>
#include <stdio.h>
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
struct stat;
From Andrew Church <andrew@users.sourceforge.net>: when testing for "pcap_version", "pcap_debug", and "yydebug", don't add our own functions referring to those variables - GCC 3.4.1 optimizes the test code out before the link is done, as it's in a function that's not called.
2004-08-27 15:17:03 +08:00
/* Most of the following tests are stolen from RCS 5.7's src/conf.sh. */
struct buf { int x; };
FILE * (*rcsopen) (struct buf *, struct stat *, int);
static char *e (p, i)
char **p;
int i;
{
return p[i];
}
static char *f (char * (*g) (char **, int), char **p, ...)
{
char *s;
va_list v;
va_start (v,p);
s = g (p, va_arg (v,int));
va_end (v);
return s;
}
Add -Wpointer-arith to the list of warnings we enable with GCC.
2005-11-08 10:59:40 +08:00
/* OSF 4.0 Compaq cc is some sort of almost-ANSI by default. It has
function prototypes and stuff, but not '\xHH' hex character constants.
These don't provoke an error unfortunately, instead are silently treated
We support building tcpdump with versions of libpcap other than the one with which it was released, and DLT_BLUETOOTH_HCI_H4_WITH_PHDR might be defined by pcap-bpf.h without pcap/bluetooth.h being present (as appears to be the case on Fedora 9, for example), so check whether <pcap/bluetooth.h> is usable. Update a comment - F9 appears to have a "/usr/include/pcap.h" if you install the libpcap headers. When adding -I flags when running a compiler-based test, add them to CPPFLAGS, not CFLAGS - the latter doesn't work right with AC_CHECK_HEADERS, as the "gcc -E" run doesn't have the -I flags added.
2008-09-26 05:45:50 +08:00
as 'x'. The following induces an error, until -std is added to get
Add -Wpointer-arith to the list of warnings we enable with GCC.
2005-11-08 10:59:40 +08:00
proper ANSI mode. Curiously '\x00'!='x' always comes out true, for an
array size at least. It's necessary to write '\x00'==0 to get something
We support building tcpdump with versions of libpcap other than the one with which it was released, and DLT_BLUETOOTH_HCI_H4_WITH_PHDR might be defined by pcap-bpf.h without pcap/bluetooth.h being present (as appears to be the case on Fedora 9, for example), so check whether <pcap/bluetooth.h> is usable. Update a comment - F9 appears to have a "/usr/include/pcap.h" if you install the libpcap headers. When adding -I flags when running a compiler-based test, add them to CPPFLAGS, not CFLAGS - the latter doesn't work right with AC_CHECK_HEADERS, as the "gcc -E" run doesn't have the -I flags added.
2008-09-26 05:45:50 +08:00
that's true only with -std. */
Add -Wpointer-arith to the list of warnings we enable with GCC.
2005-11-08 10:59:40 +08:00
int osf4_cc_array ['\x00' == 0 ? 1 : -1];
We support building tcpdump with versions of libpcap other than the one with which it was released, and DLT_BLUETOOTH_HCI_H4_WITH_PHDR might be defined by pcap-bpf.h without pcap/bluetooth.h being present (as appears to be the case on Fedora 9, for example), so check whether <pcap/bluetooth.h> is usable. Update a comment - F9 appears to have a "/usr/include/pcap.h" if you install the libpcap headers. When adding -I flags when running a compiler-based test, add them to CPPFLAGS, not CFLAGS - the latter doesn't work right with AC_CHECK_HEADERS, as the "gcc -E" run doesn't have the -I flags added.
2008-09-26 05:45:50 +08:00
/* IBM C 6 for AIX is almost-ANSI by default, but it replaces macro parameters
inside strings and character constants. */
#define FOO(x) 'x'
int xlc6_cc_array[FOO(a) == 'x' ? 1 : -1];
From Andrew Church <andrew@users.sourceforge.net>: when testing for "pcap_version", "pcap_debug", and "yydebug", don't add our own functions referring to those variables - GCC 3.4.1 optimizes the test code out before the link is done, as it's in a function that's not called.
2004-08-27 15:17:03 +08:00
int test (int i, double x);
struct s1 {int (*f) (int a);};
struct s2 {int (*f) (double a);};
int pairnames (int, char **, FILE *(*)(struct buf *, struct stat *, int), int, int);
int argc;
char **argv;
int
main ()
{
return f (e, argv, 0) != argv[0] || f (e, argv, 1) != argv[1];
;
return 0;
}
_ACEOF
We support building tcpdump with versions of libpcap other than the one with which it was released, and DLT_BLUETOOTH_HCI_H4_WITH_PHDR might be defined by pcap-bpf.h without pcap/bluetooth.h being present (as appears to be the case on Fedora 9, for example), so check whether <pcap/bluetooth.h> is usable. Update a comment - F9 appears to have a "/usr/include/pcap.h" if you install the libpcap headers. When adding -I flags when running a compiler-based test, add them to CPPFLAGS, not CFLAGS - the latter doesn't work right with AC_CHECK_HEADERS, as the "gcc -E" run doesn't have the -I flags added.
2008-09-26 05:45:50 +08:00
for ac_arg in '' -qlanglvl=extc89 -qlanglvl=ansi -std \
-Ae "-Aa -D_HPUX_SOURCE" "-Xc -D__EXTENSIONS__"
From Andrew Church <andrew@users.sourceforge.net>: when testing for "pcap_version", "pcap_debug", and "yydebug", don't add our own functions referring to those variables - GCC 3.4.1 optimizes the test code out before the link is done, as it's in a function that's not called.
2004-08-27 15:17:03 +08:00
do
CC="$ac_save_CC $ac_arg"
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
if ac_fn_c_try_compile "$LINENO"; then :
We support building tcpdump with versions of libpcap other than the one with which it was released, and DLT_BLUETOOTH_HCI_H4_WITH_PHDR might be defined by pcap-bpf.h without pcap/bluetooth.h being present (as appears to be the case on Fedora 9, for example), so check whether <pcap/bluetooth.h> is usable. Update a comment - F9 appears to have a "/usr/include/pcap.h" if you install the libpcap headers. When adding -I flags when running a compiler-based test, add them to CPPFLAGS, not CFLAGS - the latter doesn't work right with AC_CHECK_HEADERS, as the "gcc -E" run doesn't have the -I flags added.
2008-09-26 05:45:50 +08:00
ac_cv_prog_cc_c89=$ac_arg
From Andrew Church <andrew@users.sourceforge.net>: when testing for "pcap_version", "pcap_debug", and "yydebug", don't add our own functions referring to those variables - GCC 3.4.1 optimizes the test code out before the link is done, as it's in a function that's not called.
2004-08-27 15:17:03 +08:00
fi
We support building tcpdump with versions of libpcap other than the one with which it was released, and DLT_BLUETOOTH_HCI_H4_WITH_PHDR might be defined by pcap-bpf.h without pcap/bluetooth.h being present (as appears to be the case on Fedora 9, for example), so check whether <pcap/bluetooth.h> is usable. Update a comment - F9 appears to have a "/usr/include/pcap.h" if you install the libpcap headers. When adding -I flags when running a compiler-based test, add them to CPPFLAGS, not CFLAGS - the latter doesn't work right with AC_CHECK_HEADERS, as the "gcc -E" run doesn't have the -I flags added.
2008-09-26 05:45:50 +08:00
rm -f core conftest.err conftest.$ac_objext
test "x$ac_cv_prog_cc_c89" != "xno" && break
From Andrew Church <andrew@users.sourceforge.net>: when testing for "pcap_version", "pcap_debug", and "yydebug", don't add our own functions referring to those variables - GCC 3.4.1 optimizes the test code out before the link is done, as it's in a function that's not called.
2004-08-27 15:17:03 +08:00
done
We support building tcpdump with versions of libpcap other than the one with which it was released, and DLT_BLUETOOTH_HCI_H4_WITH_PHDR might be defined by pcap-bpf.h without pcap/bluetooth.h being present (as appears to be the case on Fedora 9, for example), so check whether <pcap/bluetooth.h> is usable. Update a comment - F9 appears to have a "/usr/include/pcap.h" if you install the libpcap headers. When adding -I flags when running a compiler-based test, add them to CPPFLAGS, not CFLAGS - the latter doesn't work right with AC_CHECK_HEADERS, as the "gcc -E" run doesn't have the -I flags added.
2008-09-26 05:45:50 +08:00
rm -f conftest.$ac_ext
From Andrew Church <andrew@users.sourceforge.net>: when testing for "pcap_version", "pcap_debug", and "yydebug", don't add our own functions referring to those variables - GCC 3.4.1 optimizes the test code out before the link is done, as it's in a function that's not called.
2004-08-27 15:17:03 +08:00
CC=$ac_save_CC
fi
We support building tcpdump with versions of libpcap other than the one with which it was released, and DLT_BLUETOOTH_HCI_H4_WITH_PHDR might be defined by pcap-bpf.h without pcap/bluetooth.h being present (as appears to be the case on Fedora 9, for example), so check whether <pcap/bluetooth.h> is usable. Update a comment - F9 appears to have a "/usr/include/pcap.h" if you install the libpcap headers. When adding -I flags when running a compiler-based test, add them to CPPFLAGS, not CFLAGS - the latter doesn't work right with AC_CHECK_HEADERS, as the "gcc -E" run doesn't have the -I flags added.
2008-09-26 05:45:50 +08:00
# AC_CACHE_VAL
case "x$ac_cv_prog_cc_c89" in
x)
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
{ $as_echo "$as_me:${as_lineno-$LINENO}: result: none needed" >&5
$as_echo "none needed" >&6; } ;;
We support building tcpdump with versions of libpcap other than the one with which it was released, and DLT_BLUETOOTH_HCI_H4_WITH_PHDR might be defined by pcap-bpf.h without pcap/bluetooth.h being present (as appears to be the case on Fedora 9, for example), so check whether <pcap/bluetooth.h> is usable. Update a comment - F9 appears to have a "/usr/include/pcap.h" if you install the libpcap headers. When adding -I flags when running a compiler-based test, add them to CPPFLAGS, not CFLAGS - the latter doesn't work right with AC_CHECK_HEADERS, as the "gcc -E" run doesn't have the -I flags added.
2008-09-26 05:45:50 +08:00
xno)
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
{ $as_echo "$as_me:${as_lineno-$LINENO}: result: unsupported" >&5
$as_echo "unsupported" >&6; } ;;
From Andrew Church <andrew@users.sourceforge.net>: when testing for "pcap_version", "pcap_debug", and "yydebug", don't add our own functions referring to those variables - GCC 3.4.1 optimizes the test code out before the link is done, as it's in a function that's not called.
2004-08-27 15:17:03 +08:00
*)
We support building tcpdump with versions of libpcap other than the one with which it was released, and DLT_BLUETOOTH_HCI_H4_WITH_PHDR might be defined by pcap-bpf.h without pcap/bluetooth.h being present (as appears to be the case on Fedora 9, for example), so check whether <pcap/bluetooth.h> is usable. Update a comment - F9 appears to have a "/usr/include/pcap.h" if you install the libpcap headers. When adding -I flags when running a compiler-based test, add them to CPPFLAGS, not CFLAGS - the latter doesn't work right with AC_CHECK_HEADERS, as the "gcc -E" run doesn't have the -I flags added.
2008-09-26 05:45:50 +08:00
CC="$CC $ac_cv_prog_cc_c89"
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
{ $as_echo "$as_me:${as_lineno-$LINENO}: result: $ac_cv_prog_cc_c89" >&5
$as_echo "$ac_cv_prog_cc_c89" >&6; } ;;
From Andrew Church <andrew@users.sourceforge.net>: when testing for "pcap_version", "pcap_debug", and "yydebug", don't add our own functions referring to those variables - GCC 3.4.1 optimizes the test code out before the link is done, as it's in a function that's not called.
2004-08-27 15:17:03 +08:00
esac
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
if test "x$ac_cv_prog_cc_c89" != xno; then :
From Andrew Church <andrew@users.sourceforge.net>: when testing for "pcap_version", "pcap_debug", and "yydebug", don't add our own functions referring to those variables - GCC 3.4.1 optimizes the test code out before the link is done, as it's in a function that's not called.
2004-08-27 15:17:03 +08:00
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
fi
We support building tcpdump with versions of libpcap other than the one with which it was released, and DLT_BLUETOOTH_HCI_H4_WITH_PHDR might be defined by pcap-bpf.h without pcap/bluetooth.h being present (as appears to be the case on Fedora 9, for example), so check whether <pcap/bluetooth.h> is usable. Update a comment - F9 appears to have a "/usr/include/pcap.h" if you install the libpcap headers. When adding -I flags when running a compiler-based test, add them to CPPFLAGS, not CFLAGS - the latter doesn't work right with AC_CHECK_HEADERS, as the "gcc -E" run doesn't have the -I flags added.
2008-09-26 05:45:50 +08:00
ac_ext=c
ac_cpp='$CPP $CPPFLAGS'
ac_compile='$CC -c $CFLAGS $CPPFLAGS conftest.$ac_ext >&5'
ac_link='$CC -o conftest$ac_exeext $CFLAGS $CPPFLAGS $LDFLAGS conftest.$ac_ext $LIBS >&5'
ac_compiler_gnu=$ac_cv_c_compiler_gnu
Fix some problems that show up in autoconf 2.64 and later.
2010-01-03 07:29:06 +08:00
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
We support building tcpdump with versions of libpcap other than the one with which it was released, and DLT_BLUETOOTH_HCI_H4_WITH_PHDR might be defined by pcap-bpf.h without pcap/bluetooth.h being present (as appears to be the case on Fedora 9, for example), so check whether <pcap/bluetooth.h> is usable. Update a comment - F9 appears to have a "/usr/include/pcap.h" if you install the libpcap headers. When adding -I flags when running a compiler-based test, add them to CPPFLAGS, not CFLAGS - the latter doesn't work right with AC_CHECK_HEADERS, as the "gcc -E" run doesn't have the -I flags added.
2008-09-26 05:45:50 +08:00
if test "$GCC" = yes ; then
Avoid some warnings from Sun C. Some versions of Sun C support __attribute__ but don't support the "unused" or "format" attributes - they don't fail, but they whine a lot. They also support the "noreturn" attribute, but don't allow it to be applied to function pointers, only to functions. Check whether they can be used without warnings, and use them only if they can.
2013-06-23 05:06:33 +08:00
#
# -Werror forces warnings to be errors.
#
ac_lbl_cc_force_warning_errors=-Werror
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
We no longer use the GCC version, so don't fetch it. Fix some indentation while we're at it.
2013-10-18 10:33:18 +08:00
#
# Use -ffloat-store so that, on 32-bit x86, we don't
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
# do 80-bit arithmetic with the FPU; that way we should
# get the same results for floating-point calculations
# on x86-32 and x86-64.
#
{ $as_echo "$as_me:${as_lineno-$LINENO}: checking whether the compiler supports the -ffloat-store option" >&5
$as_echo_n "checking whether the compiler supports the -ffloat-store option... " >&6; }
save_CFLAGS="$CFLAGS"
We need -Werror when testing whether -f or -m flags work. Thank you, clang, for treating unknown -f flags as warnings, only failing with them if run with -Werror, and spewing out warning messages whenever they're used.
2015-09-29 16:15:53 +08:00
if expr "x-ffloat-store" : "x-W.*" >/dev/null
then
CFLAGS="$CFLAGS $ac_lbl_unknown_warning_option_error -ffloat-store"
elif expr "x-ffloat-store" : "x-f.*" >/dev/null
then
CFLAGS="$CFLAGS -Werror -ffloat-store"
elif expr "x-ffloat-store" : "x-m.*" >/dev/null
then
CFLAGS="$CFLAGS -Werror -ffloat-store"
else
CFLAGS="$CFLAGS -ffloat-store"
fi
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
cat confdefs.h - <<_ACEOF >conftest.$ac_ext
/* end confdefs.h. */
int
main ()
{
return 0
;
return 0;
}
_ACEOF
if ac_fn_c_try_compile "$LINENO"; then :
{ $as_echo "$as_me:${as_lineno-$LINENO}: result: yes" >&5
$as_echo "yes" >&6; }
CFLAGS="$save_CFLAGS"
V_CCOPT="$V_CCOPT -ffloat-store"
else
{ $as_echo "$as_me:${as_lineno-$LINENO}: result: no" >&5
$as_echo "no" >&6; }
CFLAGS="$save_CFLAGS"
fi
rm -f core conftest.err conftest.$ac_objext conftest.$ac_ext
We support building tcpdump with versions of libpcap other than the one with which it was released, and DLT_BLUETOOTH_HCI_H4_WITH_PHDR might be defined by pcap-bpf.h without pcap/bluetooth.h being present (as appears to be the case on Fedora 9, for example), so check whether <pcap/bluetooth.h> is usable. Update a comment - F9 appears to have a "/usr/include/pcap.h" if you install the libpcap headers. When adding -I flags when running a compiler-based test, add them to CPPFLAGS, not CFLAGS - the latter doesn't work right with AC_CHECK_HEADERS, as the "gcc -E" run doesn't have the -I flags added.
2008-09-26 05:45:50 +08:00
else
Initial revision
1999-10-08 07:47:09 +08:00
V_INCLS="$V_INCLS -I/usr/local/include"
LDFLAGS="$LDFLAGS -L/usr/local/lib"
Replace "target_cpu", "target_os", and AC_CANONICAL_SYSTEM with "host_cpu", "host_os", and AC_CANONICAL_HOST, as per Maciej W. Rozycki's patch.
2001-12-10 16:41:15 +08:00
case "$host_os" in
Initial revision
1999-10-08 07:47:09 +08:00
Avoid some warnings from Sun C. Some versions of Sun C support __attribute__ but don't support the "unused" or "format" attributes - they don't fail, but they whine a lot. They also support the "noreturn" attribute, but don't allow it to be applied to function pointers, only to functions. Check whether they can be used without warnings, and use them only if they can.
2013-06-23 05:06:33 +08:00
darwin*)
#
# This is assumed either to be GCC or clang, both
# of which use -Werror to force warnings to be errors.
#
ac_lbl_cc_force_warning_errors=-Werror
;;
Don't try -W flags with HP's C compiler. HP's C compiler cannot be made to exit with a non-zero exit status when given an unknown compiler flag, so you can't use that to figure out if a flag is supported, but it *will* print a warning, which we don't want. In addition, it doesn't support -W flags for warnings in any case, so let's not bother with them.
2013-05-08 14:58:51 +08:00
hpux*)
#
HP C isn't the only compiler on which we must avoid GCC-style -W flags. MIPS C and DEC C also can't be made to reliably Just Say No to those flags, and they don't support those flags, so don't try them with those compilers either.
2013-05-13 03:30:01 +08:00
# HP C, which is what we presume we're using, doesn't
# exit with a non-zero exit status if we hand it an
# invalid -W flag, can't be forced to do so even with
# +We, and doesn't handle GCC-style -W flags, so we
# don't want to try using GCC-style -W flags.
Don't try -W flags with HP's C compiler. HP's C compiler cannot be made to exit with a non-zero exit status when given an unknown compiler flag, so you can't use that to figure out if a flag is supported, but it *will* print a warning, which we don't want. In addition, it doesn't support -W flags for warnings in any case, so let's not bother with them.
2013-05-08 14:58:51 +08:00
#
HP C isn't the only compiler on which we must avoid GCC-style -W flags. MIPS C and DEC C also can't be made to reliably Just Say No to those flags, and they don't support those flags, so don't try them with those compilers either.
2013-05-13 03:30:01 +08:00
ac_lbl_cc_dont_try_gcc_dashW=yes
Don't try -W flags with HP's C compiler. HP's C compiler cannot be made to exit with a non-zero exit status when given an unknown compiler flag, so you can't use that to figure out if a flag is supported, but it *will* print a warning, which we don't want. In addition, it doesn't support -W flags for warnings in any case, so let's not bother with them.
2013-05-08 14:58:51 +08:00
;;
Initial revision
1999-10-08 07:47:09 +08:00
irix*)
HP C isn't the only compiler on which we must avoid GCC-style -W flags. MIPS C and DEC C also can't be made to reliably Just Say No to those flags, and they don't support those flags, so don't try them with those compilers either.
2013-05-13 03:30:01 +08:00
#
# MIPS C, which is what we presume we're using, doesn't
# necessarily exit with a non-zero exit status if we
# hand it an invalid -W flag, can't be forced to do
# so, and doesn't handle GCC-style -W flags, so we
# don't want to try using GCC-style -W flags.
#
ac_lbl_cc_dont_try_gcc_dashW=yes
Explain why we set -xansi -signed for MIPS C.
2013-10-18 13:14:53 +08:00
#
# It also, apparently, defaults to "char" being
# unsigned, unlike most other C implementations;
# I suppose we could say "signed char" whenever
# we want to guarantee a signed "char", but let's
# just force signed chars.
#
# -xansi is normally the default, but the
# configure script was setting it; perhaps -cckr
# was the default in the Old Days. (Then again,
# that would probably be for backwards compatibility
# in the days when ANSI C was Shiny and New, i.e.
# 1989 and the early '90's, so maybe we can just
# drop support for those compilers.)
#
Add -g3 on some platforms even if .devel isn't present. Now that we're requiring autoconf 2.61 or later, AC_PROG_CC sets -g along with -O2 for GCC-like compilers regardless of whether .devel is present. Add "include debugging symbols" options for MIPS C/DEC C regardless of whether .devel is present; that's -g3, which is the version that doesn't turn optimization off (we also turn on -O). Also, don't change the ABI on IRIX depending on .devel. I'm not sure why we were doing that; if somebody has a good reason to continue doing it, please let us know what it is. Expand some comments while we're at it.
2013-10-22 01:56:33 +08:00
# -g is equivalent to -g2, which turns off
# optimization; we choose -g3, which generates
# debugging information but doesn't turn off
# optimization (even if the optimization would
# cause inaccuracies in debugging).
#
V_CCOPT="$V_CCOPT -xansi -signed -g3"
Initial revision
1999-10-08 07:47:09 +08:00
;;
osf*)
Pick up some AC_DEFINE comments from libpcap's aclocal.m4. Remove unused items, and items for which we now have AC_DEFINE() calls that supply a comment, from acconfig.h. Note that a host OS that matches "osf*" is assumed to be DEC OSF1/Digital UNIX/Tru64 UNIX.
2009-07-03 09:59:24 +08:00
#
# Presumed to be DEC OSF/1, Digital UNIX, or
# Tru64 UNIX.
#
HP C isn't the only compiler on which we must avoid GCC-style -W flags. MIPS C and DEC C also can't be made to reliably Just Say No to those flags, and they don't support those flags, so don't try them with those compilers either.
2013-05-13 03:30:01 +08:00
# The DEC C compiler, which is what we presume we're
# using, doesn't exit with a non-zero exit status if we
# hand it an invalid -W flag, can't be forced to do
# so, and doesn't handle GCC-style -W flags, so we
# don't want to try using GCC-style -W flags.
#
ac_lbl_cc_dont_try_gcc_dashW=yes
Add -g3 on some platforms even if .devel isn't present. Now that we're requiring autoconf 2.61 or later, AC_PROG_CC sets -g along with -O2 for GCC-like compilers regardless of whether .devel is present. Add "include debugging symbols" options for MIPS C/DEC C regardless of whether .devel is present; that's -g3, which is the version that doesn't turn optimization off (we also turn on -O). Also, don't change the ABI on IRIX depending on .devel. I'm not sure why we were doing that; if somebody has a good reason to continue doing it, please let us know what it is. Expand some comments while we're at it.
2013-10-22 01:56:33 +08:00
#
# -g is equivalent to -g2, which turns off
# optimization; we choose -g3, which generates
# debugging information but doesn't turn off
# optimization (even if the optimization would
# cause inaccuracies in debugging).
#
V_CCOPT="$V_CCOPT -g3"
Initial revision
1999-10-08 07:47:09 +08:00
;;
Avoid some warnings from Sun C. Some versions of Sun C support __attribute__ but don't support the "unused" or "format" attributes - they don't fail, but they whine a lot. They also support the "noreturn" attribute, but don't allow it to be applied to function pointers, only to functions. Check whether they can be used without warnings, and use them only if they can.
2013-06-23 05:06:33 +08:00
solaris*)
#
# Assumed to be Sun C, which requires -errwarn to force
# warnings to be treated as errors.
#
ac_lbl_cc_force_warning_errors=-errwarn
;;
Initial revision
1999-10-08 07:47:09 +08:00
ultrix*)
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
{ $as_echo "$as_me:${as_lineno-$LINENO}: checking that Ultrix $CC hacks const in prototypes" >&5
$as_echo_n "checking that Ultrix $CC hacks const in prototypes... " >&6; }
if ${ac_cv_lbl_cc_const_proto+:} false; then :
$as_echo_n "(cached) " >&6
Regenerate with autoconf 2.57.
2004-01-14 11:15:08 +08:00
else
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
cat confdefs.h - <<_ACEOF >conftest.$ac_ext
From Andrew Church <andrew@users.sourceforge.net>: when testing for "pcap_version", "pcap_debug", and "yydebug", don't add our own functions referring to those variables - GCC 3.4.1 optimizes the test code out before the link is done, as it's in a function that's not called.
2004-08-27 15:17:03 +08:00
/* end confdefs.h. */
Initial revision
1999-10-08 07:47:09 +08:00
#include <sys/types.h>
Regenerate with autoconf 2.57.
2004-01-14 11:15:08 +08:00
int
main ()
{
Initial revision
1999-10-08 07:47:09 +08:00
struct a { int b; };
void c(const struct a *)
Regenerate with autoconf 2.57.
2004-01-14 11:15:08 +08:00
;
return 0;
}
_ACEOF
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
if ac_fn_c_try_compile "$LINENO"; then :
Initial revision
1999-10-08 07:47:09 +08:00
ac_cv_lbl_cc_const_proto=yes
else
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
ac_cv_lbl_cc_const_proto=no
Initial revision
1999-10-08 07:47:09 +08:00
fi
We support building tcpdump with versions of libpcap other than the one with which it was released, and DLT_BLUETOOTH_HCI_H4_WITH_PHDR might be defined by pcap-bpf.h without pcap/bluetooth.h being present (as appears to be the case on Fedora 9, for example), so check whether <pcap/bluetooth.h> is usable. Update a comment - F9 appears to have a "/usr/include/pcap.h" if you install the libpcap headers. When adding -I flags when running a compiler-based test, add them to CPPFLAGS, not CFLAGS - the latter doesn't work right with AC_CHECK_HEADERS, as the "gcc -E" run doesn't have the -I flags added.
2008-09-26 05:45:50 +08:00
rm -f core conftest.err conftest.$ac_objext conftest.$ac_ext
Initial revision
1999-10-08 07:47:09 +08:00
fi
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
{ $as_echo "$as_me:${as_lineno-$LINENO}: result: $ac_cv_lbl_cc_const_proto" >&5
$as_echo "$ac_cv_lbl_cc_const_proto" >&6; }
Initial revision
1999-10-08 07:47:09 +08:00
if test $ac_cv_lbl_cc_const_proto = no ; then
Add a comment to the AC_DEFINE call for const, just as we did for libpcap; that eliminates the need to list it in acconfig.h, so get rid of that.
2009-07-03 10:28:34 +08:00
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
$as_echo "#define const /**/" >>confdefs.h
Initial revision
1999-10-08 07:47:09 +08:00
fi
;;
esac
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
V_CCOPT="$V_CCOPT -O"
Initial revision
1999-10-08 07:47:09 +08:00
fi
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
{ $as_echo "$as_me:${as_lineno-$LINENO}: checking for inline" >&5
$as_echo_n "checking for inline... " >&6; }
As with libpcap, so with tcpdump; when testing whether "inline" works, use the V_CCOPT flags, because some of those might disable inlining; otherwise, the test for inlining will succeed, but inlining won't work with the options we're using when compiling.
2009-07-03 02:55:55 +08:00
save_CFLAGS="$CFLAGS"
CFLAGS="$V_CCOPT"
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
if ${ac_cv_lbl_inline+:} false; then :
$as_echo_n "(cached) " >&6
Check for ether_ntohost, not ether_ntoa, since the former is what tcpdump actually wants to use. Now ethernet number -> name translation works.
1999-11-22 12:23:34 +08:00
else
Put back AC_LBL_C_INLINE; it turns out that wasn't the cause of the inline problem, and AC_LBL_C_INLINE checks for a case that some versions of the HP C compiler don't handle, and only uses inline if that case succeeds.
2005-04-21 10:21:47 +08:00
ac_cv_lbl_inline=""
ac_lbl_cc_inline=no
for ac_lbl_inline in inline __inline__ __inline
do
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
cat confdefs.h - <<_ACEOF >conftest.$ac_ext
From Andrew Church <andrew@users.sourceforge.net>: when testing for "pcap_version", "pcap_debug", and "yydebug", don't add our own functions referring to those variables - GCC 3.4.1 optimizes the test code out before the link is done, as it's in a function that's not called.
2004-08-27 15:17:03 +08:00
/* end confdefs.h. */
Put back AC_LBL_C_INLINE; it turns out that wasn't the cause of the inline problem, and AC_LBL_C_INLINE checks for a case that some versions of the HP C compiler don't handle, and only uses inline if that case succeeds.
2005-04-21 10:21:47 +08:00
#define inline $ac_lbl_inline
static inline struct iltest *foo(void);
struct iltest {
int iltest1;
int iltest2;
};
static inline struct iltest *
foo()
{
static struct iltest xxx;
return &xxx;
}
int
main ()
{
Fix up AC_LBL_C_INLINE to put all of the test code into the "inlines" section - the other section gets stuck in the middle of "main()", and, although GCC lets you define functions inside functions, other C compilers don't. Pick a name more likely to be unique to use as the iterator variable in AC_LBL_C_INLINE. Make AC_LBL_C_INLINE print "no" rather than "not supported" if inline isn't supported, to match what AC_C_INLINE does.
2002-07-02 10:22:36 +08:00
Put back AC_LBL_C_INLINE; it turns out that wasn't the cause of the inline problem, and AC_LBL_C_INLINE checks for a case that some versions of the HP C compiler don't handle, and only uses inline if that case succeeds.
2005-04-21 10:21:47 +08:00
;
return 0;
}
Regenerate with autoconf 2.57.
2004-01-14 11:15:08 +08:00
_ACEOF
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
if ac_fn_c_try_compile "$LINENO"; then :
Put back AC_LBL_C_INLINE; it turns out that wasn't the cause of the inline problem, and AC_LBL_C_INLINE checks for a case that some versions of the HP C compiler don't handle, and only uses inline if that case succeeds.
2005-04-21 10:21:47 +08:00
ac_lbl_cc_inline=yes
Check for ether_ntohost, not ether_ntoa, since the former is what tcpdump actually wants to use. Now ethernet number -> name translation works.
1999-11-22 12:23:34 +08:00
fi
We support building tcpdump with versions of libpcap other than the one with which it was released, and DLT_BLUETOOTH_HCI_H4_WITH_PHDR might be defined by pcap-bpf.h without pcap/bluetooth.h being present (as appears to be the case on Fedora 9, for example), so check whether <pcap/bluetooth.h> is usable. Update a comment - F9 appears to have a "/usr/include/pcap.h" if you install the libpcap headers. When adding -I flags when running a compiler-based test, add them to CPPFLAGS, not CFLAGS - the latter doesn't work right with AC_CHECK_HEADERS, as the "gcc -E" run doesn't have the -I flags added.
2008-09-26 05:45:50 +08:00
rm -f core conftest.err conftest.$ac_objext conftest.$ac_ext
Put back AC_LBL_C_INLINE; it turns out that wasn't the cause of the inline problem, and AC_LBL_C_INLINE checks for a case that some versions of the HP C compiler don't handle, and only uses inline if that case succeeds.
2005-04-21 10:21:47 +08:00
if test "$ac_lbl_cc_inline" = yes ; then
break;
fi
done
if test "$ac_lbl_cc_inline" = yes ; then
ac_cv_lbl_inline=$ac_lbl_inline
fi
From Albert Chin: 1. On AIX, AC_LBL_C_INLINE detected the compiler supported the inline keyword which is wrong. AC_C_INLINE from autoconf-2.59 worked. 2. AC_CHECK_TYPE from autoconf-2.5x is no longer broken. Replaced AC_LBL_CHECK_TYPE with it, mainly to use <sys/bitypes.h> for Tru64 UNIX where some of the u_int#_t types are defined. 3. Tru64 UNIX 4.0D doesn't support %llx; however, it does support %lx. 4. Added <stdint.h> to interface.h for int#_t types on Tru64 UNIX 4.0D (required for missing/snprintf.c). 5. Reworked includes in tcpdump-stdinc.h for int#_t types.
2005-04-20 17:44:30 +08:00
fi
Put back AC_LBL_C_INLINE; it turns out that wasn't the cause of the inline problem, and AC_LBL_C_INLINE checks for a case that some versions of the HP C compiler don't handle, and only uses inline if that case succeeds.
2005-04-21 10:21:47 +08:00
As with libpcap, so with tcpdump; when testing whether "inline" works, use the V_CCOPT flags, because some of those might disable inlining; otherwise, the test for inlining will succeed, but inlining won't work with the options we're using when compiling.
2009-07-03 02:55:55 +08:00
CFLAGS="$save_CFLAGS"
Put back AC_LBL_C_INLINE; it turns out that wasn't the cause of the inline problem, and AC_LBL_C_INLINE checks for a case that some versions of the HP C compiler don't handle, and only uses inline if that case succeeds.
2005-04-21 10:21:47 +08:00
if test ! -z "$ac_cv_lbl_inline" ; then
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
{ $as_echo "$as_me:${as_lineno-$LINENO}: result: $ac_cv_lbl_inline" >&5
$as_echo "$ac_cv_lbl_inline" >&6; }
Put back AC_LBL_C_INLINE; it turns out that wasn't the cause of the inline problem, and AC_LBL_C_INLINE checks for a case that some versions of the HP C compiler don't handle, and only uses inline if that case succeeds.
2005-04-21 10:21:47 +08:00
else
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
{ $as_echo "$as_me:${as_lineno-$LINENO}: result: no" >&5
$as_echo "no" >&6; }
Put back AC_LBL_C_INLINE; it turns out that wasn't the cause of the inline problem, and AC_LBL_C_INLINE checks for a case that some versions of the HP C compiler don't handle, and only uses inline if that case succeeds.
2005-04-21 10:21:47 +08:00
fi
cat >>confdefs.h <<_ACEOF
#define inline $ac_cv_lbl_inline
From Albert Chin: 1. On AIX, AC_LBL_C_INLINE detected the compiler supported the inline keyword which is wrong. AC_C_INLINE from autoconf-2.59 worked. 2. AC_CHECK_TYPE from autoconf-2.5x is no longer broken. Replaced AC_LBL_CHECK_TYPE with it, mainly to use <sys/bitypes.h> for Tru64 UNIX where some of the u_int#_t types are defined. 3. Tru64 UNIX 4.0D doesn't support %llx; however, it does support %lx. 4. Added <stdint.h> to interface.h for int#_t types on Tru64 UNIX 4.0D (required for missing/snprintf.c). 5. Reworked includes in tcpdump-stdinc.h for int#_t types.
2005-04-20 17:44:30 +08:00
_ACEOF
Initial revision
1999-10-08 07:47:09 +08:00
From Andrew Church <andrew@users.sourceforge.net>: when testing for "pcap_version", "pcap_debug", and "yydebug", don't add our own functions referring to those variables - GCC 3.4.1 optimizes the test code out before the link is done, as it's in a function that's not called.
2004-08-27 15:17:03 +08:00
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
{ $as_echo "$as_me:${as_lineno-$LINENO}: checking for __attribute__" >&5
$as_echo_n "checking for __attribute__... " >&6; }
if ${ac_cv___attribute__+:} false; then :
$as_echo_n "(cached) " >&6
regen
2000-04-01 20:26:12 +08:00
else
Regenerate with autoconf 2.57.
2004-01-14 11:15:08 +08:00
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
cat confdefs.h - <<_ACEOF >conftest.$ac_ext
Check for extra networking libraries before checking for IPv6. On some platforms, such as SunOS 5.x, building the "do we have IPv6 support?" test program requires the extra networking libraries, so we need to know what extra networking libraries are required before doing that test.
2013-04-07 04:03:58 +08:00
/* end confdefs.h. */
Simplify the detection of OpenSSL libcrypto by using standard autoconf macros rather than a local copy of AC_LBL_SSLEAY. AC_LBL_SSLEAY is old and has not kept pace with some more recent developments in packaging like Debian and Ubuntu's multiarch support. The autoconf macros have been updated to handle multiarch so using them means that tcpdump gains the ability to be built with libcrypto on these new multiarch distros and to work successfully with Travis CI, which uses Ubuntu 12, which is one such multiarch distro (see GH-32). Fixes GH-33
2012-10-14 02:21:45 +08:00
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
regen
2000-04-01 20:26:12 +08:00
#include <stdlib.h>
static void foo(void) __attribute__ ((noreturn));
static void
foo(void)
{
exit(1);
}
AC_TRY_COMPILE works only for code that fits inside "main()"; the test for __attribute__ doesn't fit inside "main()" with GCC 4.0, as it defines a function.
2005-04-21 11:50:29 +08:00
int
main(int argc, char **argv)
{
foo();
Regenerate with autoconf 2.57.
2004-01-14 11:15:08 +08:00
}
AC_TRY_COMPILE works only for code that fits inside "main()"; the test for __attribute__ doesn't fit inside "main()" with GCC 4.0, as it defines a function.
2005-04-21 11:50:29 +08:00
Regenerate with autoconf 2.57.
2004-01-14 11:15:08 +08:00
_ACEOF
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
if ac_fn_c_try_compile "$LINENO"; then :
regen
2000-04-01 20:26:12 +08:00
ac_cv___attribute__=yes
else
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
ac_cv___attribute__=no
regen
2000-04-01 20:26:12 +08:00
fi
We support building tcpdump with versions of libpcap other than the one with which it was released, and DLT_BLUETOOTH_HCI_H4_WITH_PHDR might be defined by pcap-bpf.h without pcap/bluetooth.h being present (as appears to be the case on Fedora 9, for example), so check whether <pcap/bluetooth.h> is usable. Update a comment - F9 appears to have a "/usr/include/pcap.h" if you install the libpcap headers. When adding -I flags when running a compiler-based test, add them to CPPFLAGS, not CFLAGS - the latter doesn't work right with AC_CHECK_HEADERS, as the "gcc -E" run doesn't have the -I flags added.
2008-09-26 05:45:50 +08:00
rm -f core conftest.err conftest.$ac_objext conftest.$ac_ext
regen
2000-04-01 20:26:12 +08:00
fi
if test "$ac_cv___attribute__" = "yes"; then
Regenerate with autoconf 2.57.
2004-01-14 11:15:08 +08:00
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
$as_echo "#define HAVE___ATTRIBUTE__ 1" >>confdefs.h
regen
2000-04-01 20:26:12 +08:00
Have the configure script arrange that the Makefile define _U_ appropriately, and that GNUmakefile and the MSVC++ project file define it apppriately, as we do with libpcap, rather than defining it in "interface.h". Undo the rcsid-shuffling and addition of extra #includes, as we no longer need to arrange that "interface.h" be included before using _U_ in an RCS ID or copyright.
2003-11-16 17:42:39 +08:00
else
Avoid some warnings from Sun C. Some versions of Sun C support __attribute__ but don't support the "unused" or "format" attributes - they don't fail, but they whine a lot. They also support the "noreturn" attribute, but don't allow it to be applied to function pointers, only to functions. Check whether they can be used without warnings, and use them only if they can.
2013-06-23 05:06:33 +08:00
#
# We can't use __attribute__, so we can't use __attribute__((unused)),
# so we define _U_ to an empty string.
#
Have the configure script arrange that the Makefile define _U_ appropriately, and that GNUmakefile and the MSVC++ project file define it apppriately, as we do with libpcap, rather than defining it in "interface.h". Undo the rcsid-shuffling and addition of extra #includes, as we no longer need to arrange that "interface.h" be included before using _U_ in an RCS ID or copyright.
2003-11-16 17:42:39 +08:00
V_DEFS="$V_DEFS -D_U_=\"\""
regen
2000-04-01 20:26:12 +08:00
fi
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
{ $as_echo "$as_me:${as_lineno-$LINENO}: result: $ac_cv___attribute__" >&5
$as_echo "$ac_cv___attribute__" >&6; }
regen
2000-04-01 20:26:12 +08:00
Get rid of some autoconf macros not used, or no longer used, with tcpdump. Check whether __attribute__((format)) can be applied to function pointers and, if not, don't apply it to function pointers; some older versions of GCC appear to support applying it to functions, but not pointers to functions. As we've gotten rid of missing/getaddrinfo.c, don't use it.
2009-07-08 16:22:27 +08:00
if test "$ac_cv___attribute__" = "yes"; then
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
{ $as_echo "$as_me:${as_lineno-$LINENO}: checking whether __attribute__((unused)) can be used without warnings" >&5
$as_echo_n "checking whether __attribute__((unused)) can be used without warnings... " >&6; }
if ${ac_cv___attribute___unused+:} false; then :
$as_echo_n "(cached) " >&6
Avoid some warnings from Sun C. Some versions of Sun C support __attribute__ but don't support the "unused" or "format" attributes - they don't fail, but they whine a lot. They also support the "noreturn" attribute, but don't allow it to be applied to function pointers, only to functions. Check whether they can be used without warnings, and use them only if they can.
2013-06-23 05:06:33 +08:00
else
save_CFLAGS="$CFLAGS"
CFLAGS="$CFLAGS $ac_lbl_cc_force_warning_errors"
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
cat confdefs.h - <<_ACEOF >conftest.$ac_ext
Avoid some warnings from Sun C. Some versions of Sun C support __attribute__ but don't support the "unused" or "format" attributes - they don't fail, but they whine a lot. They also support the "noreturn" attribute, but don't allow it to be applied to function pointers, only to functions. Check whether they can be used without warnings, and use them only if they can.
2013-06-23 05:06:33 +08:00
/* end confdefs.h. */
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
Avoid some warnings from Sun C. Some versions of Sun C support __attribute__ but don't support the "unused" or "format" attributes - they don't fail, but they whine a lot. They also support the "noreturn" attribute, but don't allow it to be applied to function pointers, only to functions. Check whether they can be used without warnings, and use them only if they can.
2013-06-23 05:06:33 +08:00
#include <stdlib.h>
#include <stdio.h>
int
main(int argc __attribute((unused)), char **argv __attribute((unused)))
{
printf("Hello, world!\n");
return 0;
}
_ACEOF
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
if ac_fn_c_try_compile "$LINENO"; then :
Avoid some warnings from Sun C. Some versions of Sun C support __attribute__ but don't support the "unused" or "format" attributes - they don't fail, but they whine a lot. They also support the "noreturn" attribute, but don't allow it to be applied to function pointers, only to functions. Check whether they can be used without warnings, and use them only if they can.
2013-06-23 05:06:33 +08:00
ac_cv___attribute___unused=yes
else
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
ac_cv___attribute___unused=no
Avoid some warnings from Sun C. Some versions of Sun C support __attribute__ but don't support the "unused" or "format" attributes - they don't fail, but they whine a lot. They also support the "noreturn" attribute, but don't allow it to be applied to function pointers, only to functions. Check whether they can be used without warnings, and use them only if they can.
2013-06-23 05:06:33 +08:00
fi
rm -f core conftest.err conftest.$ac_objext conftest.$ac_ext
fi
CFLAGS="$save_CFLAGS"
if test "$ac_cv___attribute___unused" = "yes"; then
V_DEFS="$V_DEFS -D_U_=\"__attribute__((unused))\""
else
V_DEFS="$V_DEFS -D_U_=\"\""
fi
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
{ $as_echo "$as_me:${as_lineno-$LINENO}: result: $ac_cv___attribute___unused" >&5
$as_echo "$ac_cv___attribute___unused" >&6; }
Avoid some warnings from Sun C. Some versions of Sun C support __attribute__ but don't support the "unused" or "format" attributes - they don't fail, but they whine a lot. They also support the "noreturn" attribute, but don't allow it to be applied to function pointers, only to functions. Check whether they can be used without warnings, and use them only if they can.
2013-06-23 05:06:33 +08:00
Check for __attribute__ ((fallthrough)) (GCC 7). The documentation claims that recent GCC is now better by default at spotting cases of code flow falling through (which is true) and that it avoids false positives by matching nearby source code comments with regexps. However, the latter feature doesn't seem to work as reliably as the manual describes it, so let's have a macro for this purpose. Tested to work on: * x86_64, Fedora 26, GCC 7.1.1 (w/__attribute__, w/fallthrough) * x86_64, Ubuntu 16.04, GCC 5.4.0 (w/__attribute__, w/o fallthrough) * x86_64, FreeBSD 11.0, CLang 3.8.0 (w/__attribute__, w/o fallthrough) * SPARC, Solaris 10, SolStudio 12.4 (w/__attribute__, w/o fallthrough) * SPARC, Solaris 10, SunStudio 11 (w/o __attribute__)
2017-07-22 05:04:15 +08:00
{ $as_echo "$as_me:${as_lineno-$LINENO}: checking whether __attribute__((fallthrough)) can be used without warnings" >&5
$as_echo_n "checking whether __attribute__((fallthrough)) can be used without warnings... " >&6; }
if ${ac_cv___attribute___fallthrough+:} false; then :
$as_echo_n "(cached) " >&6
else
save_CFLAGS="$CFLAGS"
CFLAGS="$CFLAGS $ac_lbl_cc_force_warning_errors"
cat confdefs.h - <<_ACEOF >conftest.$ac_ext
/* end confdefs.h. */
#include <stdio.h>
int
main(int argc, char **argv)
{
int x = 1;
switch (x)
{
case 1:
printf ("x == %d\n", x);
__attribute__ ((fallthrough));
case 2:
printf ("x == %d\n", x);
break;
default:
return 0;
}
return x;
}
_ACEOF
if ac_fn_c_try_compile "$LINENO"; then :
ac_cv___attribute___fallthrough=yes
else
ac_cv___attribute___fallthrough=no
fi
rm -f core conftest.err conftest.$ac_objext conftest.$ac_ext
fi
CFLAGS="$save_CFLAGS"
if test "$ac_cv___attribute___fallthrough" = "yes"; then
$as_echo "#define __ATTRIBUTE___FALLTHROUGH_OK 1" >>confdefs.h
fi
{ $as_echo "$as_me:${as_lineno-$LINENO}: result: $ac_cv___attribute___fallthrough" >&5
$as_echo "$ac_cv___attribute___fallthrough" >&6; }
Get rid of some autoconf macros not used, or no longer used, with tcpdump. Check whether __attribute__((format)) can be applied to function pointers and, if not, don't apply it to function pointers; some older versions of GCC appear to support applying it to functions, but not pointers to functions. As we've gotten rid of missing/getaddrinfo.c, don't use it.
2009-07-08 16:22:27 +08:00
fi
Use getopt_long(). This requires us to check for it in the configure script and to include a version of getopt_long() for the benefit of platforms that don't have it; we pick up the FreeBSD version and tweak it a bit (eliminating some features specific to the BSD version of getopt_long(), as we want to use it only in a fashion portable to Linux/*BSD/Solaris/etc.) We also get rid of the version of getopt() we supply for Windows in favor of the version of getopt_long() we provide.
2014-05-01 06:28:06 +08:00
Regenerate with autoconf 2.57.
2004-01-14 11:15:08 +08:00
ac_ext=c
ac_cpp='$CPP $CPPFLAGS'
ac_compile='$CC -c $CFLAGS $CPPFLAGS conftest.$ac_ext >&5'
ac_link='$CC -o conftest$ac_exeext $CFLAGS $CPPFLAGS $LDFLAGS conftest.$ac_ext $LIBS >&5'
ac_compiler_gnu=$ac_cv_c_compiler_gnu
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
{ $as_echo "$as_me:${as_lineno-$LINENO}: checking how to run the C preprocessor" >&5
$as_echo_n "checking how to run the C preprocessor... " >&6; }
Initial revision
1999-10-08 07:47:09 +08:00
# On Suns, sometimes $CPP names a directory.
if test -n "$CPP" && test -d "$CPP"; then
CPP=
fi
if test -z "$CPP"; then
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
if ${ac_cv_prog_CPP+:} false; then :
$as_echo_n "(cached) " >&6
Regenerate with autoconf 2.57.
2004-01-14 11:15:08 +08:00
else
# Double quotes because CPP needs to be expanded
for CPP in "$CC -E" "$CC -E -traditional-cpp" "/lib/cpp"
do
ac_preproc_ok=false
for ac_c_preproc_warn_flag in '' yes
do
# Use a header file that comes with gcc, so configuring glibc
# with a fresh cross-compiler works.
From Andrew Church <andrew@users.sourceforge.net>: when testing for "pcap_version", "pcap_debug", and "yydebug", don't add our own functions referring to those variables - GCC 3.4.1 optimizes the test code out before the link is done, as it's in a function that's not called.
2004-08-27 15:17:03 +08:00
# Prefer <limits.h> to <assert.h> if __STDC__ is defined, since
# <limits.h> exists even on freestanding compilers.
Regenerate with autoconf 2.57.
2004-01-14 11:15:08 +08:00
# On the NeXT, cc -E runs the code through the compiler's parser,
# not just through cpp. "Syntax error" is here to catch this case.
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
cat confdefs.h - <<_ACEOF >conftest.$ac_ext
From Andrew Church <andrew@users.sourceforge.net>: when testing for "pcap_version", "pcap_debug", and "yydebug", don't add our own functions referring to those variables - GCC 3.4.1 optimizes the test code out before the link is done, as it's in a function that's not called.
2004-08-27 15:17:03 +08:00
/* end confdefs.h. */
#ifdef __STDC__
# include <limits.h>
#else
# include <assert.h>
#endif
Add -Wpointer-arith to the list of warnings we enable with GCC.
2005-11-08 10:59:40 +08:00
Syntax error
Regenerate with autoconf 2.57.
2004-01-14 11:15:08 +08:00
_ACEOF
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
if ac_fn_c_try_cpp "$LINENO"; then :
Check for extra networking libraries before checking for IPv6. On some platforms, such as SunOS 5.x, building the "do we have IPv6 support?" test program requires the extra networking libraries, so we need to know what extra networking libraries are required before doing that test.
2013-04-07 04:03:58 +08:00
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
else
Regenerate with autoconf 2.57.
2004-01-14 11:15:08 +08:00
# Broken: fails on valid input.
continue
fi
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
rm -f conftest.err conftest.i conftest.$ac_ext
Regenerate with autoconf 2.57.
2004-01-14 11:15:08 +08:00
We support building tcpdump with versions of libpcap other than the one with which it was released, and DLT_BLUETOOTH_HCI_H4_WITH_PHDR might be defined by pcap-bpf.h without pcap/bluetooth.h being present (as appears to be the case on Fedora 9, for example), so check whether <pcap/bluetooth.h> is usable. Update a comment - F9 appears to have a "/usr/include/pcap.h" if you install the libpcap headers. When adding -I flags when running a compiler-based test, add them to CPPFLAGS, not CFLAGS - the latter doesn't work right with AC_CHECK_HEADERS, as the "gcc -E" run doesn't have the -I flags added.
2008-09-26 05:45:50 +08:00
# OK, works on sane cases. Now check whether nonexistent headers
Regenerate with autoconf 2.57.
2004-01-14 11:15:08 +08:00
# can be detected and how.
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
cat confdefs.h - <<_ACEOF >conftest.$ac_ext
From Andrew Church <andrew@users.sourceforge.net>: when testing for "pcap_version", "pcap_debug", and "yydebug", don't add our own functions referring to those variables - GCC 3.4.1 optimizes the test code out before the link is done, as it's in a function that's not called.
2004-08-27 15:17:03 +08:00
/* end confdefs.h. */
Regenerate with autoconf 2.57.
2004-01-14 11:15:08 +08:00
#include <ac_nonexistent.h>
_ACEOF
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
if ac_fn_c_try_cpp "$LINENO"; then :
Regenerate with autoconf 2.57.
2004-01-14 11:15:08 +08:00
# Broken: success on invalid input.
continue
else
# Passes both tests.
ac_preproc_ok=:
break
fi
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
rm -f conftest.err conftest.i conftest.$ac_ext
Regenerate with autoconf 2.57.
2004-01-14 11:15:08 +08:00
done
# Because of `break', _AC_PREPROC_IFELSE's cleaning code was skipped.
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
rm -f conftest.i conftest.err conftest.$ac_ext
if $ac_preproc_ok; then :
Regenerate with autoconf 2.57.
2004-01-14 11:15:08 +08:00
break
fi
done
ac_cv_prog_CPP=$CPP
fi
CPP=$ac_cv_prog_CPP
Initial revision
1999-10-08 07:47:09 +08:00
else
Regenerate with autoconf 2.57.
2004-01-14 11:15:08 +08:00
ac_cv_prog_CPP=$CPP
fi
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
{ $as_echo "$as_me:${as_lineno-$LINENO}: result: $CPP" >&5
$as_echo "$CPP" >&6; }
Regenerate with autoconf 2.57.
2004-01-14 11:15:08 +08:00
ac_preproc_ok=false
for ac_c_preproc_warn_flag in '' yes
do
# Use a header file that comes with gcc, so configuring glibc
# with a fresh cross-compiler works.
From Andrew Church <andrew@users.sourceforge.net>: when testing for "pcap_version", "pcap_debug", and "yydebug", don't add our own functions referring to those variables - GCC 3.4.1 optimizes the test code out before the link is done, as it's in a function that's not called.
2004-08-27 15:17:03 +08:00
# Prefer <limits.h> to <assert.h> if __STDC__ is defined, since
# <limits.h> exists even on freestanding compilers.
Initial revision
1999-10-08 07:47:09 +08:00
# On the NeXT, cc -E runs the code through the compiler's parser,
Regenerate with autoconf 2.57.
2004-01-14 11:15:08 +08:00
# not just through cpp. "Syntax error" is here to catch this case.
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
cat confdefs.h - <<_ACEOF >conftest.$ac_ext
From Andrew Church <andrew@users.sourceforge.net>: when testing for "pcap_version", "pcap_debug", and "yydebug", don't add our own functions referring to those variables - GCC 3.4.1 optimizes the test code out before the link is done, as it's in a function that's not called.
2004-08-27 15:17:03 +08:00
/* end confdefs.h. */
#ifdef __STDC__
# include <limits.h>
#else
# include <assert.h>
#endif
Add -Wpointer-arith to the list of warnings we enable with GCC.
2005-11-08 10:59:40 +08:00
Syntax error
Regenerate with autoconf 2.57.
2004-01-14 11:15:08 +08:00
_ACEOF
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
if ac_fn_c_try_cpp "$LINENO"; then :
Check for extra networking libraries before checking for IPv6. On some platforms, such as SunOS 5.x, building the "do we have IPv6 support?" test program requires the extra networking libraries, so we need to know what extra networking libraries are required before doing that test.
2013-04-07 04:03:58 +08:00
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
else
Regenerate with autoconf 2.57.
2004-01-14 11:15:08 +08:00
# Broken: fails on valid input.
continue
fi
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
rm -f conftest.err conftest.i conftest.$ac_ext
Regenerate with autoconf 2.57.
2004-01-14 11:15:08 +08:00
We support building tcpdump with versions of libpcap other than the one with which it was released, and DLT_BLUETOOTH_HCI_H4_WITH_PHDR might be defined by pcap-bpf.h without pcap/bluetooth.h being present (as appears to be the case on Fedora 9, for example), so check whether <pcap/bluetooth.h> is usable. Update a comment - F9 appears to have a "/usr/include/pcap.h" if you install the libpcap headers. When adding -I flags when running a compiler-based test, add them to CPPFLAGS, not CFLAGS - the latter doesn't work right with AC_CHECK_HEADERS, as the "gcc -E" run doesn't have the -I flags added.
2008-09-26 05:45:50 +08:00
# OK, works on sane cases. Now check whether nonexistent headers
Regenerate with autoconf 2.57.
2004-01-14 11:15:08 +08:00
# can be detected and how.
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
cat confdefs.h - <<_ACEOF >conftest.$ac_ext
From Andrew Church <andrew@users.sourceforge.net>: when testing for "pcap_version", "pcap_debug", and "yydebug", don't add our own functions referring to those variables - GCC 3.4.1 optimizes the test code out before the link is done, as it's in a function that's not called.
2004-08-27 15:17:03 +08:00
/* end confdefs.h. */
Regenerate with autoconf 2.57.
2004-01-14 11:15:08 +08:00
#include <ac_nonexistent.h>
_ACEOF
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
if ac_fn_c_try_cpp "$LINENO"; then :
Regenerate with autoconf 2.57.
2004-01-14 11:15:08 +08:00
# Broken: success on invalid input.
continue
else
# Passes both tests.
ac_preproc_ok=:
break
fi
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
rm -f conftest.err conftest.i conftest.$ac_ext
Regenerate with autoconf 2.57.
2004-01-14 11:15:08 +08:00
done
# Because of `break', _AC_PREPROC_IFELSE's cleaning code was skipped.
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
rm -f conftest.i conftest.err conftest.$ac_ext
if $ac_preproc_ok; then :
Bring in KAME IPv6 tcpdump. replaces esp/ah/isakmp decoder. Hope I did not break anything. Portability on IPv4-only node needs checking, I'll do this very soon. (sorry for rather jumbo commit) XXx what is _FAVOR_BSD?
1999-10-30 13:11:06 +08:00
else
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
{ { $as_echo "$as_me:${as_lineno-$LINENO}: error: in \`$ac_pwd':" >&5
$as_echo "$as_me: error: in \`$ac_pwd':" >&2;}
as_fn_error $? "C preprocessor \"$CPP\" fails sanity check
See \`config.log' for more details" "$LINENO" 5; }
Regenerate with autoconf 2.57.
2004-01-14 11:15:08 +08:00
fi
ac_ext=c
ac_cpp='$CPP $CPPFLAGS'
ac_compile='$CC -c $CFLAGS $CPPFLAGS conftest.$ac_ext >&5'
ac_link='$CC -o conftest$ac_exeext $CFLAGS $CPPFLAGS $LDFLAGS conftest.$ac_ext $LIBS >&5'
ac_compiler_gnu=$ac_cv_c_compiler_gnu
From Andrew Church <andrew@users.sourceforge.net>: when testing for "pcap_version", "pcap_debug", and "yydebug", don't add our own functions referring to those variables - GCC 3.4.1 optimizes the test code out before the link is done, as it's in a function that's not called.
2004-08-27 15:17:03 +08:00
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
{ $as_echo "$as_me:${as_lineno-$LINENO}: checking for grep that handles long lines and -e" >&5
$as_echo_n "checking for grep that handles long lines and -e... " >&6; }
if ${ac_cv_path_GREP+:} false; then :
$as_echo_n "(cached) " >&6
We support building tcpdump with versions of libpcap other than the one with which it was released, and DLT_BLUETOOTH_HCI_H4_WITH_PHDR might be defined by pcap-bpf.h without pcap/bluetooth.h being present (as appears to be the case on Fedora 9, for example), so check whether <pcap/bluetooth.h> is usable. Update a comment - F9 appears to have a "/usr/include/pcap.h" if you install the libpcap headers. When adding -I flags when running a compiler-based test, add them to CPPFLAGS, not CFLAGS - the latter doesn't work right with AC_CHECK_HEADERS, as the "gcc -E" run doesn't have the -I flags added.
2008-09-26 05:45:50 +08:00
else
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
if test -z "$GREP"; then
We support building tcpdump with versions of libpcap other than the one with which it was released, and DLT_BLUETOOTH_HCI_H4_WITH_PHDR might be defined by pcap-bpf.h without pcap/bluetooth.h being present (as appears to be the case on Fedora 9, for example), so check whether <pcap/bluetooth.h> is usable. Update a comment - F9 appears to have a "/usr/include/pcap.h" if you install the libpcap headers. When adding -I flags when running a compiler-based test, add them to CPPFLAGS, not CFLAGS - the latter doesn't work right with AC_CHECK_HEADERS, as the "gcc -E" run doesn't have the -I flags added.
2008-09-26 05:45:50 +08:00
ac_path_GREP_found=false
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
# Loop through the user's path and test for each of PROGNAME-LIST
as_save_IFS=$IFS; IFS=$PATH_SEPARATOR
We support building tcpdump with versions of libpcap other than the one with which it was released, and DLT_BLUETOOTH_HCI_H4_WITH_PHDR might be defined by pcap-bpf.h without pcap/bluetooth.h being present (as appears to be the case on Fedora 9, for example), so check whether <pcap/bluetooth.h> is usable. Update a comment - F9 appears to have a "/usr/include/pcap.h" if you install the libpcap headers. When adding -I flags when running a compiler-based test, add them to CPPFLAGS, not CFLAGS - the latter doesn't work right with AC_CHECK_HEADERS, as the "gcc -E" run doesn't have the -I flags added.
2008-09-26 05:45:50 +08:00
for as_dir in $PATH$PATH_SEPARATOR/usr/xpg4/bin
do
IFS=$as_save_IFS
test -z "$as_dir" && as_dir=.
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
for ac_prog in grep ggrep; do
for ac_exec_ext in '' $ac_executable_extensions; do
ac_path_GREP="$as_dir/$ac_prog$ac_exec_ext"
as_fn_executable_p "$ac_path_GREP" || continue
# Check for GNU ac_path_GREP and select it if it is found.
We support building tcpdump with versions of libpcap other than the one with which it was released, and DLT_BLUETOOTH_HCI_H4_WITH_PHDR might be defined by pcap-bpf.h without pcap/bluetooth.h being present (as appears to be the case on Fedora 9, for example), so check whether <pcap/bluetooth.h> is usable. Update a comment - F9 appears to have a "/usr/include/pcap.h" if you install the libpcap headers. When adding -I flags when running a compiler-based test, add them to CPPFLAGS, not CFLAGS - the latter doesn't work right with AC_CHECK_HEADERS, as the "gcc -E" run doesn't have the -I flags added.
2008-09-26 05:45:50 +08:00
# Check for GNU $ac_path_GREP
case `"$ac_path_GREP" --version 2>&1` in
*GNU*)
ac_cv_path_GREP="$ac_path_GREP" ac_path_GREP_found=:;;
*)
ac_count=0
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
$as_echo_n 0123456789 >"conftest.in"
We support building tcpdump with versions of libpcap other than the one with which it was released, and DLT_BLUETOOTH_HCI_H4_WITH_PHDR might be defined by pcap-bpf.h without pcap/bluetooth.h being present (as appears to be the case on Fedora 9, for example), so check whether <pcap/bluetooth.h> is usable. Update a comment - F9 appears to have a "/usr/include/pcap.h" if you install the libpcap headers. When adding -I flags when running a compiler-based test, add them to CPPFLAGS, not CFLAGS - the latter doesn't work right with AC_CHECK_HEADERS, as the "gcc -E" run doesn't have the -I flags added.
2008-09-26 05:45:50 +08:00
while :
do
cat "conftest.in" "conftest.in" >"conftest.tmp"
mv "conftest.tmp" "conftest.in"
cp "conftest.in" "conftest.nl"
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
$as_echo 'GREP' >> "conftest.nl"
We support building tcpdump with versions of libpcap other than the one with which it was released, and DLT_BLUETOOTH_HCI_H4_WITH_PHDR might be defined by pcap-bpf.h without pcap/bluetooth.h being present (as appears to be the case on Fedora 9, for example), so check whether <pcap/bluetooth.h> is usable. Update a comment - F9 appears to have a "/usr/include/pcap.h" if you install the libpcap headers. When adding -I flags when running a compiler-based test, add them to CPPFLAGS, not CFLAGS - the latter doesn't work right with AC_CHECK_HEADERS, as the "gcc -E" run doesn't have the -I flags added.
2008-09-26 05:45:50 +08:00
"$ac_path_GREP" -e 'GREP$' -e '-(cannot match)-' < "conftest.nl" >"conftest.out" 2>/dev/null || break
diff "conftest.out" "conftest.nl" >/dev/null 2>&1 || break
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
as_fn_arith $ac_count + 1 && ac_count=$as_val
We support building tcpdump with versions of libpcap other than the one with which it was released, and DLT_BLUETOOTH_HCI_H4_WITH_PHDR might be defined by pcap-bpf.h without pcap/bluetooth.h being present (as appears to be the case on Fedora 9, for example), so check whether <pcap/bluetooth.h> is usable. Update a comment - F9 appears to have a "/usr/include/pcap.h" if you install the libpcap headers. When adding -I flags when running a compiler-based test, add them to CPPFLAGS, not CFLAGS - the latter doesn't work right with AC_CHECK_HEADERS, as the "gcc -E" run doesn't have the -I flags added.
2008-09-26 05:45:50 +08:00
if test $ac_count -gt ${ac_path_GREP_max-0}; then
# Best one so far, save it but keep looking for a better one
ac_cv_path_GREP="$ac_path_GREP"
ac_path_GREP_max=$ac_count
fi
# 10*(2^10) chars as input seems more than enough
test $ac_count -gt 10 && break
done
rm -f conftest.in conftest.tmp conftest.nl conftest.out;;
esac
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
$ac_path_GREP_found && break 3
done
done
We support building tcpdump with versions of libpcap other than the one with which it was released, and DLT_BLUETOOTH_HCI_H4_WITH_PHDR might be defined by pcap-bpf.h without pcap/bluetooth.h being present (as appears to be the case on Fedora 9, for example), so check whether <pcap/bluetooth.h> is usable. Update a comment - F9 appears to have a "/usr/include/pcap.h" if you install the libpcap headers. When adding -I flags when running a compiler-based test, add them to CPPFLAGS, not CFLAGS - the latter doesn't work right with AC_CHECK_HEADERS, as the "gcc -E" run doesn't have the -I flags added.
2008-09-26 05:45:50 +08:00
done
IFS=$as_save_IFS
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
if test -z "$ac_cv_path_GREP"; then
as_fn_error $? "no acceptable grep could be found in $PATH$PATH_SEPARATOR/usr/xpg4/bin" "$LINENO" 5
fi
We support building tcpdump with versions of libpcap other than the one with which it was released, and DLT_BLUETOOTH_HCI_H4_WITH_PHDR might be defined by pcap-bpf.h without pcap/bluetooth.h being present (as appears to be the case on Fedora 9, for example), so check whether <pcap/bluetooth.h> is usable. Update a comment - F9 appears to have a "/usr/include/pcap.h" if you install the libpcap headers. When adding -I flags when running a compiler-based test, add them to CPPFLAGS, not CFLAGS - the latter doesn't work right with AC_CHECK_HEADERS, as the "gcc -E" run doesn't have the -I flags added.
2008-09-26 05:45:50 +08:00
else
ac_cv_path_GREP=$GREP
fi
fi
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
{ $as_echo "$as_me:${as_lineno-$LINENO}: result: $ac_cv_path_GREP" >&5
$as_echo "$ac_cv_path_GREP" >&6; }
We support building tcpdump with versions of libpcap other than the one with which it was released, and DLT_BLUETOOTH_HCI_H4_WITH_PHDR might be defined by pcap-bpf.h without pcap/bluetooth.h being present (as appears to be the case on Fedora 9, for example), so check whether <pcap/bluetooth.h> is usable. Update a comment - F9 appears to have a "/usr/include/pcap.h" if you install the libpcap headers. When adding -I flags when running a compiler-based test, add them to CPPFLAGS, not CFLAGS - the latter doesn't work right with AC_CHECK_HEADERS, as the "gcc -E" run doesn't have the -I flags added.
2008-09-26 05:45:50 +08:00
GREP="$ac_cv_path_GREP"
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
{ $as_echo "$as_me:${as_lineno-$LINENO}: checking for egrep" >&5
$as_echo_n "checking for egrep... " >&6; }
if ${ac_cv_path_EGREP+:} false; then :
$as_echo_n "(cached) " >&6
We support building tcpdump with versions of libpcap other than the one with which it was released, and DLT_BLUETOOTH_HCI_H4_WITH_PHDR might be defined by pcap-bpf.h without pcap/bluetooth.h being present (as appears to be the case on Fedora 9, for example), so check whether <pcap/bluetooth.h> is usable. Update a comment - F9 appears to have a "/usr/include/pcap.h" if you install the libpcap headers. When adding -I flags when running a compiler-based test, add them to CPPFLAGS, not CFLAGS - the latter doesn't work right with AC_CHECK_HEADERS, as the "gcc -E" run doesn't have the -I flags added.
2008-09-26 05:45:50 +08:00
else
if echo a | $GREP -E '(a|b)' >/dev/null 2>&1
then ac_cv_path_EGREP="$GREP -E"
else
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
if test -z "$EGREP"; then
We support building tcpdump with versions of libpcap other than the one with which it was released, and DLT_BLUETOOTH_HCI_H4_WITH_PHDR might be defined by pcap-bpf.h without pcap/bluetooth.h being present (as appears to be the case on Fedora 9, for example), so check whether <pcap/bluetooth.h> is usable. Update a comment - F9 appears to have a "/usr/include/pcap.h" if you install the libpcap headers. When adding -I flags when running a compiler-based test, add them to CPPFLAGS, not CFLAGS - the latter doesn't work right with AC_CHECK_HEADERS, as the "gcc -E" run doesn't have the -I flags added.
2008-09-26 05:45:50 +08:00
ac_path_EGREP_found=false
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
# Loop through the user's path and test for each of PROGNAME-LIST
as_save_IFS=$IFS; IFS=$PATH_SEPARATOR
We support building tcpdump with versions of libpcap other than the one with which it was released, and DLT_BLUETOOTH_HCI_H4_WITH_PHDR might be defined by pcap-bpf.h without pcap/bluetooth.h being present (as appears to be the case on Fedora 9, for example), so check whether <pcap/bluetooth.h> is usable. Update a comment - F9 appears to have a "/usr/include/pcap.h" if you install the libpcap headers. When adding -I flags when running a compiler-based test, add them to CPPFLAGS, not CFLAGS - the latter doesn't work right with AC_CHECK_HEADERS, as the "gcc -E" run doesn't have the -I flags added.
2008-09-26 05:45:50 +08:00
for as_dir in $PATH$PATH_SEPARATOR/usr/xpg4/bin
do
IFS=$as_save_IFS
test -z "$as_dir" && as_dir=.
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
for ac_prog in egrep; do
for ac_exec_ext in '' $ac_executable_extensions; do
ac_path_EGREP="$as_dir/$ac_prog$ac_exec_ext"
as_fn_executable_p "$ac_path_EGREP" || continue
# Check for GNU ac_path_EGREP and select it if it is found.
We support building tcpdump with versions of libpcap other than the one with which it was released, and DLT_BLUETOOTH_HCI_H4_WITH_PHDR might be defined by pcap-bpf.h without pcap/bluetooth.h being present (as appears to be the case on Fedora 9, for example), so check whether <pcap/bluetooth.h> is usable. Update a comment - F9 appears to have a "/usr/include/pcap.h" if you install the libpcap headers. When adding -I flags when running a compiler-based test, add them to CPPFLAGS, not CFLAGS - the latter doesn't work right with AC_CHECK_HEADERS, as the "gcc -E" run doesn't have the -I flags added.
2008-09-26 05:45:50 +08:00
# Check for GNU $ac_path_EGREP
case `"$ac_path_EGREP" --version 2>&1` in
*GNU*)
ac_cv_path_EGREP="$ac_path_EGREP" ac_path_EGREP_found=:;;
*)
ac_count=0
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
$as_echo_n 0123456789 >"conftest.in"
We support building tcpdump with versions of libpcap other than the one with which it was released, and DLT_BLUETOOTH_HCI_H4_WITH_PHDR might be defined by pcap-bpf.h without pcap/bluetooth.h being present (as appears to be the case on Fedora 9, for example), so check whether <pcap/bluetooth.h> is usable. Update a comment - F9 appears to have a "/usr/include/pcap.h" if you install the libpcap headers. When adding -I flags when running a compiler-based test, add them to CPPFLAGS, not CFLAGS - the latter doesn't work right with AC_CHECK_HEADERS, as the "gcc -E" run doesn't have the -I flags added.
2008-09-26 05:45:50 +08:00
while :
do
cat "conftest.in" "conftest.in" >"conftest.tmp"
mv "conftest.tmp" "conftest.in"
cp "conftest.in" "conftest.nl"
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
$as_echo 'EGREP' >> "conftest.nl"
We support building tcpdump with versions of libpcap other than the one with which it was released, and DLT_BLUETOOTH_HCI_H4_WITH_PHDR might be defined by pcap-bpf.h without pcap/bluetooth.h being present (as appears to be the case on Fedora 9, for example), so check whether <pcap/bluetooth.h> is usable. Update a comment - F9 appears to have a "/usr/include/pcap.h" if you install the libpcap headers. When adding -I flags when running a compiler-based test, add them to CPPFLAGS, not CFLAGS - the latter doesn't work right with AC_CHECK_HEADERS, as the "gcc -E" run doesn't have the -I flags added.
2008-09-26 05:45:50 +08:00
"$ac_path_EGREP" 'EGREP$' < "conftest.nl" >"conftest.out" 2>/dev/null || break
diff "conftest.out" "conftest.nl" >/dev/null 2>&1 || break
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
as_fn_arith $ac_count + 1 && ac_count=$as_val
We support building tcpdump with versions of libpcap other than the one with which it was released, and DLT_BLUETOOTH_HCI_H4_WITH_PHDR might be defined by pcap-bpf.h without pcap/bluetooth.h being present (as appears to be the case on Fedora 9, for example), so check whether <pcap/bluetooth.h> is usable. Update a comment - F9 appears to have a "/usr/include/pcap.h" if you install the libpcap headers. When adding -I flags when running a compiler-based test, add them to CPPFLAGS, not CFLAGS - the latter doesn't work right with AC_CHECK_HEADERS, as the "gcc -E" run doesn't have the -I flags added.
2008-09-26 05:45:50 +08:00
if test $ac_count -gt ${ac_path_EGREP_max-0}; then
# Best one so far, save it but keep looking for a better one
ac_cv_path_EGREP="$ac_path_EGREP"
ac_path_EGREP_max=$ac_count
From Andrew Church <andrew@users.sourceforge.net>: when testing for "pcap_version", "pcap_debug", and "yydebug", don't add our own functions referring to those variables - GCC 3.4.1 optimizes the test code out before the link is done, as it's in a function that's not called.
2004-08-27 15:17:03 +08:00
fi
We support building tcpdump with versions of libpcap other than the one with which it was released, and DLT_BLUETOOTH_HCI_H4_WITH_PHDR might be defined by pcap-bpf.h without pcap/bluetooth.h being present (as appears to be the case on Fedora 9, for example), so check whether <pcap/bluetooth.h> is usable. Update a comment - F9 appears to have a "/usr/include/pcap.h" if you install the libpcap headers. When adding -I flags when running a compiler-based test, add them to CPPFLAGS, not CFLAGS - the latter doesn't work right with AC_CHECK_HEADERS, as the "gcc -E" run doesn't have the -I flags added.
2008-09-26 05:45:50 +08:00
# 10*(2^10) chars as input seems more than enough
test $ac_count -gt 10 && break
done
rm -f conftest.in conftest.tmp conftest.nl conftest.out;;
esac
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
$ac_path_EGREP_found && break 3
done
done
We support building tcpdump with versions of libpcap other than the one with which it was released, and DLT_BLUETOOTH_HCI_H4_WITH_PHDR might be defined by pcap-bpf.h without pcap/bluetooth.h being present (as appears to be the case on Fedora 9, for example), so check whether <pcap/bluetooth.h> is usable. Update a comment - F9 appears to have a "/usr/include/pcap.h" if you install the libpcap headers. When adding -I flags when running a compiler-based test, add them to CPPFLAGS, not CFLAGS - the latter doesn't work right with AC_CHECK_HEADERS, as the "gcc -E" run doesn't have the -I flags added.
2008-09-26 05:45:50 +08:00
done
IFS=$as_save_IFS
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
if test -z "$ac_cv_path_EGREP"; then
as_fn_error $? "no acceptable egrep could be found in $PATH$PATH_SEPARATOR/usr/xpg4/bin" "$LINENO" 5
fi
We support building tcpdump with versions of libpcap other than the one with which it was released, and DLT_BLUETOOTH_HCI_H4_WITH_PHDR might be defined by pcap-bpf.h without pcap/bluetooth.h being present (as appears to be the case on Fedora 9, for example), so check whether <pcap/bluetooth.h> is usable. Update a comment - F9 appears to have a "/usr/include/pcap.h" if you install the libpcap headers. When adding -I flags when running a compiler-based test, add them to CPPFLAGS, not CFLAGS - the latter doesn't work right with AC_CHECK_HEADERS, as the "gcc -E" run doesn't have the -I flags added.
2008-09-26 05:45:50 +08:00
else
ac_cv_path_EGREP=$EGREP
From Max Laier: check whether the system has <net/pfvar.h> and: if it does, use that for the pf definitions; if it doesn't, don't compile in pf support; as both OpenBSD and FreeBSD have changed the pf definitions and header format without changing the DLT value, so you can't reliably read pflog-format libpcap files on a machine running an OS version other than the one on which the file was generated.
2007-09-13 03:36:18 +08:00
fi
We support building tcpdump with versions of libpcap other than the one with which it was released, and DLT_BLUETOOTH_HCI_H4_WITH_PHDR might be defined by pcap-bpf.h without pcap/bluetooth.h being present (as appears to be the case on Fedora 9, for example), so check whether <pcap/bluetooth.h> is usable. Update a comment - F9 appears to have a "/usr/include/pcap.h" if you install the libpcap headers. When adding -I flags when running a compiler-based test, add them to CPPFLAGS, not CFLAGS - the latter doesn't work right with AC_CHECK_HEADERS, as the "gcc -E" run doesn't have the -I flags added.
2008-09-26 05:45:50 +08:00
fi
fi
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
{ $as_echo "$as_me:${as_lineno-$LINENO}: result: $ac_cv_path_EGREP" >&5
$as_echo "$ac_cv_path_EGREP" >&6; }
We support building tcpdump with versions of libpcap other than the one with which it was released, and DLT_BLUETOOTH_HCI_H4_WITH_PHDR might be defined by pcap-bpf.h without pcap/bluetooth.h being present (as appears to be the case on Fedora 9, for example), so check whether <pcap/bluetooth.h> is usable. Update a comment - F9 appears to have a "/usr/include/pcap.h" if you install the libpcap headers. When adding -I flags when running a compiler-based test, add them to CPPFLAGS, not CFLAGS - the latter doesn't work right with AC_CHECK_HEADERS, as the "gcc -E" run doesn't have the -I flags added.
2008-09-26 05:45:50 +08:00
EGREP="$ac_cv_path_EGREP"
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
{ $as_echo "$as_me:${as_lineno-$LINENO}: checking for ANSI C header files" >&5
$as_echo_n "checking for ANSI C header files... " >&6; }
if ${ac_cv_header_stdc+:} false; then :
$as_echo_n "(cached) " >&6
Regenerate with autoconf 2.57.
2004-01-14 11:15:08 +08:00
else
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
cat confdefs.h - <<_ACEOF >conftest.$ac_ext
From Andrew Church <andrew@users.sourceforge.net>: when testing for "pcap_version", "pcap_debug", and "yydebug", don't add our own functions referring to those variables - GCC 3.4.1 optimizes the test code out before the link is done, as it's in a function that's not called.
2004-08-27 15:17:03 +08:00
/* end confdefs.h. */
#include <stdlib.h>
#include <stdarg.h>
#include <string.h>
#include <float.h>
int
main ()
{
;
return 0;
}
Regenerate with autoconf 2.57.
2004-01-14 11:15:08 +08:00
_ACEOF
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
if ac_fn_c_try_compile "$LINENO"; then :
From Andrew Church <andrew@users.sourceforge.net>: when testing for "pcap_version", "pcap_debug", and "yydebug", don't add our own functions referring to those variables - GCC 3.4.1 optimizes the test code out before the link is done, as it's in a function that's not called.
2004-08-27 15:17:03 +08:00
ac_cv_header_stdc=yes
Regenerate with autoconf 2.57.
2004-01-14 11:15:08 +08:00
else
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
ac_cv_header_stdc=no
Regenerate with autoconf 2.57.
2004-01-14 11:15:08 +08:00
fi
We support building tcpdump with versions of libpcap other than the one with which it was released, and DLT_BLUETOOTH_HCI_H4_WITH_PHDR might be defined by pcap-bpf.h without pcap/bluetooth.h being present (as appears to be the case on Fedora 9, for example), so check whether <pcap/bluetooth.h> is usable. Update a comment - F9 appears to have a "/usr/include/pcap.h" if you install the libpcap headers. When adding -I flags when running a compiler-based test, add them to CPPFLAGS, not CFLAGS - the latter doesn't work right with AC_CHECK_HEADERS, as the "gcc -E" run doesn't have the -I flags added.
2008-09-26 05:45:50 +08:00
rm -f core conftest.err conftest.$ac_objext conftest.$ac_ext
From Andrew Church <andrew@users.sourceforge.net>: when testing for "pcap_version", "pcap_debug", and "yydebug", don't add our own functions referring to those variables - GCC 3.4.1 optimizes the test code out before the link is done, as it's in a function that's not called.
2004-08-27 15:17:03 +08:00
if test $ac_cv_header_stdc = yes; then
# SunOS 4.x string.h does not declare mem*, contrary to ANSI.
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
cat confdefs.h - <<_ACEOF >conftest.$ac_ext
From Andrew Church <andrew@users.sourceforge.net>: when testing for "pcap_version", "pcap_debug", and "yydebug", don't add our own functions referring to those variables - GCC 3.4.1 optimizes the test code out before the link is done, as it's in a function that's not called.
2004-08-27 15:17:03 +08:00
/* end confdefs.h. */
#include <string.h>
_ACEOF
if (eval "$ac_cpp conftest.$ac_ext") 2>&5 |
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
$EGREP "memchr" >/dev/null 2>&1; then :
From Andrew Church <andrew@users.sourceforge.net>: when testing for "pcap_version", "pcap_debug", and "yydebug", don't add our own functions referring to those variables - GCC 3.4.1 optimizes the test code out before the link is done, as it's in a function that's not called.
2004-08-27 15:17:03 +08:00
else
ac_cv_header_stdc=no
Bring in KAME IPv6 tcpdump. replaces esp/ah/isakmp decoder. Hope I did not break anything. Portability on IPv4-only node needs checking, I'll do this very soon. (sorry for rather jumbo commit) XXx what is _FAVOR_BSD?
1999-10-30 13:11:06 +08:00
fi
Simplify the detection of OpenSSL libcrypto by using standard autoconf macros rather than a local copy of AC_LBL_SSLEAY. AC_LBL_SSLEAY is old and has not kept pace with some more recent developments in packaging like Debian and Ubuntu's multiarch support. The autoconf macros have been updated to handle multiarch so using them means that tcpdump gains the ability to be built with libcrypto on these new multiarch distros and to work successfully with Travis CI, which uses Ubuntu 12, which is one such multiarch distro (see GH-32). Fixes GH-33
2012-10-14 02:21:45 +08:00
rm -f conftest*
Regenerate with autoconf 2.57.
2004-01-14 11:15:08 +08:00
Initial revision
1999-10-08 07:47:09 +08:00
fi
Regenerate with autoconf 2.57.
2004-01-14 11:15:08 +08:00
From Andrew Church <andrew@users.sourceforge.net>: when testing for "pcap_version", "pcap_debug", and "yydebug", don't add our own functions referring to those variables - GCC 3.4.1 optimizes the test code out before the link is done, as it's in a function that's not called.
2004-08-27 15:17:03 +08:00
if test $ac_cv_header_stdc = yes; then
# ISC 2.0.2 stdlib.h does not declare free, contrary to ANSI.
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
cat confdefs.h - <<_ACEOF >conftest.$ac_ext
From Andrew Church <andrew@users.sourceforge.net>: when testing for "pcap_version", "pcap_debug", and "yydebug", don't add our own functions referring to those variables - GCC 3.4.1 optimizes the test code out before the link is done, as it's in a function that's not called.
2004-08-27 15:17:03 +08:00
/* end confdefs.h. */
#include <stdlib.h>
_ACEOF
if (eval "$ac_cpp conftest.$ac_ext") 2>&5 |
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
$EGREP "free" >/dev/null 2>&1; then :
From Andrew Church <andrew@users.sourceforge.net>: when testing for "pcap_version", "pcap_debug", and "yydebug", don't add our own functions referring to those variables - GCC 3.4.1 optimizes the test code out before the link is done, as it's in a function that's not called.
2004-08-27 15:17:03 +08:00
else
ac_cv_header_stdc=no
fi
Simplify the detection of OpenSSL libcrypto by using standard autoconf macros rather than a local copy of AC_LBL_SSLEAY. AC_LBL_SSLEAY is old and has not kept pace with some more recent developments in packaging like Debian and Ubuntu's multiarch support. The autoconf macros have been updated to handle multiarch so using them means that tcpdump gains the ability to be built with libcrypto on these new multiarch distros and to work successfully with Travis CI, which uses Ubuntu 12, which is one such multiarch distro (see GH-32). Fixes GH-33
2012-10-14 02:21:45 +08:00
rm -f conftest*
From Andrew Church <andrew@users.sourceforge.net>: when testing for "pcap_version", "pcap_debug", and "yydebug", don't add our own functions referring to those variables - GCC 3.4.1 optimizes the test code out before the link is done, as it's in a function that's not called.
2004-08-27 15:17:03 +08:00
fi
if test $ac_cv_header_stdc = yes; then
# /bin/cc in Irix-4.0.5 gets non-ANSI ctype macros unless using -ansi.
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
if test "$cross_compiling" = yes; then :
From Andrew Church <andrew@users.sourceforge.net>: when testing for "pcap_version", "pcap_debug", and "yydebug", don't add our own functions referring to those variables - GCC 3.4.1 optimizes the test code out before the link is done, as it's in a function that's not called.
2004-08-27 15:17:03 +08:00
:
Regenerate with autoconf 2.57.
2004-01-14 11:15:08 +08:00
else
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
cat confdefs.h - <<_ACEOF >conftest.$ac_ext
From Andrew Church <andrew@users.sourceforge.net>: when testing for "pcap_version", "pcap_debug", and "yydebug", don't add our own functions referring to those variables - GCC 3.4.1 optimizes the test code out before the link is done, as it's in a function that's not called.
2004-08-27 15:17:03 +08:00
/* end confdefs.h. */
#include <ctype.h>
We support building tcpdump with versions of libpcap other than the one with which it was released, and DLT_BLUETOOTH_HCI_H4_WITH_PHDR might be defined by pcap-bpf.h without pcap/bluetooth.h being present (as appears to be the case on Fedora 9, for example), so check whether <pcap/bluetooth.h> is usable. Update a comment - F9 appears to have a "/usr/include/pcap.h" if you install the libpcap headers. When adding -I flags when running a compiler-based test, add them to CPPFLAGS, not CFLAGS - the latter doesn't work right with AC_CHECK_HEADERS, as the "gcc -E" run doesn't have the -I flags added.
2008-09-26 05:45:50 +08:00
#include <stdlib.h>
From Andrew Church <andrew@users.sourceforge.net>: when testing for "pcap_version", "pcap_debug", and "yydebug", don't add our own functions referring to those variables - GCC 3.4.1 optimizes the test code out before the link is done, as it's in a function that's not called.
2004-08-27 15:17:03 +08:00
#if ((' ' & 0x0FF) == 0x020)
# define ISLOWER(c) ('a' <= (c) && (c) <= 'z')
# define TOUPPER(c) (ISLOWER(c) ? 'A' + ((c) - 'a') : (c))
#else
# define ISLOWER(c) \
Add -Wpointer-arith to the list of warnings we enable with GCC.
2005-11-08 10:59:40 +08:00
(('a' <= (c) && (c) <= 'i') \
|| ('j' <= (c) && (c) <= 'r') \
|| ('s' <= (c) && (c) <= 'z'))
From Andrew Church <andrew@users.sourceforge.net>: when testing for "pcap_version", "pcap_debug", and "yydebug", don't add our own functions referring to those variables - GCC 3.4.1 optimizes the test code out before the link is done, as it's in a function that's not called.
2004-08-27 15:17:03 +08:00
# define TOUPPER(c) (ISLOWER(c) ? ((c) | 0x40) : (c))
#endif
Regenerate with autoconf 2.57.
2004-01-14 11:15:08 +08:00
From Andrew Church <andrew@users.sourceforge.net>: when testing for "pcap_version", "pcap_debug", and "yydebug", don't add our own functions referring to those variables - GCC 3.4.1 optimizes the test code out before the link is done, as it's in a function that's not called.
2004-08-27 15:17:03 +08:00
#define XOR(e, f) (((e) && !(f)) || (!(e) && (f)))
Regenerate with autoconf 2.57.
2004-01-14 11:15:08 +08:00
int
main ()
{
From Andrew Church <andrew@users.sourceforge.net>: when testing for "pcap_version", "pcap_debug", and "yydebug", don't add our own functions referring to those variables - GCC 3.4.1 optimizes the test code out before the link is done, as it's in a function that's not called.
2004-08-27 15:17:03 +08:00
int i;
for (i = 0; i < 256; i++)
if (XOR (islower (i), ISLOWER (i))
Add -Wpointer-arith to the list of warnings we enable with GCC.
2005-11-08 10:59:40 +08:00
|| toupper (i) != TOUPPER (i))
We support building tcpdump with versions of libpcap other than the one with which it was released, and DLT_BLUETOOTH_HCI_H4_WITH_PHDR might be defined by pcap-bpf.h without pcap/bluetooth.h being present (as appears to be the case on Fedora 9, for example), so check whether <pcap/bluetooth.h> is usable. Update a comment - F9 appears to have a "/usr/include/pcap.h" if you install the libpcap headers. When adding -I flags when running a compiler-based test, add them to CPPFLAGS, not CFLAGS - the latter doesn't work right with AC_CHECK_HEADERS, as the "gcc -E" run doesn't have the -I flags added.
2008-09-26 05:45:50 +08:00
return 2;
return 0;
Regenerate with autoconf 2.57.
2004-01-14 11:15:08 +08:00
}
_ACEOF
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
if ac_fn_c_try_run "$LINENO"; then :
Check for extra networking libraries before checking for IPv6. On some platforms, such as SunOS 5.x, building the "do we have IPv6 support?" test program requires the extra networking libraries, so we need to know what extra networking libraries are required before doing that test.
2013-04-07 04:03:58 +08:00
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
else
ac_cv_header_stdc=no
Regenerate with autoconf 2.57.
2004-01-14 11:15:08 +08:00
fi
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
rm -f core *.core core.conftest.* gmon.out bb.out conftest$ac_exeext \
conftest.$ac_objext conftest.beam conftest.$ac_ext
Initial revision
1999-10-08 07:47:09 +08:00
fi
We support building tcpdump with versions of libpcap other than the one with which it was released, and DLT_BLUETOOTH_HCI_H4_WITH_PHDR might be defined by pcap-bpf.h without pcap/bluetooth.h being present (as appears to be the case on Fedora 9, for example), so check whether <pcap/bluetooth.h> is usable. Update a comment - F9 appears to have a "/usr/include/pcap.h" if you install the libpcap headers. When adding -I flags when running a compiler-based test, add them to CPPFLAGS, not CFLAGS - the latter doesn't work right with AC_CHECK_HEADERS, as the "gcc -E" run doesn't have the -I flags added.
2008-09-26 05:45:50 +08:00
From Andrew Church <andrew@users.sourceforge.net>: when testing for "pcap_version", "pcap_debug", and "yydebug", don't add our own functions referring to those variables - GCC 3.4.1 optimizes the test code out before the link is done, as it's in a function that's not called.
2004-08-27 15:17:03 +08:00
fi
fi
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
{ $as_echo "$as_me:${as_lineno-$LINENO}: result: $ac_cv_header_stdc" >&5
$as_echo "$ac_cv_header_stdc" >&6; }
From Andrew Church <andrew@users.sourceforge.net>: when testing for "pcap_version", "pcap_debug", and "yydebug", don't add our own functions referring to those variables - GCC 3.4.1 optimizes the test code out before the link is done, as it's in a function that's not called.
2004-08-27 15:17:03 +08:00
if test $ac_cv_header_stdc = yes; then
Regenerate with autoconf 2.57.
2004-01-14 11:15:08 +08:00
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
$as_echo "#define STDC_HEADERS 1" >>confdefs.h
Initial revision
1999-10-08 07:47:09 +08:00
Bring in KAME IPv6 tcpdump. replaces esp/ah/isakmp decoder. Hope I did not break anything. Portability on IPv4-only node needs checking, I'll do this very soon. (sorry for rather jumbo commit) XXx what is _FAVOR_BSD?
1999-10-30 13:11:06 +08:00
fi
Regenerate with autoconf 2.57.
2004-01-14 11:15:08 +08:00
From Andrew Church <andrew@users.sourceforge.net>: when testing for "pcap_version", "pcap_debug", and "yydebug", don't add our own functions referring to those variables - GCC 3.4.1 optimizes the test code out before the link is done, as it's in a function that's not called.
2004-08-27 15:17:03 +08:00
# On IRIX 5.3, sys/types and inttypes.h are conflicting.
Check for extra networking libraries before checking for IPv6. On some platforms, such as SunOS 5.x, building the "do we have IPv6 support?" test program requires the extra networking libraries, so we need to know what extra networking libraries are required before doing that test.
2013-04-07 04:03:58 +08:00
for ac_header in sys/types.h sys/stat.h stdlib.h string.h memory.h strings.h \
Add -Wpointer-arith to the list of warnings we enable with GCC.
2005-11-08 10:59:40 +08:00
inttypes.h stdint.h unistd.h
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
do :
as_ac_Header=`$as_echo "ac_cv_header_$ac_header" | $as_tr_sh`
ac_fn_c_check_header_compile "$LINENO" "$ac_header" "$as_ac_Header" "$ac_includes_default
"
if eval test \"x\$"$as_ac_Header"\" = x"yes"; then :
From Andrew Church <andrew@users.sourceforge.net>: when testing for "pcap_version", "pcap_debug", and "yydebug", don't add our own functions referring to those variables - GCC 3.4.1 optimizes the test code out before the link is done, as it's in a function that's not called.
2004-08-27 15:17:03 +08:00
cat >>confdefs.h <<_ACEOF
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
#define `$as_echo "HAVE_$ac_header" | $as_tr_cpp` 1
From Andrew Church <andrew@users.sourceforge.net>: when testing for "pcap_version", "pcap_debug", and "yydebug", don't add our own functions referring to those variables - GCC 3.4.1 optimizes the test code out before the link is done, as it's in a function that's not called.
2004-08-27 15:17:03 +08:00
_ACEOF
fi
done
Handle systems with getrpcbynumber() but no header file for it. Glibc 2.14 doesn't install the ONC RPC headers, but it installs the ONC RPC routines, presumably for binary compatibility. Don't use getrpcbynumber() unless we have it *and* the header file to declare it.
2011-09-03 12:31:09 +08:00
for ac_header in fcntl.h rpc/rpc.h rpc/rpcent.h netdnet/dnetdb.h
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
do :
as_ac_Header=`$as_echo "ac_cv_header_$ac_header" | $as_tr_sh`
ac_fn_c_check_header_mongrel "$LINENO" "$ac_header" "$as_ac_Header" "$ac_includes_default"
if eval test \"x\$"$as_ac_Header"\" = x"yes"; then :
From Andrew Church <andrew@users.sourceforge.net>: when testing for "pcap_version", "pcap_debug", and "yydebug", don't add our own functions referring to those variables - GCC 3.4.1 optimizes the test code out before the link is done, as it's in a function that's not called.
2004-08-27 15:17:03 +08:00
cat >>confdefs.h <<_ACEOF
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
#define `$as_echo "HAVE_$ac_header" | $as_tr_cpp` 1
From Andrew Church <andrew@users.sourceforge.net>: when testing for "pcap_version", "pcap_debug", and "yydebug", don't add our own functions referring to those variables - GCC 3.4.1 optimizes the test code out before the link is done, as it's in a function that's not called.
2004-08-27 15:17:03 +08:00
_ACEOF
fi
done
From Max Laier: check whether the system has <net/pfvar.h> and: if it does, use that for the pf definitions; if it doesn't, don't compile in pf support; as both OpenBSD and FreeBSD have changed the pf definitions and header format without changing the DLT value, so you can't reliably read pflog-format libpcap files on a machine running an OS version other than the one on which the file was generated.
2007-09-13 03:36:18 +08:00
for ac_header in net/pfvar.h
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
do :
ac_fn_c_check_header_compile "$LINENO" "net/pfvar.h" "ac_cv_header_net_pfvar_h" "#include <sys/types.h>
From Andrew Church <andrew@users.sourceforge.net>: when testing for "pcap_version", "pcap_debug", and "yydebug", don't add our own functions referring to those variables - GCC 3.4.1 optimizes the test code out before the link is done, as it's in a function that's not called.
2004-08-27 15:17:03 +08:00
#include <sys/socket.h>
From Max Laier: check whether the system has <net/pfvar.h> and: if it does, use that for the pf definitions; if it doesn't, don't compile in pf support; as both OpenBSD and FreeBSD have changed the pf definitions and header format without changing the DLT value, so you can't reliably read pflog-format libpcap files on a machine running an OS version other than the one on which the file was generated.
2007-09-13 03:36:18 +08:00
#include <net/if.h>
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
"
if test "x$ac_cv_header_net_pfvar_h" = xyes; then :
From Max Laier: check whether the system has <net/pfvar.h> and: if it does, use that for the pf definitions; if it doesn't, don't compile in pf support; as both OpenBSD and FreeBSD have changed the pf definitions and header format without changing the DLT value, so you can't reliably read pflog-format libpcap files on a machine running an OS version other than the one on which the file was generated.
2007-09-13 03:36:18 +08:00
cat >>confdefs.h <<_ACEOF
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
#define HAVE_NET_PFVAR_H 1
From Max Laier: check whether the system has <net/pfvar.h> and: if it does, use that for the pf definitions; if it doesn't, don't compile in pf support; as both OpenBSD and FreeBSD have changed the pf definitions and header format without changing the DLT value, so you can't reliably read pflog-format libpcap files on a machine running an OS version other than the one on which the file was generated.
2007-09-13 03:36:18 +08:00
_ACEOF
fi
done
The string-comparison operator in the "test" command is "=", not "==".
2008-02-06 02:58:19 +08:00
if test "$ac_cv_header_net_pfvar_h" = yes; then
Don't assume you have <net/if_pflog.h> if you have <net/pfvar.h>. Debian/kFreeBSD ships <net/pfvar.h> but not <net/if_pflog.h>.
2015-05-18 01:47:30 +08:00
for ac_header in net/if_pflog.h
do :
ac_fn_c_check_header_compile "$LINENO" "net/if_pflog.h" "ac_cv_header_net_if_pflog_h" "#include <sys/types.h>
#include <sys/socket.h>
#include <net/if.h>
#include <net/pfvar.h>
"
if test "x$ac_cv_header_net_if_pflog_h" = xyes; then :
cat >>confdefs.h <<_ACEOF
#define HAVE_NET_IF_PFLOG_H 1
_ACEOF
fi
done
if test "$ac_cv_header_net_if_pflog_h" = yes; then
LOCALSRC="print-pflog.c $LOCALSRC"
fi
From Max Laier: check whether the system has <net/pfvar.h> and: if it does, use that for the pf definitions; if it doesn't, don't compile in pf support; as both OpenBSD and FreeBSD have changed the pf definitions and header format without changing the DLT value, so you can't reliably read pflog-format libpcap files on a machine running an OS version other than the one on which the file was generated.
2007-09-13 03:36:18 +08:00
fi
for ac_header in netinet/if_ether.h
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
do :
ac_fn_c_check_header_compile "$LINENO" "netinet/if_ether.h" "ac_cv_header_netinet_if_ether_h" "#include <sys/types.h>
From Max Laier: check whether the system has <net/pfvar.h> and: if it does, use that for the pf definitions; if it doesn't, don't compile in pf support; as both OpenBSD and FreeBSD have changed the pf definitions and header format without changing the DLT value, so you can't reliably read pflog-format libpcap files on a machine running an OS version other than the one on which the file was generated.
2007-09-13 03:36:18 +08:00
#include <sys/socket.h>
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
"
if test "x$ac_cv_header_netinet_if_ether_h" = xyes; then :
From Andrew Church <andrew@users.sourceforge.net>: when testing for "pcap_version", "pcap_debug", and "yydebug", don't add our own functions referring to those variables - GCC 3.4.1 optimizes the test code out before the link is done, as it's in a function that's not called.
2004-08-27 15:17:03 +08:00
cat >>confdefs.h <<_ACEOF
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
#define HAVE_NETINET_IF_ETHER_H 1
From Andrew Church <andrew@users.sourceforge.net>: when testing for "pcap_version", "pcap_debug", and "yydebug", don't add our own functions referring to those variables - GCC 3.4.1 optimizes the test code out before the link is done, as it's in a function that's not called.
2004-08-27 15:17:03 +08:00
_ACEOF
fi
done
Do the same sort of checks whether ether_ntohost() is declared that we do in libpcap for ether_hostton(). Include <netinet/ether.h> only if it declares ether_ntohost(). If nothing declares it, declare it ourselves, as we do in libpcap. Don't cast the second argument to ether_ntohost() to a const pointer, as some systems don't modify it but don't declare that argument as a const pointer. (This is similar to what we do on libpvap for ether_hostton().) Fix indentation.
2005-03-28 06:38:09 +08:00
if test "$ac_cv_header_netinet_if_ether_h" != yes; then
#
# The simple test didn't work.
# Do we need to include <net/if.h> first?
# Unset ac_cv_header_netinet_if_ether_h so we don't
# treat the previous failure as a cached value and
# suppress the next test.
#
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
{ $as_echo "$as_me:${as_lineno-$LINENO}: Rechecking with some additional includes" >&5
$as_echo "$as_me: Rechecking with some additional includes" >&6;}
Do the same sort of checks whether ether_ntohost() is declared that we do in libpcap for ether_hostton(). Include <netinet/ether.h> only if it declares ether_ntohost(). If nothing declares it, declare it ourselves, as we do in libpcap. Don't cast the second argument to ether_ntohost() to a const pointer, as some systems don't modify it but don't declare that argument as a const pointer. (This is similar to what we do on libpvap for ether_hostton().) Fix indentation.
2005-03-28 06:38:09 +08:00
unset ac_cv_header_netinet_if_ether_h
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
for ac_header in netinet/if_ether.h
do :
ac_fn_c_check_header_compile "$LINENO" "netinet/if_ether.h" "ac_cv_header_netinet_if_ether_h" "#include <sys/types.h>
Do the same sort of checks whether ether_ntohost() is declared that we do in libpcap for ether_hostton(). Include <netinet/ether.h> only if it declares ether_ntohost(). If nothing declares it, declare it ourselves, as we do in libpcap. Don't cast the second argument to ether_ntohost() to a const pointer, as some systems don't modify it but don't declare that argument as a const pointer. (This is similar to what we do on libpvap for ether_hostton().) Fix indentation.
2005-03-28 06:38:09 +08:00
#include <sys/socket.h>
#include <netinet/in.h>
struct mbuf;
struct rtentry;
#include <net/if.h>
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
"
if test "x$ac_cv_header_netinet_if_ether_h" = xyes; then :
cat >>confdefs.h <<_ACEOF
#define HAVE_NETINET_IF_ETHER_H 1
Do the same sort of checks whether ether_ntohost() is declared that we do in libpcap for ether_hostton(). Include <netinet/ether.h> only if it declares ether_ntohost(). If nothing declares it, declare it ourselves, as we do in libpcap. Don't cast the second argument to ether_ntohost() to a const pointer, as some systems don't modify it but don't declare that argument as a const pointer. (This is similar to what we do on libpvap for ether_hostton().) Fix indentation.
2005-03-28 06:38:09 +08:00
_ACEOF
fi
done
fi
From Andrew Church <andrew@users.sourceforge.net>: when testing for "pcap_version", "pcap_debug", and "yydebug", don't add our own functions referring to those variables - GCC 3.4.1 optimizes the test code out before the link is done, as it's in a function that's not called.
2004-08-27 15:17:03 +08:00
case "$host_os" in
Build universal on OS X by default; add an option to disable that. Instead of requiring the user to specify -arch options on OS X to build a universal version of tcpdump, just default to universal on OS X by default. Pick the particular targets to match the way tcpdump is built for the OS for which we're building.
2010-04-05 03:08:11 +08:00
darwin*)
# Check whether --enable-universal was given.
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
if test "${enable_universal+set}" = set; then :
Build universal on OS X by default; add an option to disable that. Instead of requiring the user to specify -arch options on OS X to build a universal version of tcpdump, just default to universal on OS X by default. Pick the particular targets to match the way tcpdump is built for the OS for which we're building.
2010-04-05 03:08:11 +08:00
enableval=$enable_universal;
fi
if test "$enable_universal" != "no"; then
case "$host_os" in
Build fat appropriately for Leopard.
2010-04-07 06:10:31 +08:00
darwin9.*)
#
# Leopard. Build for x86 and 32-bit PowerPC, with
# x86 first. (That's what Apple does.)
#
V_CCOPT="$V_CCOPT -arch i386 -arch ppc"
LDFLAGS="$LDFLAGS -arch i386 -arch ppc"
;;
Fix check for Snow Leopard. For OS X version 10.{x}.{y}, Darwin is (at least for later versions) version {x+4}.{y}.
2010-04-05 03:42:00 +08:00
darwin10.*)
Build universal on OS X by default; add an option to disable that. Instead of requiring the user to specify -arch options on OS X to build a universal version of tcpdump, just default to universal on OS X by default. Pick the particular targets to match the way tcpdump is built for the OS for which we're building.
2010-04-05 03:08:11 +08:00
#
# Snow Leopard. Build for x86-64 and x86, with
# x86-64 first. (That's what Apple does.)
#
V_CCOPT="$V_CCOPT -arch x86_64 -arch i386"
LDFLAGS="$LDFLAGS -arch x86_64 -arch i386"
;;
esac
fi
;;
Bring in KAME IPv6 tcpdump. replaces esp/ah/isakmp decoder. Hope I did not break anything. Portability on IPv4-only node needs checking, I'll do this very soon. (sorry for rather jumbo commit) XXx what is _FAVOR_BSD?
1999-10-30 13:11:06 +08:00
esac
From Andrew Church <andrew@users.sourceforge.net>: when testing for "pcap_version", "pcap_debug", and "yydebug", don't add our own functions referring to those variables - GCC 3.4.1 optimizes the test code out before the link is done, as it's in a function that's not called.
2004-08-27 15:17:03 +08:00
Propagate from the git tree: Author: Peter Volkov <pva@gentoo.org> Date: Sun Nov 9 20:33:27 2008 -0500 Currently it's impossible to build tcpdump without libsmi on system with libsmi installed. The patch in attachment adds --with{,out}-smi configure switch which allows to disable it.
2008-11-18 15:39:20 +08:00
# Check whether --with-smi was given.
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
if test "${with_smi+set}" = set; then :
Propagate from the git tree: Author: Peter Volkov <pva@gentoo.org> Date: Sun Nov 9 20:33:27 2008 -0500 Currently it's impossible to build tcpdump without libsmi on system with libsmi installed. The patch in attachment adds --with{,out}-smi configure switch which allows to disable it.
2008-11-18 15:39:20 +08:00
withval=$with_smi;
else
with_smi=yes
fi
if test "x$with_smi" != "xno" ; then
Clean up configure check for libsmi. First, check for smi.h. If we don't have it, don't check for anything else. If we do have it, check for libsmi containing smiInit. If we don't have it, don't check for anything else. If we do have it, check, with our test program, whether we can use it. If that succeeds, prepend -lsmi to LIBS, and set USE_LIBSMI. Otherwise, don't do either of those. Check, in source, *only* for USE_LIBSMI. If it's set, use libsmi, otherwise don't - don't even include smi.h, even if we happened to have found it, and don't print the libsmi version string.
2014-09-01 02:57:04 +08:00
ac_fn_c_check_header_mongrel "$LINENO" "smi.h" "ac_cv_header_smi_h" "$ac_includes_default"
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
if test "x$ac_cv_header_smi_h" = xyes; then :
Update to rev 1.15 of configure.in
1999-12-15 00:39:39 +08:00
Clean up configure check for libsmi. First, check for smi.h. If we don't have it, don't check for anything else. If we do have it, check for libsmi containing smiInit. If we don't have it, don't check for anything else. If we do have it, check, with our test program, whether we can use it. If that succeeds, prepend -lsmi to LIBS, and set USE_LIBSMI. Otherwise, don't do either of those. Check, in source, *only* for USE_LIBSMI. If it's set, use libsmi, otherwise don't - don't even include smi.h, even if we happened to have found it, and don't print the libsmi version string.
2014-09-01 02:57:04 +08:00
#
# OK, we found smi.h. Do we have libsmi with smiInit?
#
{ $as_echo "$as_me:${as_lineno-$LINENO}: checking for smiInit in -lsmi" >&5
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
$as_echo_n "checking for smiInit in -lsmi... " >&6; }
if ${ac_cv_lib_smi_smiInit+:} false; then :
$as_echo_n "(cached) " >&6
Update to rev 1.15 of configure.in
1999-12-15 00:39:39 +08:00
else
Regenerate with autoconf 2.57.
2004-01-14 11:15:08 +08:00
ac_check_lib_save_LIBS=$LIBS
Update to rev 1.15 of configure.in
1999-12-15 00:39:39 +08:00
LIBS="-lsmi $LIBS"
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
cat confdefs.h - <<_ACEOF >conftest.$ac_ext
From Andrew Church <andrew@users.sourceforge.net>: when testing for "pcap_version", "pcap_debug", and "yydebug", don't add our own functions referring to those variables - GCC 3.4.1 optimizes the test code out before the link is done, as it's in a function that's not called.
2004-08-27 15:17:03 +08:00
/* end confdefs.h. */
Regenerate with autoconf 2.57.
2004-01-14 11:15:08 +08:00
We support building tcpdump with versions of libpcap other than the one with which it was released, and DLT_BLUETOOTH_HCI_H4_WITH_PHDR might be defined by pcap-bpf.h without pcap/bluetooth.h being present (as appears to be the case on Fedora 9, for example), so check whether <pcap/bluetooth.h> is usable. Update a comment - F9 appears to have a "/usr/include/pcap.h" if you install the libpcap headers. When adding -I flags when running a compiler-based test, add them to CPPFLAGS, not CFLAGS - the latter doesn't work right with AC_CHECK_HEADERS, as the "gcc -E" run doesn't have the -I flags added.
2008-09-26 05:45:50 +08:00
/* Override any GCC internal prototype to avoid an error.
Use char because int might match the return type of a GCC
builtin and then its argument prototype would still apply. */
Regenerate with autoconf 2.57.
2004-01-14 11:15:08 +08:00
#ifdef __cplusplus
extern "C"
#endif
char smiInit ();
int
main ()
{
We support building tcpdump with versions of libpcap other than the one with which it was released, and DLT_BLUETOOTH_HCI_H4_WITH_PHDR might be defined by pcap-bpf.h without pcap/bluetooth.h being present (as appears to be the case on Fedora 9, for example), so check whether <pcap/bluetooth.h> is usable. Update a comment - F9 appears to have a "/usr/include/pcap.h" if you install the libpcap headers. When adding -I flags when running a compiler-based test, add them to CPPFLAGS, not CFLAGS - the latter doesn't work right with AC_CHECK_HEADERS, as the "gcc -E" run doesn't have the -I flags added.
2008-09-26 05:45:50 +08:00
return smiInit ();
Regenerate with autoconf 2.57.
2004-01-14 11:15:08 +08:00
;
return 0;
}
_ACEOF
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
if ac_fn_c_try_link "$LINENO"; then :
Regenerate with autoconf 2.57.
2004-01-14 11:15:08 +08:00
ac_cv_lib_smi_smiInit=yes
else
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
ac_cv_lib_smi_smiInit=no
Regenerate with autoconf 2.57.
2004-01-14 11:15:08 +08:00
fi
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
rm -f core conftest.err conftest.$ac_objext \
conftest$ac_exeext conftest.$ac_ext
Regenerate with autoconf 2.57.
2004-01-14 11:15:08 +08:00
LIBS=$ac_check_lib_save_LIBS
fi
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
{ $as_echo "$as_me:${as_lineno-$LINENO}: result: $ac_cv_lib_smi_smiInit" >&5
$as_echo "$ac_cv_lib_smi_smiInit" >&6; }
if test "x$ac_cv_lib_smi_smiInit" = xyes; then :
Update to rev 1.15 of configure.in
1999-12-15 00:39:39 +08:00
Clean up configure check for libsmi. First, check for smi.h. If we don't have it, don't check for anything else. If we do have it, check for libsmi containing smiInit. If we don't have it, don't check for anything else. If we do have it, check, with our test program, whether we can use it. If that succeeds, prepend -lsmi to LIBS, and set USE_LIBSMI. Otherwise, don't do either of those. Check, in source, *only* for USE_LIBSMI. If it's set, use libsmi, otherwise don't - don't even include smi.h, even if we happened to have found it, and don't print the libsmi version string.
2014-09-01 02:57:04 +08:00
#
# OK, we have libsmi with smiInit. Can we use it?
#
{ $as_echo "$as_me:${as_lineno-$LINENO}: checking whether to enable libsmi" >&5
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
$as_echo_n "checking whether to enable libsmi... " >&6; }
Clean up configure check for libsmi. First, check for smi.h. If we don't have it, don't check for anything else. If we do have it, check for libsmi containing smiInit. If we don't have it, don't check for anything else. If we do have it, check, with our test program, whether we can use it. If that succeeds, prepend -lsmi to LIBS, and set USE_LIBSMI. Otherwise, don't do either of those. Check, in source, *only* for USE_LIBSMI. If it's set, use libsmi, otherwise don't - don't even include smi.h, even if we happened to have found it, and don't print the libsmi version string.
2014-09-01 02:57:04 +08:00
savedlibs="$LIBS"
LIBS="-lsmi $LIBS"
if test "$cross_compiling" = yes; then :
{ $as_echo "$as_me:${as_lineno-$LINENO}: result: not when cross-compiling" >&5
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
$as_echo "not when cross-compiling" >&6; }
Clean up configure check for libsmi. First, check for smi.h. If we don't have it, don't check for anything else. If we do have it, check for libsmi containing smiInit. If we don't have it, don't check for anything else. If we do have it, check, with our test program, whether we can use it. If that succeeds, prepend -lsmi to LIBS, and set USE_LIBSMI. Otherwise, don't do either of those. Check, in source, *only* for USE_LIBSMI. If it's set, use libsmi, otherwise don't - don't even include smi.h, even if we happened to have found it, and don't print the libsmi version string.
2014-09-01 02:57:04 +08:00
LIBS="$savedlibs"
Provide defaults for cross-compiling (libsmi = no, "standard" type sizes) and print a warning about the unavoidable warning from AC_C_BIGENDIAN
2000-01-10 05:41:00 +08:00
regen
2000-01-08 00:36:57 +08:00
else
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
cat confdefs.h - <<_ACEOF >conftest.$ac_ext
From Andrew Church <andrew@users.sourceforge.net>: when testing for "pcap_version", "pcap_debug", and "yydebug", don't add our own functions referring to those variables - GCC 3.4.1 optimizes the test code out before the link is done, as it's in a function that's not called.
2004-08-27 15:17:03 +08:00
/* end confdefs.h. */
Clean up configure check for libsmi. First, check for smi.h. If we don't have it, don't check for anything else. If we do have it, check for libsmi containing smiInit. If we don't have it, don't check for anything else. If we do have it, check, with our test program, whether we can use it. If that succeeds, prepend -lsmi to LIBS, and set USE_LIBSMI. Otherwise, don't do either of those. Check, in source, *only* for USE_LIBSMI. If it's set, use libsmi, otherwise don't - don't even include smi.h, even if we happened to have found it, and don't print the libsmi version string.
2014-09-01 02:57:04 +08:00
/* libsmi available check */
regen
2000-01-08 00:36:57 +08:00
#include <smi.h>
main()
{
re-generated
2000-07-01 11:40:34 +08:00
int current, revision, age, n;
const int required = 2;
Regenerate with autoconf 2.57.
2004-01-14 11:15:08 +08:00
if (smiInit(""))
regen
2000-01-08 00:36:57 +08:00
exit(1);
re-generated
2000-07-01 11:40:34 +08:00
if (strcmp(SMI_LIBRARY_VERSION, smi_library_version))
exit(2);
n = sscanf(smi_library_version, "%d:%d:%d", &current, &revision, &age);
if (n != 3)
exit(3);
if (required < current - age || required > current)
exit(4);
exit(0);
regen
2000-01-08 00:36:57 +08:00
}
Regenerate with autoconf 2.57.
2004-01-14 11:15:08 +08:00
_ACEOF
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
if ac_fn_c_try_run "$LINENO"; then :
Clean up configure check for libsmi. First, check for smi.h. If we don't have it, don't check for anything else. If we do have it, check for libsmi containing smiInit. If we don't have it, don't check for anything else. If we do have it, check, with our test program, whether we can use it. If that succeeds, prepend -lsmi to LIBS, and set USE_LIBSMI. Otherwise, don't do either of those. Check, in source, *only* for USE_LIBSMI. If it's set, use libsmi, otherwise don't - don't even include smi.h, even if we happened to have found it, and don't print the libsmi version string.
2014-09-01 02:57:04 +08:00
{ $as_echo "$as_me:${as_lineno-$LINENO}: result: yes" >&5
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
$as_echo "yes" >&6; }
Get rid of acconfig.h.
2013-05-13 06:28:28 +08:00
Clean up configure check for libsmi. First, check for smi.h. If we don't have it, don't check for anything else. If we do have it, check for libsmi containing smiInit. If we don't have it, don't check for anything else. If we do have it, check, with our test program, whether we can use it. If that succeeds, prepend -lsmi to LIBS, and set USE_LIBSMI. Otherwise, don't do either of those. Check, in source, *only* for USE_LIBSMI. If it's set, use libsmi, otherwise don't - don't even include smi.h, even if we happened to have found it, and don't print the libsmi version string.
2014-09-01 02:57:04 +08:00
$as_echo "#define USE_LIBSMI 1" >>confdefs.h
Update to rev 1.15 of configure.in
1999-12-15 00:39:39 +08:00
regen
2000-01-08 00:36:57 +08:00
else
Clean up configure check for libsmi. First, check for smi.h. If we don't have it, don't check for anything else. If we do have it, check for libsmi containing smiInit. If we don't have it, don't check for anything else. If we do have it, check, with our test program, whether we can use it. If that succeeds, prepend -lsmi to LIBS, and set USE_LIBSMI. Otherwise, don't do either of those. Check, in source, *only* for USE_LIBSMI. If it's set, use libsmi, otherwise don't - don't even include smi.h, even if we happened to have found it, and don't print the libsmi version string.
2014-09-01 02:57:04 +08:00
case $? in
1) { $as_echo "$as_me:${as_lineno-$LINENO}: result: no - smiInit failed" >&5
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
$as_echo "no - smiInit failed" >&6; } ;;
Clean up configure check for libsmi. First, check for smi.h. If we don't have it, don't check for anything else. If we do have it, check for libsmi containing smiInit. If we don't have it, don't check for anything else. If we do have it, check, with our test program, whether we can use it. If that succeeds, prepend -lsmi to LIBS, and set USE_LIBSMI. Otherwise, don't do either of those. Check, in source, *only* for USE_LIBSMI. If it's set, use libsmi, otherwise don't - don't even include smi.h, even if we happened to have found it, and don't print the libsmi version string.
2014-09-01 02:57:04 +08:00
2) { $as_echo "$as_me:${as_lineno-$LINENO}: result: no - header/library version mismatch" >&5
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
$as_echo "no - header/library version mismatch" >&6; } ;;
Clean up configure check for libsmi. First, check for smi.h. If we don't have it, don't check for anything else. If we do have it, check for libsmi containing smiInit. If we don't have it, don't check for anything else. If we do have it, check, with our test program, whether we can use it. If that succeeds, prepend -lsmi to LIBS, and set USE_LIBSMI. Otherwise, don't do either of those. Check, in source, *only* for USE_LIBSMI. If it's set, use libsmi, otherwise don't - don't even include smi.h, even if we happened to have found it, and don't print the libsmi version string.
2014-09-01 02:57:04 +08:00
3) { $as_echo "$as_me:${as_lineno-$LINENO}: result: no - can't determine library version" >&5
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
$as_echo "no - can't determine library version" >&6; } ;;
Clean up configure check for libsmi. First, check for smi.h. If we don't have it, don't check for anything else. If we do have it, check for libsmi containing smiInit. If we don't have it, don't check for anything else. If we do have it, check, with our test program, whether we can use it. If that succeeds, prepend -lsmi to LIBS, and set USE_LIBSMI. Otherwise, don't do either of those. Check, in source, *only* for USE_LIBSMI. If it's set, use libsmi, otherwise don't - don't even include smi.h, even if we happened to have found it, and don't print the libsmi version string.
2014-09-01 02:57:04 +08:00
4) { $as_echo "$as_me:${as_lineno-$LINENO}: result: no - too old" >&5
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
$as_echo "no - too old" >&6; } ;;
Clean up configure check for libsmi. First, check for smi.h. If we don't have it, don't check for anything else. If we do have it, check for libsmi containing smiInit. If we don't have it, don't check for anything else. If we do have it, check, with our test program, whether we can use it. If that succeeds, prepend -lsmi to LIBS, and set USE_LIBSMI. Otherwise, don't do either of those. Check, in source, *only* for USE_LIBSMI. If it's set, use libsmi, otherwise don't - don't even include smi.h, even if we happened to have found it, and don't print the libsmi version string.
2014-09-01 02:57:04 +08:00
*) { $as_echo "$as_me:${as_lineno-$LINENO}: result: no" >&5
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
$as_echo "no" >&6; } ;;
Clean up configure check for libsmi. First, check for smi.h. If we don't have it, don't check for anything else. If we do have it, check for libsmi containing smiInit. If we don't have it, don't check for anything else. If we do have it, check, with our test program, whether we can use it. If that succeeds, prepend -lsmi to LIBS, and set USE_LIBSMI. Otherwise, don't do either of those. Check, in source, *only* for USE_LIBSMI. If it's set, use libsmi, otherwise don't - don't even include smi.h, even if we happened to have found it, and don't print the libsmi version string.
2014-09-01 02:57:04 +08:00
esac
LIBS="$savedlibs"
regen
2000-01-08 00:36:57 +08:00
fi
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
rm -f core *.core core.conftest.* gmon.out bb.out conftest$ac_exeext \
conftest.$ac_objext conftest.beam conftest.$ac_ext
Update to rev 1.15 of configure.in
1999-12-15 00:39:39 +08:00
fi
We support building tcpdump with versions of libpcap other than the one with which it was released, and DLT_BLUETOOTH_HCI_H4_WITH_PHDR might be defined by pcap-bpf.h without pcap/bluetooth.h being present (as appears to be the case on Fedora 9, for example), so check whether <pcap/bluetooth.h> is usable. Update a comment - F9 appears to have a "/usr/include/pcap.h" if you install the libpcap headers. When adding -I flags when running a compiler-based test, add them to CPPFLAGS, not CFLAGS - the latter doesn't work right with AC_CHECK_HEADERS, as the "gcc -E" run doesn't have the -I flags added.
2008-09-26 05:45:50 +08:00
Clean up configure check for libsmi. First, check for smi.h. If we don't have it, don't check for anything else. If we do have it, check for libsmi containing smiInit. If we don't have it, don't check for anything else. If we do have it, check, with our test program, whether we can use it. If that succeeds, prepend -lsmi to LIBS, and set USE_LIBSMI. Otherwise, don't do either of those. Check, in source, *only* for USE_LIBSMI. If it's set, use libsmi, otherwise don't - don't even include smi.h, even if we happened to have found it, and don't print the libsmi version string.
2014-09-01 02:57:04 +08:00
Propagate from the git tree: Author: Peter Volkov <pva@gentoo.org> Date: Sun Nov 9 20:33:27 2008 -0500 Currently it's impossible to build tcpdump without libsmi on system with libsmi installed. The patch in attachment adds --with{,out}-smi configure switch which allows to disable it.
2008-11-18 15:39:20 +08:00
fi
Clean up configure check for libsmi. First, check for smi.h. If we don't have it, don't check for anything else. If we do have it, check for libsmi containing smiInit. If we don't have it, don't check for anything else. If we do have it, check, with our test program, whether we can use it. If that succeeds, prepend -lsmi to LIBS, and set USE_LIBSMI. Otherwise, don't do either of those. Check, in source, *only* for USE_LIBSMI. If it's set, use libsmi, otherwise don't - don't even include smi.h, even if we happened to have found it, and don't print the libsmi version string.
2014-09-01 02:57:04 +08:00
Propagate from the git tree: Author: Peter Volkov <pva@gentoo.org> Date: Sun Nov 9 20:33:27 2008 -0500 Currently it's impossible to build tcpdump without libsmi on system with libsmi installed. The patch in attachment adds --with{,out}-smi configure switch which allows to disable it.
2008-11-18 15:39:20 +08:00
fi
Clean up configure check for libsmi. First, check for smi.h. If we don't have it, don't check for anything else. If we do have it, check for libsmi containing smiInit. If we don't have it, don't check for anything else. If we do have it, check, with our test program, whether we can use it. If that succeeds, prepend -lsmi to LIBS, and set USE_LIBSMI. Otherwise, don't do either of those. Check, in source, *only* for USE_LIBSMI. If it's set, use libsmi, otherwise don't - don't even include smi.h, even if we happened to have found it, and don't print the libsmi version string.
2014-09-01 02:57:04 +08:00
Regenerate.
2001-04-27 10:36:16 +08:00
fi
regen
2000-01-08 00:36:57 +08:00
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
{ $as_echo "$as_me:${as_lineno-$LINENO}: checking whether to enable the possibly-buggy SMB printer" >&5
$as_echo_n "checking whether to enable the possibly-buggy SMB printer... " >&6; }
We support building tcpdump with versions of libpcap other than the one with which it was released, and DLT_BLUETOOTH_HCI_H4_WITH_PHDR might be defined by pcap-bpf.h without pcap/bluetooth.h being present (as appears to be the case on Fedora 9, for example), so check whether <pcap/bluetooth.h> is usable. Update a comment - F9 appears to have a "/usr/include/pcap.h" if you install the libpcap headers. When adding -I flags when running a compiler-based test, add them to CPPFLAGS, not CFLAGS - the latter doesn't work right with AC_CHECK_HEADERS, as the "gcc -E" run doesn't have the -I flags added.
2008-09-26 05:45:50 +08:00
# Check whether --enable-smb was given.
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
if test "${enable_smb+set}" = set; then :
We support building tcpdump with versions of libpcap other than the one with which it was released, and DLT_BLUETOOTH_HCI_H4_WITH_PHDR might be defined by pcap-bpf.h without pcap/bluetooth.h being present (as appears to be the case on Fedora 9, for example), so check whether <pcap/bluetooth.h> is usable. Update a comment - F9 appears to have a "/usr/include/pcap.h" if you install the libpcap headers. When adding -I flags when running a compiler-based test, add them to CPPFLAGS, not CFLAGS - the latter doesn't work right with AC_CHECK_HEADERS, as the "gcc -E" run doesn't have the -I flags added.
2008-09-26 05:45:50 +08:00
enableval=$enable_smb;
Enable the SMB dissector by default, now that Bill Fenner's added bounds checking; however, leave in the "possibly buggy" warning and the option to disable it.
2002-01-17 13:00:16 +08:00
else
enableval=yes
We support building tcpdump with versions of libpcap other than the one with which it was released, and DLT_BLUETOOTH_HCI_H4_WITH_PHDR might be defined by pcap-bpf.h without pcap/bluetooth.h being present (as appears to be the case on Fedora 9, for example), so check whether <pcap/bluetooth.h> is usable. Update a comment - F9 appears to have a "/usr/include/pcap.h" if you install the libpcap headers. When adding -I flags when running a compiler-based test, add them to CPPFLAGS, not CFLAGS - the latter doesn't work right with AC_CHECK_HEADERS, as the "gcc -E" run doesn't have the -I flags added.
2008-09-26 05:45:50 +08:00
fi
Enable the SMB dissector by default, now that Bill Fenner's added bounds checking; however, leave in the "possibly buggy" warning and the option to disable it.
2002-01-17 13:00:16 +08:00
case "$enableval" in
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
yes) { $as_echo "$as_me:${as_lineno-$LINENO}: result: yes" >&5
$as_echo "yes" >&6; }
{ $as_echo "$as_me:${as_lineno-$LINENO}: WARNING: The SMB printer may have exploitable buffer overflows!!!" >&5
$as_echo "$as_me: WARNING: The SMB printer may have exploitable buffer overflows!!!" >&2;}
Get rid of acconfig.h.
2013-05-13 06:28:28 +08:00
Get rid of "TCPDUMP" in some libnetdissect codes
2015-10-08 22:36:23 +08:00
$as_echo "#define ENABLE_SMB 1" >>confdefs.h
Regenerate.
2001-10-09 05:25:50 +08:00
LOCALSRC="print-smb.c smbutil.c $LOCALSRC"
;;
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
*) { $as_echo "$as_me:${as_lineno-$LINENO}: result: no" >&5
$as_echo "no" >&6; }
Regenerate.
2001-10-09 05:25:50 +08:00
;;
Enable the SMB dissector by default, now that Bill Fenner's added bounds checking; however, leave in the "possibly buggy" warning and the option to disable it.
2002-01-17 13:00:16 +08:00
esac
Regenerate.
2001-10-09 05:25:50 +08:00
From Andrew Church <andrew@users.sourceforge.net>: when testing for "pcap_version", "pcap_debug", and "yydebug", don't add our own functions referring to those variables - GCC 3.4.1 optimizes the test code out before the link is done, as it's in a function that's not called.
2004-08-27 15:17:03 +08:00
We support building tcpdump with versions of libpcap other than the one with which it was released, and DLT_BLUETOOTH_HCI_H4_WITH_PHDR might be defined by pcap-bpf.h without pcap/bluetooth.h being present (as appears to be the case on Fedora 9, for example), so check whether <pcap/bluetooth.h> is usable. Update a comment - F9 appears to have a "/usr/include/pcap.h" if you install the libpcap headers. When adding -I flags when running a compiler-based test, add them to CPPFLAGS, not CFLAGS - the latter doesn't work right with AC_CHECK_HEADERS, as the "gcc -E" run doesn't have the -I flags added.
2008-09-26 05:45:50 +08:00
# Check whether --with-user was given.
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
if test "${with_user+set}" = set; then :
We support building tcpdump with versions of libpcap other than the one with which it was released, and DLT_BLUETOOTH_HCI_H4_WITH_PHDR might be defined by pcap-bpf.h without pcap/bluetooth.h being present (as appears to be the case on Fedora 9, for example), so check whether <pcap/bluetooth.h> is usable. Update a comment - F9 appears to have a "/usr/include/pcap.h" if you install the libpcap headers. When adding -I flags when running a compiler-based test, add them to CPPFLAGS, not CFLAGS - the latter doesn't work right with AC_CHECK_HEADERS, as the "gcc -E" run doesn't have the -I flags added.
2008-09-26 05:45:50 +08:00
withval=$with_user;
fi
Regenerate.
2004-01-26 08:51:31 +08:00
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
{ $as_echo "$as_me:${as_lineno-$LINENO}: checking whether to drop root privileges by default" >&5
$as_echo_n "checking whether to drop root privileges by default... " >&6; }
Regenerate.
2004-01-26 08:51:31 +08:00
if test ! -z "$with_user" ; then
Get rid of acconfig.h.
2013-05-13 06:28:28 +08:00
cat >>confdefs.h <<_ACEOF
Regenerate.
2004-01-26 08:51:31 +08:00
#define WITH_USER "$withval"
From Andrew Church <andrew@users.sourceforge.net>: when testing for "pcap_version", "pcap_debug", and "yydebug", don't add our own functions referring to those variables - GCC 3.4.1 optimizes the test code out before the link is done, as it's in a function that's not called.
2004-08-27 15:17:03 +08:00
_ACEOF
Regenerate.
2004-01-26 08:51:31 +08:00
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
{ $as_echo "$as_me:${as_lineno-$LINENO}: result: to \"$withval\"" >&5
$as_echo "to \"$withval\"" >&6; }
Regenerate.
2004-01-26 08:51:31 +08:00
else
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
{ $as_echo "$as_me:${as_lineno-$LINENO}: result: no" >&5
$as_echo "no" >&6; }
Regenerate.
2004-01-26 08:51:31 +08:00
fi
From Andrew Church <andrew@users.sourceforge.net>: when testing for "pcap_version", "pcap_debug", and "yydebug", don't add our own functions referring to those variables - GCC 3.4.1 optimizes the test code out before the link is done, as it's in a function that's not called.
2004-08-27 15:17:03 +08:00
We support building tcpdump with versions of libpcap other than the one with which it was released, and DLT_BLUETOOTH_HCI_H4_WITH_PHDR might be defined by pcap-bpf.h without pcap/bluetooth.h being present (as appears to be the case on Fedora 9, for example), so check whether <pcap/bluetooth.h> is usable. Update a comment - F9 appears to have a "/usr/include/pcap.h" if you install the libpcap headers. When adding -I flags when running a compiler-based test, add them to CPPFLAGS, not CFLAGS - the latter doesn't work right with AC_CHECK_HEADERS, as the "gcc -E" run doesn't have the -I flags added.
2008-09-26 05:45:50 +08:00
# Check whether --with-chroot was given.
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
if test "${with_chroot+set}" = set; then :
We support building tcpdump with versions of libpcap other than the one with which it was released, and DLT_BLUETOOTH_HCI_H4_WITH_PHDR might be defined by pcap-bpf.h without pcap/bluetooth.h being present (as appears to be the case on Fedora 9, for example), so check whether <pcap/bluetooth.h> is usable. Update a comment - F9 appears to have a "/usr/include/pcap.h" if you install the libpcap headers. When adding -I flags when running a compiler-based test, add them to CPPFLAGS, not CFLAGS - the latter doesn't work right with AC_CHECK_HEADERS, as the "gcc -E" run doesn't have the -I flags added.
2008-09-26 05:45:50 +08:00
withval=$with_chroot;
fi
Regenerate.
2004-03-12 07:53:33 +08:00
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
{ $as_echo "$as_me:${as_lineno-$LINENO}: checking whether to chroot" >&5
$as_echo_n "checking whether to chroot... " >&6; }
Re-generate configure script.
2010-04-02 14:01:56 +08:00
if test ! -z "$with_chroot" && test "$with_chroot" != "no" ; then
Get rid of acconfig.h.
2013-05-13 06:28:28 +08:00
cat >>confdefs.h <<_ACEOF
Regenerate.
2004-03-12 07:53:33 +08:00
#define WITH_CHROOT "$withval"
From Andrew Church <andrew@users.sourceforge.net>: when testing for "pcap_version", "pcap_debug", and "yydebug", don't add our own functions referring to those variables - GCC 3.4.1 optimizes the test code out before the link is done, as it's in a function that's not called.
2004-08-27 15:17:03 +08:00
_ACEOF
Regenerate.
2004-03-12 07:53:33 +08:00
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
{ $as_echo "$as_me:${as_lineno-$LINENO}: result: to \"$withval\"" >&5
$as_echo "to \"$withval\"" >&6; }
Regenerate.
2004-03-12 07:53:33 +08:00
else
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
{ $as_echo "$as_me:${as_lineno-$LINENO}: result: no" >&5
$as_echo "no" >&6; }
Regenerate.
2004-03-12 07:53:33 +08:00
fi
Add support for FreeBSD capsicum sandboxing.
2014-07-11 03:19:39 +08:00
# Check whether --with-sandbox-capsicum was given.
if test "${with_sandbox_capsicum+set}" = set; then :
withval=$with_sandbox_capsicum;
fi
#
# Check whether various functions are available. If any are, set
# ac_lbl_capsicum_function_seen to yes; if any are not, set
# ac_lbl_capsicum_function_not_seen to yes.
#
Regenerate configure script.
2014-12-20 05:38:54 +08:00
# We don't check cap_rights_init(), as it's a macro, wrapping another
# function, in at least some versions of FreeBSD, and AC_CHECK_FUNCS()
# doesn't handle that.
#
# All of the ones we check for must be available in order to enable
# capsicum sandboxing.
Add support for FreeBSD capsicum sandboxing.
2014-07-11 03:19:39 +08:00
#
Assume non-buggy getaddrinfo() when cross-compiling. The cross target is probably some flavor of Linux (this includes Android) or *BSD (or maybe iOS if you're building for a jailbroken system), and those should have non-buggy getaddrinfo(). If somebody's cross-compiling for a target with a buggy getaddrinfo(), and tcpdump incorrectly converting IPv6 addresses to host names causes the universe to collapse into a giant black hole or something equally horrible, too bad. Expand a comment while we're at it.
2014-12-20 05:44:21 +08:00
# XXX - do we need to check for all of them, or are there some that, if
# present, imply others are present?
#
Add support for FreeBSD capsicum sandboxing.
2014-07-11 03:19:39 +08:00
if test ! -z "$with_sandbox-capsicum" && test "$with_sandbox-capsicum" != "no" ; then
Regenerate configure script.
2014-12-20 05:38:54 +08:00
for ac_func in cap_enter cap_rights_limit cap_ioctls_limit openat
Add support for FreeBSD capsicum sandboxing.
2014-07-11 03:19:39 +08:00
do :
as_ac_var=`$as_echo "ac_cv_func_$ac_func" | $as_tr_sh`
ac_fn_c_check_func "$LINENO" "$ac_func" "$as_ac_var"
if eval test \"x\$"$as_ac_var"\" = x"yes"; then :
cat >>confdefs.h <<_ACEOF
#define `$as_echo "HAVE_$ac_func" | $as_tr_cpp` 1
_ACEOF
ac_lbl_capsicum_function_seen=yes
else
ac_lbl_capsicum_function_not_seen=yes
fi
done
Add support for libcasper library available on FreeBSD 11.0 and newer. The patch allows tcpdump to run sandboxed and still do name resolution. The code is obtained from FreeBSD tree, where it was developed by Pawel Jakub Dawidek <pjd@FreeBSD.org> Mariusz Zaborski <oshogbo@FreeBSD.org>
2017-02-02 08:13:05 +08:00
{ $as_echo "$as_me:${as_lineno-$LINENO}: checking for cap_init in -lcasper" >&5
$as_echo_n "checking for cap_init in -lcasper... " >&6; }
if ${ac_cv_lib_casper_cap_init+:} false; then :
$as_echo_n "(cached) " >&6
else
ac_check_lib_save_LIBS=$LIBS
LIBS="-lcasper $LIBS"
cat confdefs.h - <<_ACEOF >conftest.$ac_ext
/* end confdefs.h. */
/* Override any GCC internal prototype to avoid an error.
Use char because int might match the return type of a GCC
builtin and then its argument prototype would still apply. */
#ifdef __cplusplus
extern "C"
#endif
char cap_init ();
int
main ()
{
return cap_init ();
;
return 0;
}
_ACEOF
if ac_fn_c_try_link "$LINENO"; then :
ac_cv_lib_casper_cap_init=yes
else
ac_cv_lib_casper_cap_init=no
fi
rm -f core conftest.err conftest.$ac_objext \
conftest$ac_exeext conftest.$ac_ext
LIBS=$ac_check_lib_save_LIBS
fi
{ $as_echo "$as_me:${as_lineno-$LINENO}: result: $ac_cv_lib_casper_cap_init" >&5
$as_echo "$ac_cv_lib_casper_cap_init" >&6; }
if test "x$ac_cv_lib_casper_cap_init" = xyes; then :
LIBS="$LIBS -lcasper"
fi
{ $as_echo "$as_me:${as_lineno-$LINENO}: checking for cap_gethostbyaddr in -lcap_dns" >&5
$as_echo_n "checking for cap_gethostbyaddr in -lcap_dns... " >&6; }
if ${ac_cv_lib_cap_dns_cap_gethostbyaddr+:} false; then :
$as_echo_n "(cached) " >&6
else
ac_check_lib_save_LIBS=$LIBS
LIBS="-lcap_dns $LIBS"
cat confdefs.h - <<_ACEOF >conftest.$ac_ext
/* end confdefs.h. */
/* Override any GCC internal prototype to avoid an error.
Use char because int might match the return type of a GCC
builtin and then its argument prototype would still apply. */
#ifdef __cplusplus
extern "C"
#endif
char cap_gethostbyaddr ();
int
main ()
{
return cap_gethostbyaddr ();
;
return 0;
}
_ACEOF
if ac_fn_c_try_link "$LINENO"; then :
ac_cv_lib_cap_dns_cap_gethostbyaddr=yes
else
ac_cv_lib_cap_dns_cap_gethostbyaddr=no
fi
rm -f core conftest.err conftest.$ac_objext \
conftest$ac_exeext conftest.$ac_ext
LIBS=$ac_check_lib_save_LIBS
fi
{ $as_echo "$as_me:${as_lineno-$LINENO}: result: $ac_cv_lib_cap_dns_cap_gethostbyaddr" >&5
$as_echo "$ac_cv_lib_cap_dns_cap_gethostbyaddr" >&6; }
if test "x$ac_cv_lib_cap_dns_cap_gethostbyaddr" = xyes; then :
LIBS="$LIBS -lcap_dns"
fi
Add support for FreeBSD capsicum sandboxing.
2014-07-11 03:19:39 +08:00
fi
{ $as_echo "$as_me:${as_lineno-$LINENO}: checking whether to sandbox using capsicum" >&5
$as_echo_n "checking whether to sandbox using capsicum... " >&6; }
if test "x$ac_lbl_capsicum_function_seen" = "xyes" -a "x$ac_lbl_capsicum_function_not_seen" != "xyes"; then
$as_echo "#define HAVE_CAPSICUM 1" >>confdefs.h
{ $as_echo "$as_me:${as_lineno-$LINENO}: result: yes" >&5
$as_echo "yes" >&6; }
else
{ $as_echo "$as_me:${as_lineno-$LINENO}: result: no" >&5
$as_echo "no" >&6; }
fi
Add support for libcasper library available on FreeBSD 11.0 and newer. The patch allows tcpdump to run sandboxed and still do name resolution. The code is obtained from FreeBSD tree, where it was developed by Pawel Jakub Dawidek <pjd@FreeBSD.org> Mariusz Zaborski <oshogbo@FreeBSD.org>
2017-02-02 08:13:05 +08:00
{ $as_echo "$as_me:${as_lineno-$LINENO}: checking whether to sandbox using Casper library" >&5
$as_echo_n "checking whether to sandbox using Casper library... " >&6; }
if test "x$ac_cv_lib_casper_cap_init" = "xyes" -a "x$ac_cv_lib_cap_dns_cap_gethostbyaddr" = "xyes"; then
$as_echo "#define HAVE_CASPER 1" >>confdefs.h
{ $as_echo "$as_me:${as_lineno-$LINENO}: result: yes" >&5
$as_echo "yes" >&6; }
else
{ $as_echo "$as_me:${as_lineno-$LINENO}: result: no" >&5
$as_echo "no" >&6; }
fi
Add support for FreeBSD capsicum sandboxing.
2014-07-11 03:19:39 +08:00
Check for extra networking libraries before checking for IPv6. On some platforms, such as SunOS 5.x, building the "do we have IPv6 support?" test program requires the extra networking libraries, so we need to know what extra networking libraries are required before doing that test.
2013-04-07 04:03:58 +08:00
#
Don't require IPv6 library support in order to support IPv6 addresses. Have our own routines to convert between IPv4/IPv6 addresses and strings; that helps if, for example, we want to build binary versions of tcpdump for Windows that can run both on NT 5 (W2K/WXP), which doesn't have inet_ntop() or inet_pton(), and NT 6 (Vista/7/8/10), which do. It also means that we don't require IPv6 library support on UN*X to print addresses (if somebody wants to build tcpdump for older UN*Xes lacking IPv6 support in the system library or in add-on libraries). Get rid of files in the missing directory that we don't need, and various no-longer-necessary autoconf tests.
2015-09-18 05:56:44 +08:00
# We must check this before checking whether to check the OS's IPv6,
# support because, on some platforms (such as SunOS 5.x), the test
# program requires the extra networking libraries.
Check for extra networking libraries before checking for IPv6. On some platforms, such as SunOS 5.x, building the "do we have IPv6 support?" test program requires the extra networking libraries, so we need to know what extra networking libraries are required before doing that test.
2013-04-07 04:03:58 +08:00
#
Bring in KAME IPv6 tcpdump. replaces esp/ah/isakmp decoder. Hope I did not break anything. Portability on IPv4-only node needs checking, I'll do this very soon. (sorry for rather jumbo commit) XXx what is _FAVOR_BSD?
1999-10-30 13:11:06 +08:00
Check for extra networking libraries before checking for IPv6. On some platforms, such as SunOS 5.x, building the "do we have IPv6 support?" test program requires the extra networking libraries, so we need to know what extra networking libraries are required before doing that test.
2013-04-07 04:03:58 +08:00
# Most operating systems have gethostbyname() in the default searched
# libraries (i.e. libc):
# Some OSes (eg. Solaris) place it in libnsl
# Some strange OSes (SINIX) have it in libsocket:
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
{ $as_echo "$as_me:${as_lineno-$LINENO}: checking for library containing gethostbyname" >&5
$as_echo_n "checking for library containing gethostbyname... " >&6; }
if ${ac_cv_search_gethostbyname+:} false; then :
$as_echo_n "(cached) " >&6
Bring in KAME IPv6 tcpdump. replaces esp/ah/isakmp decoder. Hope I did not break anything. Portability on IPv4-only node needs checking, I'll do this very soon. (sorry for rather jumbo commit) XXx what is _FAVOR_BSD?
1999-10-30 13:11:06 +08:00
else
Check for extra networking libraries before checking for IPv6. On some platforms, such as SunOS 5.x, building the "do we have IPv6 support?" test program requires the extra networking libraries, so we need to know what extra networking libraries are required before doing that test.
2013-04-07 04:03:58 +08:00
ac_func_search_save_LIBS=$LIBS
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
cat confdefs.h - <<_ACEOF >conftest.$ac_ext
From Andrew Church <andrew@users.sourceforge.net>: when testing for "pcap_version", "pcap_debug", and "yydebug", don't add our own functions referring to those variables - GCC 3.4.1 optimizes the test code out before the link is done, as it's in a function that's not called.
2004-08-27 15:17:03 +08:00
/* end confdefs.h. */
Check for extra networking libraries before checking for IPv6. On some platforms, such as SunOS 5.x, building the "do we have IPv6 support?" test program requires the extra networking libraries, so we need to know what extra networking libraries are required before doing that test.
2013-04-07 04:03:58 +08:00
/* Override any GCC internal prototype to avoid an error.
Use char because int might match the return type of a GCC
builtin and then its argument prototype would still apply. */
#ifdef __cplusplus
extern "C"
#endif
char gethostbyname ();
int
main ()
Bring in KAME IPv6 tcpdump. replaces esp/ah/isakmp decoder. Hope I did not break anything. Portability on IPv4-only node needs checking, I'll do this very soon. (sorry for rather jumbo commit) XXx what is _FAVOR_BSD?
1999-10-30 13:11:06 +08:00
{
Check for extra networking libraries before checking for IPv6. On some platforms, such as SunOS 5.x, building the "do we have IPv6 support?" test program requires the extra networking libraries, so we need to know what extra networking libraries are required before doing that test.
2013-04-07 04:03:58 +08:00
return gethostbyname ();
;
return 0;
Bring in KAME IPv6 tcpdump. replaces esp/ah/isakmp decoder. Hope I did not break anything. Portability on IPv4-only node needs checking, I'll do this very soon. (sorry for rather jumbo commit) XXx what is _FAVOR_BSD?
1999-10-30 13:11:06 +08:00
}
Regenerate with autoconf 2.57.
2004-01-14 11:15:08 +08:00
_ACEOF
Check for extra networking libraries before checking for IPv6. On some platforms, such as SunOS 5.x, building the "do we have IPv6 support?" test program requires the extra networking libraries, so we need to know what extra networking libraries are required before doing that test.
2013-04-07 04:03:58 +08:00
for ac_lib in '' nsl socket resolv; do
if test -z "$ac_lib"; then
ac_res="none required"
else
ac_res=-l$ac_lib
LIBS="-l$ac_lib $ac_func_search_save_LIBS"
fi
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
if ac_fn_c_try_link "$LINENO"; then :
Check for extra networking libraries before checking for IPv6. On some platforms, such as SunOS 5.x, building the "do we have IPv6 support?" test program requires the extra networking libraries, so we need to know what extra networking libraries are required before doing that test.
2013-04-07 04:03:58 +08:00
ac_cv_search_gethostbyname=$ac_res
Bring in KAME IPv6 tcpdump. replaces esp/ah/isakmp decoder. Hope I did not break anything. Portability on IPv4-only node needs checking, I'll do this very soon. (sorry for rather jumbo commit) XXx what is _FAVOR_BSD?
1999-10-30 13:11:06 +08:00
fi
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
rm -f core conftest.err conftest.$ac_objext \
conftest$ac_exeext
if ${ac_cv_search_gethostbyname+:} false; then :
Check for extra networking libraries before checking for IPv6. On some platforms, such as SunOS 5.x, building the "do we have IPv6 support?" test program requires the extra networking libraries, so we need to know what extra networking libraries are required before doing that test.
2013-04-07 04:03:58 +08:00
break
Bring in KAME IPv6 tcpdump. replaces esp/ah/isakmp decoder. Hope I did not break anything. Portability on IPv4-only node needs checking, I'll do this very soon. (sorry for rather jumbo commit) XXx what is _FAVOR_BSD?
1999-10-30 13:11:06 +08:00
fi
Check for extra networking libraries before checking for IPv6. On some platforms, such as SunOS 5.x, building the "do we have IPv6 support?" test program requires the extra networking libraries, so we need to know what extra networking libraries are required before doing that test.
2013-04-07 04:03:58 +08:00
done
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
if ${ac_cv_search_gethostbyname+:} false; then :
Check for extra networking libraries before checking for IPv6. On some platforms, such as SunOS 5.x, building the "do we have IPv6 support?" test program requires the extra networking libraries, so we need to know what extra networking libraries are required before doing that test.
2013-04-07 04:03:58 +08:00
else
ac_cv_search_gethostbyname=no
Bring in KAME IPv6 tcpdump. replaces esp/ah/isakmp decoder. Hope I did not break anything. Portability on IPv4-only node needs checking, I'll do this very soon. (sorry for rather jumbo commit) XXx what is _FAVOR_BSD?
1999-10-30 13:11:06 +08:00
fi
Check for extra networking libraries before checking for IPv6. On some platforms, such as SunOS 5.x, building the "do we have IPv6 support?" test program requires the extra networking libraries, so we need to know what extra networking libraries are required before doing that test.
2013-04-07 04:03:58 +08:00
rm conftest.$ac_ext
LIBS=$ac_func_search_save_LIBS
Bring in KAME IPv6 tcpdump. replaces esp/ah/isakmp decoder. Hope I did not break anything. Portability on IPv4-only node needs checking, I'll do this very soon. (sorry for rather jumbo commit) XXx what is _FAVOR_BSD?
1999-10-30 13:11:06 +08:00
fi
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
{ $as_echo "$as_me:${as_lineno-$LINENO}: result: $ac_cv_search_gethostbyname" >&5
$as_echo "$ac_cv_search_gethostbyname" >&6; }
Check for extra networking libraries before checking for IPv6. On some platforms, such as SunOS 5.x, building the "do we have IPv6 support?" test program requires the extra networking libraries, so we need to know what extra networking libraries are required before doing that test.
2013-04-07 04:03:58 +08:00
ac_res=$ac_cv_search_gethostbyname
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
if test "$ac_res" != no; then :
Check for extra networking libraries before checking for IPv6. On some platforms, such as SunOS 5.x, building the "do we have IPv6 support?" test program requires the extra networking libraries, so we need to know what extra networking libraries are required before doing that test.
2013-04-07 04:03:58 +08:00
test "$ac_res" = "none required" || LIBS="$ac_res $LIBS"
Bring in KAME IPv6 tcpdump. replaces esp/ah/isakmp decoder. Hope I did not break anything. Portability on IPv4-only node needs checking, I'll do this very soon. (sorry for rather jumbo commit) XXx what is _FAVOR_BSD?
1999-10-30 13:11:06 +08:00
fi
Check for extra networking libraries before checking for IPv6. On some platforms, such as SunOS 5.x, building the "do we have IPv6 support?" test program requires the extra networking libraries, so we need to know what extra networking libraries are required before doing that test.
2013-04-07 04:03:58 +08:00
# Unfortunately libsocket sometimes depends on libnsl and
# AC_SEARCH_LIBS isn't up to the task of handling dependencies like this.
if test "$ac_cv_search_gethostbyname" = "no"
then
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
{ $as_echo "$as_me:${as_lineno-$LINENO}: checking for gethostbyname in -lsocket" >&5
$as_echo_n "checking for gethostbyname in -lsocket... " >&6; }
if ${ac_cv_lib_socket_gethostbyname+:} false; then :
$as_echo_n "(cached) " >&6
Check for extra networking libraries before checking for IPv6. On some platforms, such as SunOS 5.x, building the "do we have IPv6 support?" test program requires the extra networking libraries, so we need to know what extra networking libraries are required before doing that test.
2013-04-07 04:03:58 +08:00
else
ac_check_lib_save_LIBS=$LIBS
LIBS="-lsocket -lnsl $LIBS"
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
cat confdefs.h - <<_ACEOF >conftest.$ac_ext
From Andrew Church <andrew@users.sourceforge.net>: when testing for "pcap_version", "pcap_debug", and "yydebug", don't add our own functions referring to those variables - GCC 3.4.1 optimizes the test code out before the link is done, as it's in a function that's not called.
2004-08-27 15:17:03 +08:00
/* end confdefs.h. */
Check for extra networking libraries before checking for IPv6. On some platforms, such as SunOS 5.x, building the "do we have IPv6 support?" test program requires the extra networking libraries, so we need to know what extra networking libraries are required before doing that test.
2013-04-07 04:03:58 +08:00
/* Override any GCC internal prototype to avoid an error.
Use char because int might match the return type of a GCC
builtin and then its argument prototype would still apply. */
#ifdef __cplusplus
extern "C"
Bring in KAME IPv6 tcpdump. replaces esp/ah/isakmp decoder. Hope I did not break anything. Portability on IPv4-only node needs checking, I'll do this very soon. (sorry for rather jumbo commit) XXx what is _FAVOR_BSD?
1999-10-30 13:11:06 +08:00
#endif
Check for extra networking libraries before checking for IPv6. On some platforms, such as SunOS 5.x, building the "do we have IPv6 support?" test program requires the extra networking libraries, so we need to know what extra networking libraries are required before doing that test.
2013-04-07 04:03:58 +08:00
char gethostbyname ();
int
main ()
{
return gethostbyname ();
;
return 0;
}
Regenerate with autoconf 2.57.
2004-01-14 11:15:08 +08:00
_ACEOF
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
if ac_fn_c_try_link "$LINENO"; then :
Check for extra networking libraries before checking for IPv6. On some platforms, such as SunOS 5.x, building the "do we have IPv6 support?" test program requires the extra networking libraries, so we need to know what extra networking libraries are required before doing that test.
2013-04-07 04:03:58 +08:00
ac_cv_lib_socket_gethostbyname=yes
else
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
ac_cv_lib_socket_gethostbyname=no
Bring in KAME IPv6 tcpdump. replaces esp/ah/isakmp decoder. Hope I did not break anything. Portability on IPv4-only node needs checking, I'll do this very soon. (sorry for rather jumbo commit) XXx what is _FAVOR_BSD?
1999-10-30 13:11:06 +08:00
fi
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
rm -f core conftest.err conftest.$ac_objext \
conftest$ac_exeext conftest.$ac_ext
Check for extra networking libraries before checking for IPv6. On some platforms, such as SunOS 5.x, building the "do we have IPv6 support?" test program requires the extra networking libraries, so we need to know what extra networking libraries are required before doing that test.
2013-04-07 04:03:58 +08:00
LIBS=$ac_check_lib_save_LIBS
fi
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
{ $as_echo "$as_me:${as_lineno-$LINENO}: result: $ac_cv_lib_socket_gethostbyname" >&5
$as_echo "$ac_cv_lib_socket_gethostbyname" >&6; }
if test "x$ac_cv_lib_socket_gethostbyname" = xyes; then :
Check for extra networking libraries before checking for IPv6. On some platforms, such as SunOS 5.x, building the "do we have IPv6 support?" test program requires the extra networking libraries, so we need to know what extra networking libraries are required before doing that test.
2013-04-07 04:03:58 +08:00
LIBS="-lsocket -lnsl $LIBS"
Bring in KAME IPv6 tcpdump. replaces esp/ah/isakmp decoder. Hope I did not break anything. Portability on IPv4-only node needs checking, I'll do this very soon. (sorry for rather jumbo commit) XXx what is _FAVOR_BSD?
1999-10-30 13:11:06 +08:00
fi
Check for extra networking libraries before checking for IPv6. On some platforms, such as SunOS 5.x, building the "do we have IPv6 support?" test program requires the extra networking libraries, so we need to know what extra networking libraries are required before doing that test.
2013-04-07 04:03:58 +08:00
fi
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
{ $as_echo "$as_me:${as_lineno-$LINENO}: checking for library containing socket" >&5
$as_echo_n "checking for library containing socket... " >&6; }
if ${ac_cv_search_socket+:} false; then :
$as_echo_n "(cached) " >&6
Regenerate with autoconf 2.57.
2004-01-14 11:15:08 +08:00
else
ac_func_search_save_LIBS=$LIBS
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
cat confdefs.h - <<_ACEOF >conftest.$ac_ext
From Andrew Church <andrew@users.sourceforge.net>: when testing for "pcap_version", "pcap_debug", and "yydebug", don't add our own functions referring to those variables - GCC 3.4.1 optimizes the test code out before the link is done, as it's in a function that's not called.
2004-08-27 15:17:03 +08:00
/* end confdefs.h. */
Regenerate with autoconf 2.57.
2004-01-14 11:15:08 +08:00
We support building tcpdump with versions of libpcap other than the one with which it was released, and DLT_BLUETOOTH_HCI_H4_WITH_PHDR might be defined by pcap-bpf.h without pcap/bluetooth.h being present (as appears to be the case on Fedora 9, for example), so check whether <pcap/bluetooth.h> is usable. Update a comment - F9 appears to have a "/usr/include/pcap.h" if you install the libpcap headers. When adding -I flags when running a compiler-based test, add them to CPPFLAGS, not CFLAGS - the latter doesn't work right with AC_CHECK_HEADERS, as the "gcc -E" run doesn't have the -I flags added.
2008-09-26 05:45:50 +08:00
/* Override any GCC internal prototype to avoid an error.
Use char because int might match the return type of a GCC
builtin and then its argument prototype would still apply. */
Regenerate with autoconf 2.57.
2004-01-14 11:15:08 +08:00
#ifdef __cplusplus
extern "C"
#endif
Check for extra networking libraries before checking for IPv6. On some platforms, such as SunOS 5.x, building the "do we have IPv6 support?" test program requires the extra networking libraries, so we need to know what extra networking libraries are required before doing that test.
2013-04-07 04:03:58 +08:00
char socket ();
Regenerate with autoconf 2.57.
2004-01-14 11:15:08 +08:00
int
main ()
{
Check for extra networking libraries before checking for IPv6. On some platforms, such as SunOS 5.x, building the "do we have IPv6 support?" test program requires the extra networking libraries, so we need to know what extra networking libraries are required before doing that test.
2013-04-07 04:03:58 +08:00
return socket ();
Regenerate with autoconf 2.57.
2004-01-14 11:15:08 +08:00
;
return 0;
}
_ACEOF
We support building tcpdump with versions of libpcap other than the one with which it was released, and DLT_BLUETOOTH_HCI_H4_WITH_PHDR might be defined by pcap-bpf.h without pcap/bluetooth.h being present (as appears to be the case on Fedora 9, for example), so check whether <pcap/bluetooth.h> is usable. Update a comment - F9 appears to have a "/usr/include/pcap.h" if you install the libpcap headers. When adding -I flags when running a compiler-based test, add them to CPPFLAGS, not CFLAGS - the latter doesn't work right with AC_CHECK_HEADERS, as the "gcc -E" run doesn't have the -I flags added.
2008-09-26 05:45:50 +08:00
for ac_lib in '' socket; do
if test -z "$ac_lib"; then
ac_res="none required"
else
ac_res=-l$ac_lib
LIBS="-l$ac_lib $ac_func_search_save_LIBS"
fi
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
if ac_fn_c_try_link "$LINENO"; then :
Check for extra networking libraries before checking for IPv6. On some platforms, such as SunOS 5.x, building the "do we have IPv6 support?" test program requires the extra networking libraries, so we need to know what extra networking libraries are required before doing that test.
2013-04-07 04:03:58 +08:00
ac_cv_search_socket=$ac_res
fi
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
rm -f core conftest.err conftest.$ac_objext \
conftest$ac_exeext
if ${ac_cv_search_socket+:} false; then :
Check for extra networking libraries before checking for IPv6. On some platforms, such as SunOS 5.x, building the "do we have IPv6 support?" test program requires the extra networking libraries, so we need to know what extra networking libraries are required before doing that test.
2013-04-07 04:03:58 +08:00
break
fi
done
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
if ${ac_cv_search_socket+:} false; then :
Check for extra networking libraries before checking for IPv6. On some platforms, such as SunOS 5.x, building the "do we have IPv6 support?" test program requires the extra networking libraries, so we need to know what extra networking libraries are required before doing that test.
2013-04-07 04:03:58 +08:00
else
ac_cv_search_socket=no
fi
rm conftest.$ac_ext
LIBS=$ac_func_search_save_LIBS
fi
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
{ $as_echo "$as_me:${as_lineno-$LINENO}: result: $ac_cv_search_socket" >&5
$as_echo "$ac_cv_search_socket" >&6; }
Check for extra networking libraries before checking for IPv6. On some platforms, such as SunOS 5.x, building the "do we have IPv6 support?" test program requires the extra networking libraries, so we need to know what extra networking libraries are required before doing that test.
2013-04-07 04:03:58 +08:00
ac_res=$ac_cv_search_socket
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
if test "$ac_res" != no; then :
Check for extra networking libraries before checking for IPv6. On some platforms, such as SunOS 5.x, building the "do we have IPv6 support?" test program requires the extra networking libraries, so we need to know what extra networking libraries are required before doing that test.
2013-04-07 04:03:58 +08:00
test "$ac_res" = "none required" || LIBS="$ac_res $LIBS"
else
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
{ $as_echo "$as_me:${as_lineno-$LINENO}: checking for socket in -lsocket" >&5
$as_echo_n "checking for socket in -lsocket... " >&6; }
if ${ac_cv_lib_socket_socket+:} false; then :
$as_echo_n "(cached) " >&6
Check for extra networking libraries before checking for IPv6. On some platforms, such as SunOS 5.x, building the "do we have IPv6 support?" test program requires the extra networking libraries, so we need to know what extra networking libraries are required before doing that test.
2013-04-07 04:03:58 +08:00
else
ac_check_lib_save_LIBS=$LIBS
LIBS="-lsocket -lnsl $LIBS"
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
cat confdefs.h - <<_ACEOF >conftest.$ac_ext
Check for extra networking libraries before checking for IPv6. On some platforms, such as SunOS 5.x, building the "do we have IPv6 support?" test program requires the extra networking libraries, so we need to know what extra networking libraries are required before doing that test.
2013-04-07 04:03:58 +08:00
/* end confdefs.h. */
/* Override any GCC internal prototype to avoid an error.
Use char because int might match the return type of a GCC
builtin and then its argument prototype would still apply. */
#ifdef __cplusplus
extern "C"
#endif
char socket ();
int
main ()
{
return socket ();
;
return 0;
}
_ACEOF
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
if ac_fn_c_try_link "$LINENO"; then :
Check for extra networking libraries before checking for IPv6. On some platforms, such as SunOS 5.x, building the "do we have IPv6 support?" test program requires the extra networking libraries, so we need to know what extra networking libraries are required before doing that test.
2013-04-07 04:03:58 +08:00
ac_cv_lib_socket_socket=yes
else
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
ac_cv_lib_socket_socket=no
Check for extra networking libraries before checking for IPv6. On some platforms, such as SunOS 5.x, building the "do we have IPv6 support?" test program requires the extra networking libraries, so we need to know what extra networking libraries are required before doing that test.
2013-04-07 04:03:58 +08:00
fi
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
rm -f core conftest.err conftest.$ac_objext \
conftest$ac_exeext conftest.$ac_ext
Check for extra networking libraries before checking for IPv6. On some platforms, such as SunOS 5.x, building the "do we have IPv6 support?" test program requires the extra networking libraries, so we need to know what extra networking libraries are required before doing that test.
2013-04-07 04:03:58 +08:00
LIBS=$ac_check_lib_save_LIBS
fi
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
{ $as_echo "$as_me:${as_lineno-$LINENO}: result: $ac_cv_lib_socket_socket" >&5
$as_echo "$ac_cv_lib_socket_socket" >&6; }
if test "x$ac_cv_lib_socket_socket" = xyes; then :
Check for extra networking libraries before checking for IPv6. On some platforms, such as SunOS 5.x, building the "do we have IPv6 support?" test program requires the extra networking libraries, so we need to know what extra networking libraries are required before doing that test.
2013-04-07 04:03:58 +08:00
LIBS="-lsocket -lnsl $LIBS"
fi
fi
# DLPI needs putmsg under HPUX so test for -lstr while we're at it
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
{ $as_echo "$as_me:${as_lineno-$LINENO}: checking for library containing putmsg" >&5
$as_echo_n "checking for library containing putmsg... " >&6; }
if ${ac_cv_search_putmsg+:} false; then :
$as_echo_n "(cached) " >&6
Check for extra networking libraries before checking for IPv6. On some platforms, such as SunOS 5.x, building the "do we have IPv6 support?" test program requires the extra networking libraries, so we need to know what extra networking libraries are required before doing that test.
2013-04-07 04:03:58 +08:00
else
ac_func_search_save_LIBS=$LIBS
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
cat confdefs.h - <<_ACEOF >conftest.$ac_ext
Check for extra networking libraries before checking for IPv6. On some platforms, such as SunOS 5.x, building the "do we have IPv6 support?" test program requires the extra networking libraries, so we need to know what extra networking libraries are required before doing that test.
2013-04-07 04:03:58 +08:00
/* end confdefs.h. */
/* Override any GCC internal prototype to avoid an error.
Use char because int might match the return type of a GCC
builtin and then its argument prototype would still apply. */
#ifdef __cplusplus
extern "C"
#endif
char putmsg ();
int
main ()
{
return putmsg ();
;
return 0;
}
_ACEOF
for ac_lib in '' str; do
if test -z "$ac_lib"; then
ac_res="none required"
else
ac_res=-l$ac_lib
LIBS="-l$ac_lib $ac_func_search_save_LIBS"
fi
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
if ac_fn_c_try_link "$LINENO"; then :
Check for extra networking libraries before checking for IPv6. On some platforms, such as SunOS 5.x, building the "do we have IPv6 support?" test program requires the extra networking libraries, so we need to know what extra networking libraries are required before doing that test.
2013-04-07 04:03:58 +08:00
ac_cv_search_putmsg=$ac_res
fi
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
rm -f core conftest.err conftest.$ac_objext \
conftest$ac_exeext
if ${ac_cv_search_putmsg+:} false; then :
Check for extra networking libraries before checking for IPv6. On some platforms, such as SunOS 5.x, building the "do we have IPv6 support?" test program requires the extra networking libraries, so we need to know what extra networking libraries are required before doing that test.
2013-04-07 04:03:58 +08:00
break
fi
done
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
if ${ac_cv_search_putmsg+:} false; then :
Check for extra networking libraries before checking for IPv6. On some platforms, such as SunOS 5.x, building the "do we have IPv6 support?" test program requires the extra networking libraries, so we need to know what extra networking libraries are required before doing that test.
2013-04-07 04:03:58 +08:00
else
ac_cv_search_putmsg=no
fi
rm conftest.$ac_ext
LIBS=$ac_func_search_save_LIBS
fi
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
{ $as_echo "$as_me:${as_lineno-$LINENO}: result: $ac_cv_search_putmsg" >&5
$as_echo "$ac_cv_search_putmsg" >&6; }
Check for extra networking libraries before checking for IPv6. On some platforms, such as SunOS 5.x, building the "do we have IPv6 support?" test program requires the extra networking libraries, so we need to know what extra networking libraries are required before doing that test.
2013-04-07 04:03:58 +08:00
ac_res=$ac_cv_search_putmsg
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
if test "$ac_res" != no; then :
We support building tcpdump with versions of libpcap other than the one with which it was released, and DLT_BLUETOOTH_HCI_H4_WITH_PHDR might be defined by pcap-bpf.h without pcap/bluetooth.h being present (as appears to be the case on Fedora 9, for example), so check whether <pcap/bluetooth.h> is usable. Update a comment - F9 appears to have a "/usr/include/pcap.h" if you install the libpcap headers. When adding -I flags when running a compiler-based test, add them to CPPFLAGS, not CFLAGS - the latter doesn't work right with AC_CHECK_HEADERS, as the "gcc -E" run doesn't have the -I flags added.
2008-09-26 05:45:50 +08:00
test "$ac_res" = "none required" || LIBS="$ac_res $LIBS"
Check for extra networking libraries before checking for IPv6. On some platforms, such as SunOS 5.x, building the "do we have IPv6 support?" test program requires the extra networking libraries, so we need to know what extra networking libraries are required before doing that test.
2013-04-07 04:03:58 +08:00
fi
Don't require IPv6 library support in order to support IPv6 addresses. Have our own routines to convert between IPv4/IPv6 addresses and strings; that helps if, for example, we want to build binary versions of tcpdump for Windows that can run both on NT 5 (W2K/WXP), which doesn't have inet_ntop() or inet_pton(), and NT 6 (Vista/7/8/10), which do. It also means that we don't require IPv6 library support on UN*X to print addresses (if somebody wants to build tcpdump for older UN*Xes lacking IPv6 support in the system library or in add-on libraries). Get rid of files in the missing directory that we don't need, and various no-longer-necessary autoconf tests.
2015-09-18 05:56:44 +08:00
#
# Check whether AF_INET6 and struct in6_addr are defined.
# If they aren't both defined, we don't have sufficient OS
# support for IPv6, so we don't look for IPv6 support libraries,
# and we define AF_INET6 and struct in6_addr ourselves.
#
{ $as_echo "$as_me:${as_lineno-$LINENO}: checking whether the operating system supports IPv6" >&5
$as_echo_n "checking whether the operating system supports IPv6... " >&6; }
cat confdefs.h - <<_ACEOF >conftest.$ac_ext
Check for extra networking libraries before checking for IPv6. On some platforms, such as SunOS 5.x, building the "do we have IPv6 support?" test program requires the extra networking libraries, so we need to know what extra networking libraries are required before doing that test.
2013-04-07 04:03:58 +08:00
/* end confdefs.h. */
Check for compiling for IPv6; don't check whether we can create an IPv6 socket. Don't check whether we can create a TCP-over-IPv6 socket; that appears to fail in some cases where tcpdump can be built with IPv6 support. Instead, just check whether AF_INET6 and struct in6_addr are defined.
2014-01-18 06:08:39 +08:00
Don't require IPv6 library support in order to support IPv6 addresses. Have our own routines to convert between IPv4/IPv6 addresses and strings; that helps if, for example, we want to build binary versions of tcpdump for Windows that can run both on NT 5 (W2K/WXP), which doesn't have inet_ntop() or inet_pton(), and NT 6 (Vista/7/8/10), which do. It also means that we don't require IPv6 library support on UN*X to print addresses (if somebody wants to build tcpdump for older UN*Xes lacking IPv6 support in the system library or in add-on libraries). Get rid of files in the missing directory that we don't need, and various no-longer-necessary autoconf tests.
2015-09-18 05:56:44 +08:00
/* AF_INET6 available check */
Check for extra networking libraries before checking for IPv6. On some platforms, such as SunOS 5.x, building the "do we have IPv6 support?" test program requires the extra networking libraries, so we need to know what extra networking libraries are required before doing that test.
2013-04-07 04:03:58 +08:00
#include <sys/types.h>
improved check for ipv6 support on windows (autotools)
2017-11-06 06:42:13 +08:00
#ifdef _WIN32
#include <ws2tcpip.h>
#else
Check for extra networking libraries before checking for IPv6. On some platforms, such as SunOS 5.x, building the "do we have IPv6 support?" test program requires the extra networking libraries, so we need to know what extra networking libraries are required before doing that test.
2013-04-07 04:03:58 +08:00
#include <sys/socket.h>
Check for compiling for IPv6; don't check whether we can create an IPv6 socket. Don't check whether we can create a TCP-over-IPv6 socket; that appears to fail in some cases where tcpdump can be built with IPv6 support. Instead, just check whether AF_INET6 and struct in6_addr are defined.
2014-01-18 06:08:39 +08:00
#include <netinet/in.h>
improved check for ipv6 support on windows (autotools)
2017-11-06 06:42:13 +08:00
#endif
Check for compiling for IPv6; don't check whether we can create an IPv6 socket. Don't check whether we can create a TCP-over-IPv6 socket; that appears to fail in some cases where tcpdump can be built with IPv6 support. Instead, just check whether AF_INET6 and struct in6_addr are defined.
2014-01-18 06:08:39 +08:00
#ifdef AF_INET6
void
foo(struct in6_addr *addr)
Check for extra networking libraries before checking for IPv6. On some platforms, such as SunOS 5.x, building the "do we have IPv6 support?" test program requires the extra networking libraries, so we need to know what extra networking libraries are required before doing that test.
2013-04-07 04:03:58 +08:00
{
Check for compiling for IPv6; don't check whether we can create an IPv6 socket. Don't check whether we can create a TCP-over-IPv6 socket; that appears to fail in some cases where tcpdump can be built with IPv6 support. Instead, just check whether AF_INET6 and struct in6_addr are defined.
2014-01-18 06:08:39 +08:00
memset(addr, 0, sizeof (struct in6_addr));
Check for extra networking libraries before checking for IPv6. On some platforms, such as SunOS 5.x, building the "do we have IPv6 support?" test program requires the extra networking libraries, so we need to know what extra networking libraries are required before doing that test.
2013-04-07 04:03:58 +08:00
}
Check for compiling for IPv6; don't check whether we can create an IPv6 socket. Don't check whether we can create a TCP-over-IPv6 socket; that appears to fail in some cases where tcpdump can be built with IPv6 support. Instead, just check whether AF_INET6 and struct in6_addr are defined.
2014-01-18 06:08:39 +08:00
#else
#error "AF_INET6 not defined"
#endif
Check for extra networking libraries before checking for IPv6. On some platforms, such as SunOS 5.x, building the "do we have IPv6 support?" test program requires the extra networking libraries, so we need to know what extra networking libraries are required before doing that test.
2013-04-07 04:03:58 +08:00
_ACEOF
Check for compiling for IPv6; don't check whether we can create an IPv6 socket. Don't check whether we can create a TCP-over-IPv6 socket; that appears to fail in some cases where tcpdump can be built with IPv6 support. Instead, just check whether AF_INET6 and struct in6_addr are defined.
2014-01-18 06:08:39 +08:00
if ac_fn_c_try_compile "$LINENO"; then :
Don't require IPv6 library support in order to support IPv6 addresses. Have our own routines to convert between IPv4/IPv6 addresses and strings; that helps if, for example, we want to build binary versions of tcpdump for Windows that can run both on NT 5 (W2K/WXP), which doesn't have inet_ntop() or inet_pton(), and NT 6 (Vista/7/8/10), which do. It also means that we don't require IPv6 library support on UN*X to print addresses (if somebody wants to build tcpdump for older UN*Xes lacking IPv6 support in the system library or in add-on libraries). Get rid of files in the missing directory that we don't need, and various no-longer-necessary autoconf tests.
2015-09-18 05:56:44 +08:00
{ $as_echo "$as_me:${as_lineno-$LINENO}: result: yes" >&5
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
$as_echo "yes" >&6; }
Get rid of acconfig.h.
2013-05-13 06:28:28 +08:00
Don't require IPv6 library support in order to support IPv6 addresses. Have our own routines to convert between IPv4/IPv6 addresses and strings; that helps if, for example, we want to build binary versions of tcpdump for Windows that can run both on NT 5 (W2K/WXP), which doesn't have inet_ntop() or inet_pton(), and NT 6 (Vista/7/8/10), which do. It also means that we don't require IPv6 library support on UN*X to print addresses (if somebody wants to build tcpdump for older UN*Xes lacking IPv6 support in the system library or in add-on libraries). Get rid of files in the missing directory that we don't need, and various no-longer-necessary autoconf tests.
2015-09-18 05:56:44 +08:00
$as_echo "#define HAVE_OS_IPV6_SUPPORT 1" >>confdefs.h
ipv6=yes
Check for extra networking libraries before checking for IPv6. On some platforms, such as SunOS 5.x, building the "do we have IPv6 support?" test program requires the extra networking libraries, so we need to know what extra networking libraries are required before doing that test.
2013-04-07 04:03:58 +08:00
else
Don't require IPv6 library support in order to support IPv6 addresses. Have our own routines to convert between IPv4/IPv6 addresses and strings; that helps if, for example, we want to build binary versions of tcpdump for Windows that can run both on NT 5 (W2K/WXP), which doesn't have inet_ntop() or inet_pton(), and NT 6 (Vista/7/8/10), which do. It also means that we don't require IPv6 library support on UN*X to print addresses (if somebody wants to build tcpdump for older UN*Xes lacking IPv6 support in the system library or in add-on libraries). Get rid of files in the missing directory that we don't need, and various no-longer-necessary autoconf tests.
2015-09-18 05:56:44 +08:00
{ $as_echo "$as_me:${as_lineno-$LINENO}: result: no" >&5
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
$as_echo "no" >&6; }
Don't require IPv6 library support in order to support IPv6 addresses. Have our own routines to convert between IPv4/IPv6 addresses and strings; that helps if, for example, we want to build binary versions of tcpdump for Windows that can run both on NT 5 (W2K/WXP), which doesn't have inet_ntop() or inet_pton(), and NT 6 (Vista/7/8/10), which do. It also means that we don't require IPv6 library support on UN*X to print addresses (if somebody wants to build tcpdump for older UN*Xes lacking IPv6 support in the system library or in add-on libraries). Get rid of files in the missing directory that we don't need, and various no-longer-necessary autoconf tests.
2015-09-18 05:56:44 +08:00
ipv6=no
Check for extra networking libraries before checking for IPv6. On some platforms, such as SunOS 5.x, building the "do we have IPv6 support?" test program requires the extra networking libraries, so we need to know what extra networking libraries are required before doing that test.
2013-04-07 04:03:58 +08:00
fi
Check for compiling for IPv6; don't check whether we can create an IPv6 socket. Don't check whether we can create a TCP-over-IPv6 socket; that appears to fail in some cases where tcpdump can be built with IPv6 support. Instead, just check whether AF_INET6 and struct in6_addr are defined.
2014-01-18 06:08:39 +08:00
rm -f core conftest.err conftest.$ac_objext conftest.$ac_ext
Check for extra networking libraries before checking for IPv6. On some platforms, such as SunOS 5.x, building the "do we have IPv6 support?" test program requires the extra networking libraries, so we need to know what extra networking libraries are required before doing that test.
2013-04-07 04:03:58 +08:00
ipv6type=unknown
ipv6lib=none
ipv6trylibc=no
if test "$ipv6" = "yes"; then
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
{ $as_echo "$as_me:${as_lineno-$LINENO}: checking ipv6 stack type" >&5
$as_echo_n "checking ipv6 stack type... " >&6; }
Check for extra networking libraries before checking for IPv6. On some platforms, such as SunOS 5.x, building the "do we have IPv6 support?" test program requires the extra networking libraries, so we need to know what extra networking libraries are required before doing that test.
2013-04-07 04:03:58 +08:00
for i in inria kame linux-glibc linux-libinet6 toshiba v6d zeta; do
case $i in
inria)
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
cat confdefs.h - <<_ACEOF >conftest.$ac_ext
Check for extra networking libraries before checking for IPv6. On some platforms, such as SunOS 5.x, building the "do we have IPv6 support?" test program requires the extra networking libraries, so we need to know what extra networking libraries are required before doing that test.
2013-04-07 04:03:58 +08:00
/* end confdefs.h. */
#include <netinet/in.h>
#ifdef IPV6_INRIA_VERSION
yes
#endif
_ACEOF
if (eval "$ac_cpp conftest.$ac_ext") 2>&5 |
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
$EGREP "yes" >/dev/null 2>&1; then :
Don't require IPv6 library support in order to support IPv6 addresses. Have our own routines to convert between IPv4/IPv6 addresses and strings; that helps if, for example, we want to build binary versions of tcpdump for Windows that can run both on NT 5 (W2K/WXP), which doesn't have inet_ntop() or inet_pton(), and NT 6 (Vista/7/8/10), which do. It also means that we don't require IPv6 library support on UN*X to print addresses (if somebody wants to build tcpdump for older UN*Xes lacking IPv6 support in the system library or in add-on libraries). Get rid of files in the missing directory that we don't need, and various no-longer-necessary autoconf tests.
2015-09-18 05:56:44 +08:00
ipv6type=$i
Check for extra networking libraries before checking for IPv6. On some platforms, such as SunOS 5.x, building the "do we have IPv6 support?" test program requires the extra networking libraries, so we need to know what extra networking libraries are required before doing that test.
2013-04-07 04:03:58 +08:00
fi
rm -f conftest*
;;
kame)
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
cat confdefs.h - <<_ACEOF >conftest.$ac_ext
Check for extra networking libraries before checking for IPv6. On some platforms, such as SunOS 5.x, building the "do we have IPv6 support?" test program requires the extra networking libraries, so we need to know what extra networking libraries are required before doing that test.
2013-04-07 04:03:58 +08:00
/* end confdefs.h. */
#include <netinet/in.h>
#ifdef __KAME__
yes
#endif
_ACEOF
if (eval "$ac_cpp conftest.$ac_ext") 2>&5 |
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
$EGREP "yes" >/dev/null 2>&1; then :
Check for extra networking libraries before checking for IPv6. On some platforms, such as SunOS 5.x, building the "do we have IPv6 support?" test program requires the extra networking libraries, so we need to know what extra networking libraries are required before doing that test.
2013-04-07 04:03:58 +08:00
ipv6type=$i;
ipv6lib=inet6;
ipv6libdir=/usr/local/v6/lib;
Don't require IPv6 library support in order to support IPv6 addresses. Have our own routines to convert between IPv4/IPv6 addresses and strings; that helps if, for example, we want to build binary versions of tcpdump for Windows that can run both on NT 5 (W2K/WXP), which doesn't have inet_ntop() or inet_pton(), and NT 6 (Vista/7/8/10), which do. It also means that we don't require IPv6 library support on UN*X to print addresses (if somebody wants to build tcpdump for older UN*Xes lacking IPv6 support in the system library or in add-on libraries). Get rid of files in the missing directory that we don't need, and various no-longer-necessary autoconf tests.
2015-09-18 05:56:44 +08:00
ipv6trylibc=yes
Check for extra networking libraries before checking for IPv6. On some platforms, such as SunOS 5.x, building the "do we have IPv6 support?" test program requires the extra networking libraries, so we need to know what extra networking libraries are required before doing that test.
2013-04-07 04:03:58 +08:00
fi
rm -f conftest*
;;
linux-glibc)
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
cat confdefs.h - <<_ACEOF >conftest.$ac_ext
Check for extra networking libraries before checking for IPv6. On some platforms, such as SunOS 5.x, building the "do we have IPv6 support?" test program requires the extra networking libraries, so we need to know what extra networking libraries are required before doing that test.
2013-04-07 04:03:58 +08:00
/* end confdefs.h. */
#include <features.h>
#if defined(__GLIBC__) && __GLIBC__ >= 2 && __GLIBC_MINOR__ >= 1
yes
#endif
_ACEOF
if (eval "$ac_cpp conftest.$ac_ext") 2>&5 |
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
$EGREP "yes" >/dev/null 2>&1; then :
Don't require IPv6 library support in order to support IPv6 addresses. Have our own routines to convert between IPv4/IPv6 addresses and strings; that helps if, for example, we want to build binary versions of tcpdump for Windows that can run both on NT 5 (W2K/WXP), which doesn't have inet_ntop() or inet_pton(), and NT 6 (Vista/7/8/10), which do. It also means that we don't require IPv6 library support on UN*X to print addresses (if somebody wants to build tcpdump for older UN*Xes lacking IPv6 support in the system library or in add-on libraries). Get rid of files in the missing directory that we don't need, and various no-longer-necessary autoconf tests.
2015-09-18 05:56:44 +08:00
ipv6type=$i
Check for extra networking libraries before checking for IPv6. On some platforms, such as SunOS 5.x, building the "do we have IPv6 support?" test program requires the extra networking libraries, so we need to know what extra networking libraries are required before doing that test.
2013-04-07 04:03:58 +08:00
fi
rm -f conftest*
;;
linux-libinet6)
if test -d /usr/inet6 -o -f /usr/include/netinet/ip6.h; then
ipv6type=$i
ipv6lib=inet6
ipv6libdir=/usr/inet6/lib
ipv6trylibc=yes;
Don't require IPv6 library support in order to support IPv6 addresses. Have our own routines to convert between IPv4/IPv6 addresses and strings; that helps if, for example, we want to build binary versions of tcpdump for Windows that can run both on NT 5 (W2K/WXP), which doesn't have inet_ntop() or inet_pton(), and NT 6 (Vista/7/8/10), which do. It also means that we don't require IPv6 library support on UN*X to print addresses (if somebody wants to build tcpdump for older UN*Xes lacking IPv6 support in the system library or in add-on libraries). Get rid of files in the missing directory that we don't need, and various no-longer-necessary autoconf tests.
2015-09-18 05:56:44 +08:00
CFLAGS="-I/usr/inet6/include $CFLAGS"
Check for extra networking libraries before checking for IPv6. On some platforms, such as SunOS 5.x, building the "do we have IPv6 support?" test program requires the extra networking libraries, so we need to know what extra networking libraries are required before doing that test.
2013-04-07 04:03:58 +08:00
fi
;;
toshiba)
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
cat confdefs.h - <<_ACEOF >conftest.$ac_ext
Check for extra networking libraries before checking for IPv6. On some platforms, such as SunOS 5.x, building the "do we have IPv6 support?" test program requires the extra networking libraries, so we need to know what extra networking libraries are required before doing that test.
2013-04-07 04:03:58 +08:00
/* end confdefs.h. */
#include <sys/param.h>
#ifdef _TOSHIBA_INET6
yes
#endif
_ACEOF
if (eval "$ac_cpp conftest.$ac_ext") 2>&5 |
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
$EGREP "yes" >/dev/null 2>&1; then :
Check for extra networking libraries before checking for IPv6. On some platforms, such as SunOS 5.x, building the "do we have IPv6 support?" test program requires the extra networking libraries, so we need to know what extra networking libraries are required before doing that test.
2013-04-07 04:03:58 +08:00
ipv6type=$i;
ipv6lib=inet6;
Don't require IPv6 library support in order to support IPv6 addresses. Have our own routines to convert between IPv4/IPv6 addresses and strings; that helps if, for example, we want to build binary versions of tcpdump for Windows that can run both on NT 5 (W2K/WXP), which doesn't have inet_ntop() or inet_pton(), and NT 6 (Vista/7/8/10), which do. It also means that we don't require IPv6 library support on UN*X to print addresses (if somebody wants to build tcpdump for older UN*Xes lacking IPv6 support in the system library or in add-on libraries). Get rid of files in the missing directory that we don't need, and various no-longer-necessary autoconf tests.
2015-09-18 05:56:44 +08:00
ipv6libdir=/usr/local/v6/lib
Check for extra networking libraries before checking for IPv6. On some platforms, such as SunOS 5.x, building the "do we have IPv6 support?" test program requires the extra networking libraries, so we need to know what extra networking libraries are required before doing that test.
2013-04-07 04:03:58 +08:00
fi
rm -f conftest*
;;
v6d)
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
cat confdefs.h - <<_ACEOF >conftest.$ac_ext
Check for extra networking libraries before checking for IPv6. On some platforms, such as SunOS 5.x, building the "do we have IPv6 support?" test program requires the extra networking libraries, so we need to know what extra networking libraries are required before doing that test.
2013-04-07 04:03:58 +08:00
/* end confdefs.h. */
#include </usr/local/v6/include/sys/v6config.h>
#ifdef __V6D__
yes
#endif
_ACEOF
if (eval "$ac_cpp conftest.$ac_ext") 2>&5 |
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
$EGREP "yes" >/dev/null 2>&1; then :
Check for extra networking libraries before checking for IPv6. On some platforms, such as SunOS 5.x, building the "do we have IPv6 support?" test program requires the extra networking libraries, so we need to know what extra networking libraries are required before doing that test.
2013-04-07 04:03:58 +08:00
ipv6type=$i;
ipv6lib=v6;
ipv6libdir=/usr/local/v6/lib;
CFLAGS="-I/usr/local/v6/include $CFLAGS"
fi
rm -f conftest*
;;
zeta)
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
cat confdefs.h - <<_ACEOF >conftest.$ac_ext
Check for extra networking libraries before checking for IPv6. On some platforms, such as SunOS 5.x, building the "do we have IPv6 support?" test program requires the extra networking libraries, so we need to know what extra networking libraries are required before doing that test.
2013-04-07 04:03:58 +08:00
/* end confdefs.h. */
#include <sys/param.h>
#ifdef _ZETA_MINAMI_INET6
yes
#endif
_ACEOF
if (eval "$ac_cpp conftest.$ac_ext") 2>&5 |
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
$EGREP "yes" >/dev/null 2>&1; then :
Check for extra networking libraries before checking for IPv6. On some platforms, such as SunOS 5.x, building the "do we have IPv6 support?" test program requires the extra networking libraries, so we need to know what extra networking libraries are required before doing that test.
2013-04-07 04:03:58 +08:00
ipv6type=$i;
ipv6lib=inet6;
Don't require IPv6 library support in order to support IPv6 addresses. Have our own routines to convert between IPv4/IPv6 addresses and strings; that helps if, for example, we want to build binary versions of tcpdump for Windows that can run both on NT 5 (W2K/WXP), which doesn't have inet_ntop() or inet_pton(), and NT 6 (Vista/7/8/10), which do. It also means that we don't require IPv6 library support on UN*X to print addresses (if somebody wants to build tcpdump for older UN*Xes lacking IPv6 support in the system library or in add-on libraries). Get rid of files in the missing directory that we don't need, and various no-longer-necessary autoconf tests.
2015-09-18 05:56:44 +08:00
ipv6libdir=/usr/local/v6/lib
Check for extra networking libraries before checking for IPv6. On some platforms, such as SunOS 5.x, building the "do we have IPv6 support?" test program requires the extra networking libraries, so we need to know what extra networking libraries are required before doing that test.
2013-04-07 04:03:58 +08:00
fi
rm -f conftest*
;;
esac
if test "$ipv6type" != "unknown"; then
break
fi
done
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
{ $as_echo "$as_me:${as_lineno-$LINENO}: result: $ipv6type" >&5
$as_echo "$ipv6type" >&6; }
Check for extra networking libraries before checking for IPv6. On some platforms, such as SunOS 5.x, building the "do we have IPv6 support?" test program requires the extra networking libraries, so we need to know what extra networking libraries are required before doing that test.
2013-04-07 04:03:58 +08:00
fi
if test "$ipv6" = "yes" -a "$ipv6lib" != "none"; then
if test -d $ipv6libdir -a -f $ipv6libdir/lib$ipv6lib.a; then
LIBS="-L$ipv6libdir -l$ipv6lib $LIBS"
echo "You have $ipv6lib library, using it"
else
if test "$ipv6trylibc" = "yes"; then
echo "You do not have $ipv6lib library, using libc"
else
echo 'Fatal: no $ipv6lib library found. cannot continue.'
echo "You need to fetch lib$ipv6lib.a from appropriate"
echo 'ipv6 kit and compile beforehand.'
exit 1
fi
fi
fi
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
{ $as_echo "$as_me:${as_lineno-$LINENO}: checking for dnet_htoa declaration in netdnet/dnetdb.h" >&5
$as_echo_n "checking for dnet_htoa declaration in netdnet/dnetdb.h... " >&6; }
if ${td_cv_decl_netdnet_dnetdb_h_dnet_htoa+:} false; then :
$as_echo_n "(cached) " >&6
else
cat confdefs.h - <<_ACEOF >conftest.$ac_ext
/* end confdefs.h. */
#include <netdnet/dnetdb.h>
Initial revision
1999-10-08 07:47:09 +08:00
Regenerate with autoconf 2.57.
2004-01-14 11:15:08 +08:00
_ACEOF
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
if (eval "$ac_cpp conftest.$ac_ext") 2>&5 |
$EGREP "dnet_htoa" >/dev/null 2>&1; then :
td_cv_decl_netdnet_dnetdb_h_dnet_htoa=yes
Regenerate with autoconf 2.57.
2004-01-14 11:15:08 +08:00
else
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
td_cv_decl_netdnet_dnetdb_h_dnet_htoa=no
Regenerate with autoconf 2.57.
2004-01-14 11:15:08 +08:00
fi
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
rm -f conftest*
Check for extra networking libraries before checking for IPv6. On some platforms, such as SunOS 5.x, building the "do we have IPv6 support?" test program requires the extra networking libraries, so we need to know what extra networking libraries are required before doing that test.
2013-04-07 04:03:58 +08:00
fi
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
{ $as_echo "$as_me:${as_lineno-$LINENO}: result: $td_cv_decl_netdnet_dnetdb_h_dnet_htoa" >&5
$as_echo "$td_cv_decl_netdnet_dnetdb_h_dnet_htoa" >&6; }
if test "$td_cv_decl_netdnet_dnetdb_h_dnet_htoa" = yes; then
Initial revision
1999-10-08 07:47:09 +08:00
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
$as_echo "#define HAVE_NETDNET_DNETDB_H_DNET_HTOA 1" >>confdefs.h
Initial revision
1999-10-08 07:47:09 +08:00
Check for ether_ntohost() after checking for libpcap, so that we do so after we've checked whether we need -lsocket -lnsl to get routines such as ether_ntohost().
2005-03-28 07:16:08 +08:00
fi
Initial revision
1999-10-08 07:47:09 +08:00
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
ac_fn_c_check_func "$LINENO" "vfprintf" "ac_cv_func_vfprintf"
if test "x$ac_cv_func_vfprintf" = xyes; then :
$as_echo "#define HAVE_VFPRINTF 1" >>confdefs.h
Initial revision
1999-10-08 07:47:09 +08:00
else
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
case " $LIBOBJS " in
*" vfprintf.$ac_objext "* ) ;;
*) LIBOBJS="$LIBOBJS vfprintf.$ac_objext"
;;
esac
Initial revision
1999-10-08 07:47:09 +08:00
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
fi
Check for extra networking libraries before checking for IPv6. On some platforms, such as SunOS 5.x, building the "do we have IPv6 support?" test program requires the extra networking libraries, so we need to know what extra networking libraries are required before doing that test.
2013-04-07 04:03:58 +08:00
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
ac_fn_c_check_func "$LINENO" "strlcat" "ac_cv_func_strlcat"
if test "x$ac_cv_func_strlcat" = xyes; then :
$as_echo "#define HAVE_STRLCAT 1" >>confdefs.h
else
case " $LIBOBJS " in
*" strlcat.$ac_objext "* ) ;;
*) LIBOBJS="$LIBOBJS strlcat.$ac_objext"
;;
Check for extra networking libraries before checking for IPv6. On some platforms, such as SunOS 5.x, building the "do we have IPv6 support?" test program requires the extra networking libraries, so we need to know what extra networking libraries are required before doing that test.
2013-04-07 04:03:58 +08:00
esac
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
fi
ac_fn_c_check_func "$LINENO" "strlcpy" "ac_cv_func_strlcpy"
if test "x$ac_cv_func_strlcpy" = xyes; then :
$as_echo "#define HAVE_STRLCPY 1" >>confdefs.h
Regenerate with autoconf 2.57.
2004-01-14 11:15:08 +08:00
else
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
case " $LIBOBJS " in
*" strlcpy.$ac_objext "* ) ;;
*) LIBOBJS="$LIBOBJS strlcpy.$ac_objext"
;;
esac
Check for extra networking libraries before checking for IPv6. On some platforms, such as SunOS 5.x, building the "do we have IPv6 support?" test program requires the extra networking libraries, so we need to know what extra networking libraries are required before doing that test.
2013-04-07 04:03:58 +08:00
Regenerate with autoconf 2.57.
2004-01-14 11:15:08 +08:00
fi
Check for extra networking libraries before checking for IPv6. On some platforms, such as SunOS 5.x, building the "do we have IPv6 support?" test program requires the extra networking libraries, so we need to know what extra networking libraries are required before doing that test.
2013-04-07 04:03:58 +08:00
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
ac_fn_c_check_func "$LINENO" "strdup" "ac_cv_func_strdup"
if test "x$ac_cv_func_strdup" = xyes; then :
$as_echo "#define HAVE_STRDUP 1" >>confdefs.h
else
case " $LIBOBJS " in
*" strdup.$ac_objext "* ) ;;
*) LIBOBJS="$LIBOBJS strdup.$ac_objext"
;;
esac
Regenerate with autoconf 2.57.
2004-01-14 11:15:08 +08:00
fi
Check for extra networking libraries before checking for IPv6. On some platforms, such as SunOS 5.x, building the "do we have IPv6 support?" test program requires the extra networking libraries, so we need to know what extra networking libraries are required before doing that test.
2013-04-07 04:03:58 +08:00
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
ac_fn_c_check_func "$LINENO" "strsep" "ac_cv_func_strsep"
if test "x$ac_cv_func_strsep" = xyes; then :
$as_echo "#define HAVE_STRSEP 1" >>confdefs.h
Check for extra networking libraries before checking for IPv6. On some platforms, such as SunOS 5.x, building the "do we have IPv6 support?" test program requires the extra networking libraries, so we need to know what extra networking libraries are required before doing that test.
2013-04-07 04:03:58 +08:00
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
else
case " $LIBOBJS " in
*" strsep.$ac_objext "* ) ;;
*) LIBOBJS="$LIBOBJS strsep.$ac_objext"
;;
esac
Check for extra networking libraries before checking for IPv6. On some platforms, such as SunOS 5.x, building the "do we have IPv6 support?" test program requires the extra networking libraries, so we need to know what extra networking libraries are required before doing that test.
2013-04-07 04:03:58 +08:00
Initial revision
1999-10-08 07:47:09 +08:00
fi
regenerate
2017-10-24 13:17:52 +08:00
ac_fn_c_check_func "$LINENO" "getservent" "ac_cv_func_getservent"
if test "x$ac_cv_func_getservent" = xyes; then :
$as_echo "#define HAVE_GETSERVENT 1" >>confdefs.h
else
case " $LIBOBJS " in
*" getservent.$ac_objext "* ) ;;
*) LIBOBJS="$LIBOBJS getservent.$ac_objext"
;;
esac
fi
Use getopt_long(). This requires us to check for it in the configure script and to include a version of getopt_long() for the benefit of platforms that don't have it; we pick up the FreeBSD version and tweak it a bit (eliminating some features specific to the BSD version of getopt_long(), as we want to use it only in a fashion portable to Linux/*BSD/Solaris/etc.) We also get rid of the version of getopt() we supply for Windows in favor of the version of getopt_long() we provide.
2014-05-01 06:28:06 +08:00
ac_fn_c_check_func "$LINENO" "getopt_long" "ac_cv_func_getopt_long"
if test "x$ac_cv_func_getopt_long" = xyes; then :
$as_echo "#define HAVE_GETOPT_LONG 1" >>confdefs.h
else
case " $LIBOBJS " in
*" getopt_long.$ac_objext "* ) ;;
*) LIBOBJS="$LIBOBJS getopt_long.$ac_objext"
;;
esac
fi
Check for extra networking libraries before checking for IPv6. On some platforms, such as SunOS 5.x, building the "do we have IPv6 support?" test program requires the extra networking libraries, so we need to know what extra networking libraries are required before doing that test.
2013-04-07 04:03:58 +08:00
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
for ac_func in fork vfork strftime
do :
as_ac_var=`$as_echo "ac_cv_func_$ac_func" | $as_tr_sh`
ac_fn_c_check_func "$LINENO" "$ac_func" "$as_ac_var"
if eval test \"x\$"$as_ac_var"\" = x"yes"; then :
cat >>confdefs.h <<_ACEOF
#define `$as_echo "HAVE_$ac_func" | $as_tr_cpp` 1
Check for extra networking libraries before checking for IPv6. On some platforms, such as SunOS 5.x, building the "do we have IPv6 support?" test program requires the extra networking libraries, so we need to know what extra networking libraries are required before doing that test.
2013-04-07 04:03:58 +08:00
_ACEOF
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
fi
done
Check for extra networking libraries before checking for IPv6. On some platforms, such as SunOS 5.x, building the "do we have IPv6 support?" test program requires the extra networking libraries, so we need to know what extra networking libraries are required before doing that test.
2013-04-07 04:03:58 +08:00
Use alarm() iff we're not on Windows. We assume "not on Windows" means "on UN*X", which means we have alarm() (we don't care about V6 and earlier; 1978 called, they want their UNIX back). If somebody wants to support something that's neither UN*X nor Windows, they'll need to contribute support, properly checking for that other OS.
2017-11-13 05:31:57 +08:00
for ac_func in setlinebuf
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
do :
Use alarm() iff we're not on Windows. We assume "not on Windows" means "on UN*X", which means we have alarm() (we don't care about V6 and earlier; 1978 called, they want their UNIX back). If somebody wants to support something that's neither UN*X nor Windows, they'll need to contribute support, properly checking for that other OS.
2017-11-13 05:31:57 +08:00
ac_fn_c_check_func "$LINENO" "setlinebuf" "ac_cv_func_setlinebuf"
if test "x$ac_cv_func_setlinebuf" = xyes; then :
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
cat >>confdefs.h <<_ACEOF
Use alarm() iff we're not on Windows. We assume "not on Windows" means "on UN*X", which means we have alarm() (we don't care about V6 and earlier; 1978 called, they want their UNIX back). If somebody wants to support something that's neither UN*X nor Windows, they'll need to contribute support, properly checking for that other OS.
2017-11-13 05:31:57 +08:00
#define HAVE_SETLINEBUF 1
Check for extra networking libraries before checking for IPv6. On some platforms, such as SunOS 5.x, building the "do we have IPv6 support?" test program requires the extra networking libraries, so we need to know what extra networking libraries are required before doing that test.
2013-04-07 04:03:58 +08:00
_ACEOF
Initial revision
1999-10-08 07:47:09 +08:00
fi
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
done
Regenerate with autoconf 2.57.
2004-01-14 11:15:08 +08:00
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
needsnprintf=no
for ac_func in vsnprintf snprintf
do :
as_ac_var=`$as_echo "ac_cv_func_$ac_func" | $as_tr_sh`
ac_fn_c_check_func "$LINENO" "$ac_func" "$as_ac_var"
if eval test \"x\$"$as_ac_var"\" = x"yes"; then :
cat >>confdefs.h <<_ACEOF
#define `$as_echo "HAVE_$ac_func" | $as_tr_cpp` 1
Regenerate with autoconf 2.57.
2004-01-14 11:15:08 +08:00
_ACEOF
If we're using a local libpcap library, check for a local pcap-config script and, if we find it, query it to see what additional libraries are needed to link with that library. If we're not, check for a system pcap-config script and, if we find it, query it to see what C compiler flags and linker flags are needed to build with that library.
2009-05-23 09:45:27 +08:00
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
else
needsnprintf=yes
Use AC_PATH_TOOL, not AC_PATH_PROG, to find pcap-config. The PROG variant does not take into consideration cross-compilation, so it always looks for "pcap-config" which finds the host script. So use the TOOL variant instead which first searches for the cross-prefixed pcap-config before falling back to the bare "pcap-config". Reviewed-By: Guy Harris <guy@alum.mit.edu>
2010-12-01 08:13:05 +08:00
fi
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
done
Use AC_PATH_TOOL, not AC_PATH_PROG, to find pcap-config. The PROG variant does not take into consideration cross-compilation, so it always looks for "pcap-config" which finds the host script. So use the TOOL variant instead which first searches for the cross-prefixed pcap-config before falling back to the bare "pcap-config". Reviewed-By: Guy Harris <guy@alum.mit.edu>
2010-12-01 08:13:05 +08:00
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
if test $needsnprintf = yes; then
case " $LIBOBJS " in
*" snprintf.$ac_objext "* ) ;;
*) LIBOBJS="$LIBOBJS snprintf.$ac_objext"
;;
esac
Use AC_PATH_TOOL, not AC_PATH_PROG, to find pcap-config. The PROG variant does not take into consideration cross-compilation, so it always looks for "pcap-config" which finds the host script. So use the TOOL variant instead which first searches for the cross-prefixed pcap-config before falling back to the bare "pcap-config". Reviewed-By: Guy Harris <guy@alum.mit.edu>
2010-12-01 08:13:05 +08:00
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
fi
Use AC_PATH_TOOL, not AC_PATH_PROG, to find pcap-config. The PROG variant does not take into consideration cross-compilation, so it always looks for "pcap-config" which finds the host script. So use the TOOL variant instead which first searches for the cross-prefixed pcap-config before falling back to the bare "pcap-config". Reviewed-By: Guy Harris <guy@alum.mit.edu>
2010-12-01 08:13:05 +08:00
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
{ $as_echo "$as_me:${as_lineno-$LINENO}: checking for library containing dnet_htoa" >&5
$as_echo_n "checking for library containing dnet_htoa... " >&6; }
if ${ac_cv_search_dnet_htoa+:} false; then :
$as_echo_n "(cached) " >&6
NetBSD support for multiple data link types on an interface, from David Young <dyoung@ojctech.com>, with some minor changes by Jason R. Thorpe <thorpej@netbsd.org>, and further changes by me to: use "-y" rather than "-D" to set the link type ("-D" was already taken); use libpcap APIs to map between data link type names and values; supply stub versions of missing-but-needed libpcap APIs. Update Jason Thorpe's e-mail address (Zembu is going away, if it hasn't done so already).
2002-12-19 17:27:54 +08:00
else
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
ac_func_search_save_LIBS=$LIBS
cat confdefs.h - <<_ACEOF >conftest.$ac_ext
Check for extra networking libraries before checking for IPv6. On some platforms, such as SunOS 5.x, building the "do we have IPv6 support?" test program requires the extra networking libraries, so we need to know what extra networking libraries are required before doing that test.
2013-04-07 04:03:58 +08:00
/* end confdefs.h. */
/* Override any GCC internal prototype to avoid an error.
Use char because int might match the return type of a GCC
builtin and then its argument prototype would still apply. */
#ifdef __cplusplus
extern "C"
#endif
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
char dnet_htoa ();
Check for extra networking libraries before checking for IPv6. On some platforms, such as SunOS 5.x, building the "do we have IPv6 support?" test program requires the extra networking libraries, so we need to know what extra networking libraries are required before doing that test.
2013-04-07 04:03:58 +08:00
int
main ()
{
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
return dnet_htoa ();
Check for extra networking libraries before checking for IPv6. On some platforms, such as SunOS 5.x, building the "do we have IPv6 support?" test program requires the extra networking libraries, so we need to know what extra networking libraries are required before doing that test.
2013-04-07 04:03:58 +08:00
;
return 0;
}
_ACEOF
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
for ac_lib in '' dnet; do
if test -z "$ac_lib"; then
ac_res="none required"
else
ac_res=-l$ac_lib
LIBS="-l$ac_lib $ac_func_search_save_LIBS"
fi
if ac_fn_c_try_link "$LINENO"; then :
ac_cv_search_dnet_htoa=$ac_res
NetBSD support for multiple data link types on an interface, from David Young <dyoung@ojctech.com>, with some minor changes by Jason R. Thorpe <thorpej@netbsd.org>, and further changes by me to: use "-y" rather than "-D" to set the link type ("-D" was already taken); use libpcap APIs to map between data link type names and values; supply stub versions of missing-but-needed libpcap APIs. Update Jason Thorpe's e-mail address (Zembu is going away, if it hasn't done so already).
2002-12-19 17:27:54 +08:00
fi
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
rm -f core conftest.err conftest.$ac_objext \
conftest$ac_exeext
if ${ac_cv_search_dnet_htoa+:} false; then :
break
Check for extra networking libraries before checking for IPv6. On some platforms, such as SunOS 5.x, building the "do we have IPv6 support?" test program requires the extra networking libraries, so we need to know what extra networking libraries are required before doing that test.
2013-04-07 04:03:58 +08:00
fi
done
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
if ${ac_cv_search_dnet_htoa+:} false; then :
Add -Wpointer-arith to the list of warnings we enable with GCC.
2005-11-08 10:59:40 +08:00
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
else
ac_cv_search_dnet_htoa=no
fi
rm conftest.$ac_ext
LIBS=$ac_func_search_save_LIBS
Regenerate with autoconf 2.57.
2004-01-14 11:15:08 +08:00
fi
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
{ $as_echo "$as_me:${as_lineno-$LINENO}: result: $ac_cv_search_dnet_htoa" >&5
$as_echo "$ac_cv_search_dnet_htoa" >&6; }
ac_res=$ac_cv_search_dnet_htoa
if test "$ac_res" != no; then :
test "$ac_res" = "none required" || LIBS="$ac_res $LIBS"
Add -Wpointer-arith to the list of warnings we enable with GCC.
2005-11-08 10:59:40 +08:00
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
$as_echo "#define HAVE_DNET_HTOA 1" >>confdefs.h
Add -Wpointer-arith to the list of warnings we enable with GCC.
2005-11-08 10:59:40 +08:00
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
fi
Add -Wpointer-arith to the list of warnings we enable with GCC.
2005-11-08 10:59:40 +08:00
Print both the name and the description of a link-layer type (the name isn't always very suggestive - for example, somebody might think "EN10MB" is always 10 MB/s, and might not know that "IEEE802" is Token Ring), using "pcap_datalink_val_to_description()". Supply our own "pcap_datalink_val_to_description()" if libpcap doesn't have it (even if it has "pcap_datalink_name_to_val()").
2003-11-19 07:09:42 +08:00
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
{ $as_echo "$as_me:${as_lineno-$LINENO}: checking for main in -lrpc" >&5
$as_echo_n "checking for main in -lrpc... " >&6; }
if ${ac_cv_lib_rpc_main+:} false; then :
$as_echo_n "(cached) " >&6
Print both the name and the description of a link-layer type (the name isn't always very suggestive - for example, somebody might think "EN10MB" is always 10 MB/s, and might not know that "IEEE802" is Token Ring), using "pcap_datalink_val_to_description()". Supply our own "pcap_datalink_val_to_description()" if libpcap doesn't have it (even if it has "pcap_datalink_name_to_val()").
2003-11-19 07:09:42 +08:00
else
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
ac_check_lib_save_LIBS=$LIBS
LIBS="-lrpc $LIBS"
cat confdefs.h - <<_ACEOF >conftest.$ac_ext
/* end confdefs.h. */
Fix to work with autoconf 2.59.
2005-06-04 05:36:41 +08:00
Check for extra networking libraries before checking for IPv6. On some platforms, such as SunOS 5.x, building the "do we have IPv6 support?" test program requires the extra networking libraries, so we need to know what extra networking libraries are required before doing that test.
2013-04-07 04:03:58 +08:00
int
main ()
{
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
return main ();
Check for extra networking libraries before checking for IPv6. On some platforms, such as SunOS 5.x, building the "do we have IPv6 support?" test program requires the extra networking libraries, so we need to know what extra networking libraries are required before doing that test.
2013-04-07 04:03:58 +08:00
;
return 0;
}
_ACEOF
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
if ac_fn_c_try_link "$LINENO"; then :
ac_cv_lib_rpc_main=yes
Check for extra networking libraries before checking for IPv6. On some platforms, such as SunOS 5.x, building the "do we have IPv6 support?" test program requires the extra networking libraries, so we need to know what extra networking libraries are required before doing that test.
2013-04-07 04:03:58 +08:00
else
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
ac_cv_lib_rpc_main=no
NetBSD support for multiple data link types on an interface, from David Young <dyoung@ojctech.com>, with some minor changes by Jason R. Thorpe <thorpej@netbsd.org>, and further changes by me to: use "-y" rather than "-D" to set the link type ("-D" was already taken); use libpcap APIs to map between data link type names and values; supply stub versions of missing-but-needed libpcap APIs. Update Jason Thorpe's e-mail address (Zembu is going away, if it hasn't done so already).
2002-12-19 17:27:54 +08:00
fi
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
rm -f core conftest.err conftest.$ac_objext \
conftest$ac_exeext conftest.$ac_ext
LIBS=$ac_check_lib_save_LIBS
Check for extra networking libraries before checking for IPv6. On some platforms, such as SunOS 5.x, building the "do we have IPv6 support?" test program requires the extra networking libraries, so we need to know what extra networking libraries are required before doing that test.
2013-04-07 04:03:58 +08:00
fi
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
{ $as_echo "$as_me:${as_lineno-$LINENO}: result: $ac_cv_lib_rpc_main" >&5
$as_echo "$ac_cv_lib_rpc_main" >&6; }
if test "x$ac_cv_lib_rpc_main" = xyes; then :
From Andrew Church <andrew@users.sourceforge.net>: when testing for "pcap_version", "pcap_debug", and "yydebug", don't add our own functions referring to those variables - GCC 3.4.1 optimizes the test code out before the link is done, as it's in a function that's not called.
2004-08-27 15:17:03 +08:00
cat >>confdefs.h <<_ACEOF
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
#define HAVE_LIBRPC 1
From Andrew Church <andrew@users.sourceforge.net>: when testing for "pcap_version", "pcap_debug", and "yydebug", don't add our own functions referring to those variables - GCC 3.4.1 optimizes the test code out before the link is done, as it's in a function that's not called.
2004-08-27 15:17:03 +08:00
_ACEOF
Check whether we have "pcap_breakloop()", and use it if we do - it's a safer way to terminate "pcap_loop()" in a signal handler (it just sets a flag, it doesn't muck with data structures that might have been in the middle of being updated). Have "setsignal()" not request SA_RESTART, so that if we call "pcap_breakloop()" in a signal handler and then return, we don't restart a call that was waiting for captured packets, we just make that call EINTR out.
2003-11-04 15:29:15 +08:00
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
LIBS="-lrpc $LIBS"
Check whether we have "pcap_breakloop()", and use it if we do - it's a safer way to terminate "pcap_loop()" in a signal handler (it just sets a flag, it doesn't muck with data structures that might have been in the middle of being updated). Have "setsignal()" not request SA_RESTART, so that if we call "pcap_breakloop()" in a signal handler and then return, we don't restart a call that was waiting for captured packets, we just make that call EINTR out.
2003-11-04 15:29:15 +08:00
fi
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
{ $as_echo "$as_me:${as_lineno-$LINENO}: checking for library containing getrpcbynumber" >&5
$as_echo_n "checking for library containing getrpcbynumber... " >&6; }
if ${ac_cv_search_getrpcbynumber+:} false; then :
$as_echo_n "(cached) " >&6
Use pcap_dump_ftell() rather than casting a pcap_dumper_t * to a FILE * and using ftell(); that won't necessarily work on Windows (if libpcap was built with a different version of the C runtime library than tcpdump is), and, even on UN*X, would break if a pcap_dumper_t * were ever made something other than a FILE *. Provide a pcap_dump_ftell() implementation that does that cheating cast for use if libpcap doesn't have it (a pcap_dumper_t * is just a FILE * on those older versions of libpcap).
2005-06-04 06:08:51 +08:00
else
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
ac_func_search_save_LIBS=$LIBS
cat confdefs.h - <<_ACEOF >conftest.$ac_ext
Check for extra networking libraries before checking for IPv6. On some platforms, such as SunOS 5.x, building the "do we have IPv6 support?" test program requires the extra networking libraries, so we need to know what extra networking libraries are required before doing that test.
2013-04-07 04:03:58 +08:00
/* end confdefs.h. */
Use pcap_dump_ftell() rather than casting a pcap_dumper_t * to a FILE * and using ftell(); that won't necessarily work on Windows (if libpcap was built with a different version of the C runtime library than tcpdump is), and, even on UN*X, would break if a pcap_dumper_t * were ever made something other than a FILE *. Provide a pcap_dump_ftell() implementation that does that cheating cast for use if libpcap doesn't have it (a pcap_dumper_t * is just a FILE * on those older versions of libpcap).
2005-06-04 06:08:51 +08:00
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
/* Override any GCC internal prototype to avoid an error.
Use char because int might match the return type of a GCC
builtin and then its argument prototype would still apply. */
#ifdef __cplusplus
extern "C"
#endif
char getrpcbynumber ();
Check for extra networking libraries before checking for IPv6. On some platforms, such as SunOS 5.x, building the "do we have IPv6 support?" test program requires the extra networking libraries, so we need to know what extra networking libraries are required before doing that test.
2013-04-07 04:03:58 +08:00
int
main ()
{
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
return getrpcbynumber ();
Check for extra networking libraries before checking for IPv6. On some platforms, such as SunOS 5.x, building the "do we have IPv6 support?" test program requires the extra networking libraries, so we need to know what extra networking libraries are required before doing that test.
2013-04-07 04:03:58 +08:00
;
return 0;
}
_ACEOF
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
for ac_lib in '' nsl; do
if test -z "$ac_lib"; then
ac_res="none required"
else
ac_res=-l$ac_lib
LIBS="-l$ac_lib $ac_func_search_save_LIBS"
fi
if ac_fn_c_try_link "$LINENO"; then :
ac_cv_search_getrpcbynumber=$ac_res
fi
rm -f core conftest.err conftest.$ac_objext \
conftest$ac_exeext
if ${ac_cv_search_getrpcbynumber+:} false; then :
break
fi
done
if ${ac_cv_search_getrpcbynumber+:} false; then :
Add -Wpointer-arith to the list of warnings we enable with GCC.
2005-11-08 10:59:40 +08:00
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
else
ac_cv_search_getrpcbynumber=no
fi
rm conftest.$ac_ext
LIBS=$ac_func_search_save_LIBS
Check for extra networking libraries before checking for IPv6. On some platforms, such as SunOS 5.x, building the "do we have IPv6 support?" test program requires the extra networking libraries, so we need to know what extra networking libraries are required before doing that test.
2013-04-07 04:03:58 +08:00
fi
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
{ $as_echo "$as_me:${as_lineno-$LINENO}: result: $ac_cv_search_getrpcbynumber" >&5
$as_echo "$ac_cv_search_getrpcbynumber" >&6; }
ac_res=$ac_cv_search_getrpcbynumber
if test "$ac_res" != no; then :
test "$ac_res" = "none required" || LIBS="$ac_res $LIBS"
$as_echo "#define HAVE_GETRPCBYNUMBER 1" >>confdefs.h
Use pcap_dump_ftell() rather than casting a pcap_dumper_t * to a FILE * and using ftell(); that won't necessarily work on Windows (if libpcap was built with a different version of the C runtime library than tcpdump is), and, even on UN*X, would break if a pcap_dumper_t * were ever made something other than a FILE *. Provide a pcap_dump_ftell() implementation that does that cheating cast for use if libpcap doesn't have it (a pcap_dumper_t * is just a FILE * on those older versions of libpcap).
2005-06-04 06:08:51 +08:00
fi
Check for extra networking libraries before checking for IPv6. On some platforms, such as SunOS 5.x, building the "do we have IPv6 support?" test program requires the extra networking libraries, so we need to know what extra networking libraries are required before doing that test.
2013-04-07 04:03:58 +08:00
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
LBL_LIBS="$LIBS"
pfopen=/usr/examples/packetfilter/pfopen.c
if test -f $pfopen ; then
for ac_func in pfopen
do :
ac_fn_c_check_func "$LINENO" "pfopen" "ac_cv_func_pfopen"
if test "x$ac_cv_func_pfopen" = xyes; then :
cat >>confdefs.h <<_ACEOF
#define HAVE_PFOPEN 1
Check for extra networking libraries before checking for IPv6. On some platforms, such as SunOS 5.x, building the "do we have IPv6 support?" test program requires the extra networking libraries, so we need to know what extra networking libraries are required before doing that test.
2013-04-07 04:03:58 +08:00
_ACEOF
Use pcap_dump_ftell() rather than casting a pcap_dumper_t * to a FILE * and using ftell(); that won't necessarily work on Windows (if libpcap was built with a different version of the C runtime library than tcpdump is), and, even on UN*X, would break if a pcap_dumper_t * were ever made something other than a FILE *. Provide a pcap_dump_ftell() implementation that does that cheating cast for use if libpcap doesn't have it (a pcap_dumper_t * is just a FILE * on those older versions of libpcap).
2005-06-04 06:08:51 +08:00
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
fi
done
if test $ac_cv_func_pfopen = "no" ; then
{ $as_echo "$as_me:${as_lineno-$LINENO}: result: Using $pfopen" >&5
$as_echo "Using $pfopen" >&6; }
LIBS="$LIBS $pfopen"
fi
fi
Regenerate configure script.
2014-11-06 14:21:33 +08:00
libpcap=FAIL
{ $as_echo "$as_me:${as_lineno-$LINENO}: checking for local pcap library" >&5
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
$as_echo_n "checking for local pcap library... " >&6; }
Regenerate configure script.
2014-11-06 14:21:33 +08:00
# Check whether --with-system-libpcap was given.
if test "${with_system_libpcap+set}" = set; then :
withval=$with_system_libpcap;
fi
if test "x$with_system_libpcap" != xyes ; then
lastdir=FAIL
places=`ls $srcdir/.. | sed -e 's,/$,,' -e "s,^,$srcdir/../," | \
egrep '/libpcap-[0-9]+\.[0-9]+(\.[0-9]*)?([ab][0-9]*|-PRE-GIT)?$'`
places2=`ls .. | sed -e 's,/$,,' -e "s,^,../," | \
egrep '/libpcap-[0-9]+\.[0-9]+(\.[0-9]*)?([ab][0-9]*|-PRE-GIT)?$'`
for dir in $places $srcdir/../libpcap ../libpcap $srcdir/libpcap $places2 ; do
basedir=`echo $dir | sed -e 's/[ab][0-9]*$//' | \
sed -e 's/-PRE-GIT$//' `
if test $lastdir = $basedir ; then
continue;
fi
lastdir=$dir
if test -r $dir/libpcap.a ; then
libpcap=$dir/libpcap.a
d=$dir
fi
done
fi
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
if test $libpcap = FAIL ; then
{ $as_echo "$as_me:${as_lineno-$LINENO}: result: not found" >&5
$as_echo "not found" >&6; }
#
# Look for pcap-config.
#
if test -n "$ac_tool_prefix"; then
# Extract the first word of "${ac_tool_prefix}pcap-config", so it can be a program name with args.
set dummy ${ac_tool_prefix}pcap-config; ac_word=$2
{ $as_echo "$as_me:${as_lineno-$LINENO}: checking for $ac_word" >&5
$as_echo_n "checking for $ac_word... " >&6; }
if ${ac_cv_path_PCAP_CONFIG+:} false; then :
$as_echo_n "(cached) " >&6
else
case $PCAP_CONFIG in
[\\/]* | ?:[\\/]*)
ac_cv_path_PCAP_CONFIG="$PCAP_CONFIG" # Let the user override the test with a path.
;;
*)
as_save_IFS=$IFS; IFS=$PATH_SEPARATOR
for as_dir in $PATH
do
IFS=$as_save_IFS
test -z "$as_dir" && as_dir=.
for ac_exec_ext in '' $ac_executable_extensions; do
if as_fn_executable_p "$as_dir/$ac_word$ac_exec_ext"; then
ac_cv_path_PCAP_CONFIG="$as_dir/$ac_word$ac_exec_ext"
$as_echo "$as_me:${as_lineno-$LINENO}: found $as_dir/$ac_word$ac_exec_ext" >&5
break 2
fi
done
done
IFS=$as_save_IFS
Use pcap_dump_ftell() rather than casting a pcap_dumper_t * to a FILE * and using ftell(); that won't necessarily work on Windows (if libpcap was built with a different version of the C runtime library than tcpdump is), and, even on UN*X, would break if a pcap_dumper_t * were ever made something other than a FILE *. Provide a pcap_dump_ftell() implementation that does that cheating cast for use if libpcap doesn't have it (a pcap_dumper_t * is just a FILE * on those older versions of libpcap).
2005-06-04 06:08:51 +08:00
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
;;
esac
fi
PCAP_CONFIG=$ac_cv_path_PCAP_CONFIG
if test -n "$PCAP_CONFIG"; then
{ $as_echo "$as_me:${as_lineno-$LINENO}: result: $PCAP_CONFIG" >&5
$as_echo "$PCAP_CONFIG" >&6; }
else
{ $as_echo "$as_me:${as_lineno-$LINENO}: result: no" >&5
$as_echo "no" >&6; }
Check for extra networking libraries before checking for IPv6. On some platforms, such as SunOS 5.x, building the "do we have IPv6 support?" test program requires the extra networking libraries, so we need to know what extra networking libraries are required before doing that test.
2013-04-07 04:03:58 +08:00
fi
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
fi
if test -z "$ac_cv_path_PCAP_CONFIG"; then
ac_pt_PCAP_CONFIG=$PCAP_CONFIG
# Extract the first word of "pcap-config", so it can be a program name with args.
set dummy pcap-config; ac_word=$2
{ $as_echo "$as_me:${as_lineno-$LINENO}: checking for $ac_word" >&5
$as_echo_n "checking for $ac_word... " >&6; }
if ${ac_cv_path_ac_pt_PCAP_CONFIG+:} false; then :
$as_echo_n "(cached) " >&6
else
case $ac_pt_PCAP_CONFIG in
[\\/]* | ?:[\\/]*)
ac_cv_path_ac_pt_PCAP_CONFIG="$ac_pt_PCAP_CONFIG" # Let the user override the test with a path.
;;
*)
as_save_IFS=$IFS; IFS=$PATH_SEPARATOR
for as_dir in $PATH
do
IFS=$as_save_IFS
test -z "$as_dir" && as_dir=.
for ac_exec_ext in '' $ac_executable_extensions; do
if as_fn_executable_p "$as_dir/$ac_word$ac_exec_ext"; then
ac_cv_path_ac_pt_PCAP_CONFIG="$as_dir/$ac_word$ac_exec_ext"
$as_echo "$as_me:${as_lineno-$LINENO}: found $as_dir/$ac_word$ac_exec_ext" >&5
break 2
fi
done
done
IFS=$as_save_IFS
;;
esac
fi
ac_pt_PCAP_CONFIG=$ac_cv_path_ac_pt_PCAP_CONFIG
if test -n "$ac_pt_PCAP_CONFIG"; then
{ $as_echo "$as_me:${as_lineno-$LINENO}: result: $ac_pt_PCAP_CONFIG" >&5
$as_echo "$ac_pt_PCAP_CONFIG" >&6; }
else
{ $as_echo "$as_me:${as_lineno-$LINENO}: result: no" >&5
$as_echo "no" >&6; }
Check for extra networking libraries before checking for IPv6. On some platforms, such as SunOS 5.x, building the "do we have IPv6 support?" test program requires the extra networking libraries, so we need to know what extra networking libraries are required before doing that test.
2013-04-07 04:03:58 +08:00
fi
From Andrew Church <andrew@users.sourceforge.net>: when testing for "pcap_version", "pcap_debug", and "yydebug", don't add our own functions referring to those variables - GCC 3.4.1 optimizes the test code out before the link is done, as it's in a function that's not called.
2004-08-27 15:17:03 +08:00
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
if test "x$ac_pt_PCAP_CONFIG" = x; then
PCAP_CONFIG=""
else
case $cross_compiling:$ac_tool_warned in
yes:)
{ $as_echo "$as_me:${as_lineno-$LINENO}: WARNING: using cross tools not prefixed with host triplet" >&5
$as_echo "$as_me: WARNING: using cross tools not prefixed with host triplet" >&2;}
ac_tool_warned=yes ;;
esac
PCAP_CONFIG=$ac_pt_PCAP_CONFIG
fi
else
PCAP_CONFIG="$ac_cv_path_PCAP_CONFIG"
fi
if test -n "$PCAP_CONFIG" ; then
#
# Found - use it to get the include flags for
# libpcap and the flags to link with libpcap.
#
# Please read section 11.6 "Shell Substitutions"
# in the autoconf manual before doing anything
# to this that involves quoting. Especially note
# the statement "There is just no portable way to use
# double-quoted strings inside double-quoted back-quoted
# expressions (pfew!)."
#
cflags=`"$PCAP_CONFIG" --cflags`
V_INCLS="$cflags $V_INCLS"
libpcap=`"$PCAP_CONFIG" --libs`
else
#
# Not found; look for pcap.
#
{ $as_echo "$as_me:${as_lineno-$LINENO}: checking for main in -lpcap" >&5
$as_echo_n "checking for main in -lpcap... " >&6; }
if ${ac_cv_lib_pcap_main+:} false; then :
$as_echo_n "(cached) " >&6
else
ac_check_lib_save_LIBS=$LIBS
LIBS="-lpcap $LIBS"
cat confdefs.h - <<_ACEOF >conftest.$ac_ext
From Andrew Church <andrew@users.sourceforge.net>: when testing for "pcap_version", "pcap_debug", and "yydebug", don't add our own functions referring to those variables - GCC 3.4.1 optimizes the test code out before the link is done, as it's in a function that's not called.
2004-08-27 15:17:03 +08:00
/* end confdefs.h. */
Check for extra networking libraries before checking for IPv6. On some platforms, such as SunOS 5.x, building the "do we have IPv6 support?" test program requires the extra networking libraries, so we need to know what extra networking libraries are required before doing that test.
2013-04-07 04:03:58 +08:00
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
Regenerate with autoconf 2.57.
2004-01-14 11:15:08 +08:00
int
main ()
{
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
return main ();
Regenerate with autoconf 2.57.
2004-01-14 11:15:08 +08:00
;
return 0;
}
_ACEOF
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
if ac_fn_c_try_link "$LINENO"; then :
ac_cv_lib_pcap_main=yes
else
ac_cv_lib_pcap_main=no
fi
rm -f core conftest.err conftest.$ac_objext \
conftest$ac_exeext conftest.$ac_ext
LIBS=$ac_check_lib_save_LIBS
fi
{ $as_echo "$as_me:${as_lineno-$LINENO}: result: $ac_cv_lib_pcap_main" >&5
$as_echo "$ac_cv_lib_pcap_main" >&6; }
if test "x$ac_cv_lib_pcap_main" = xyes; then :
libpcap="-lpcap"
fi
if test $libpcap = FAIL ; then
as_fn_error $? "see the INSTALL doc for more info" "$LINENO" 5
fi
{ $as_echo "$as_me:${as_lineno-$LINENO}: checking for extraneous pcap header directories" >&5
$as_echo_n "checking for extraneous pcap header directories... " >&6; }
if test \( ! -r /usr/local/include/pcap.h \) -a \
\( ! -r /usr/include/pcap.h \); then
if test -r /usr/local/include/pcap/pcap.h; then
d="/usr/local/include/pcap"
elif test -r /usr/include/pcap/pcap.h; then
d="/usr/include/pcap"
fi
fi
if test -z "$d" ; then
{ $as_echo "$as_me:${as_lineno-$LINENO}: result: not found" >&5
$as_echo "not found" >&6; }
else
V_INCLS="-I$d $V_INCLS"
{ $as_echo "$as_me:${as_lineno-$LINENO}: result: found -- -I$d added" >&5
$as_echo "found -- -I$d added" >&6; }
fi
fi
else
V_PCAPDEP=$libpcap
places=`ls $srcdir/.. | sed -e 's,/$,,' -e "s,^,$srcdir/../," | \
egrep '/libpcap-[0-9]*.[0-9]*(.[0-9]*)?([ab][0-9]*)?$'`
these changes to aclocal let tcpdump, when build out of source tree, to find a libpcap that is adjacent to it, also built out of source tree
2014-09-03 09:16:24 +08:00
places2=`ls .. | sed -e 's,/$,,' -e "s,^,../," | \
egrep '/libpcap-[0-9]*.[0-9]*(.[0-9]*)?([ab][0-9]*)?$'`
pcapH=FAIL
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
if test -r $d/pcap.h; then
these changes to aclocal let tcpdump, when build out of source tree, to find a libpcap that is adjacent to it, also built out of source tree
2014-09-03 09:16:24 +08:00
pcapH=$d
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
else
these changes to aclocal let tcpdump, when build out of source tree, to find a libpcap that is adjacent to it, also built out of source tree
2014-09-03 09:16:24 +08:00
for dir in $places $srcdir/../libpcap ../libpcap $srcdir/libpcap $places2 ; do
if test -r $dir/pcap.h ; then
pcapH=$dir
fi
done
fi
if test $pcapH = FAIL ; then
as_fn_error $? "cannot find pcap.h: see INSTALL" "$LINENO" 5
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
fi
these changes to aclocal let tcpdump, when build out of source tree, to find a libpcap that is adjacent to it, also built out of source tree
2014-09-03 09:16:24 +08:00
V_INCLS="-I$pcapH $V_INCLS"
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
{ $as_echo "$as_me:${as_lineno-$LINENO}: result: $libpcap" >&5
$as_echo "$libpcap" >&6; }
# Extract the first word of "pcap-config", so it can be a program name with args.
set dummy pcap-config; ac_word=$2
{ $as_echo "$as_me:${as_lineno-$LINENO}: checking for $ac_word" >&5
$as_echo_n "checking for $ac_word... " >&6; }
if ${ac_cv_path_PCAP_CONFIG+:} false; then :
$as_echo_n "(cached) " >&6
else
case $PCAP_CONFIG in
[\\/]* | ?:[\\/]*)
ac_cv_path_PCAP_CONFIG="$PCAP_CONFIG" # Let the user override the test with a path.
;;
*)
as_save_IFS=$IFS; IFS=$PATH_SEPARATOR
for as_dir in $d
do
IFS=$as_save_IFS
test -z "$as_dir" && as_dir=.
for ac_exec_ext in '' $ac_executable_extensions; do
if as_fn_executable_p "$as_dir/$ac_word$ac_exec_ext"; then
ac_cv_path_PCAP_CONFIG="$as_dir/$ac_word$ac_exec_ext"
$as_echo "$as_me:${as_lineno-$LINENO}: found $as_dir/$ac_word$ac_exec_ext" >&5
break 2
fi
done
done
IFS=$as_save_IFS
;;
Add -Wpointer-arith to the list of warnings we enable with GCC.
2005-11-08 10:59:40 +08:00
esac
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
fi
PCAP_CONFIG=$ac_cv_path_PCAP_CONFIG
if test -n "$PCAP_CONFIG"; then
{ $as_echo "$as_me:${as_lineno-$LINENO}: result: $PCAP_CONFIG" >&5
$as_echo "$PCAP_CONFIG" >&6; }
Check for extra networking libraries before checking for IPv6. On some platforms, such as SunOS 5.x, building the "do we have IPv6 support?" test program requires the extra networking libraries, so we need to know what extra networking libraries are required before doing that test.
2013-04-07 04:03:58 +08:00
else
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
{ $as_echo "$as_me:${as_lineno-$LINENO}: result: no" >&5
$as_echo "no" >&6; }
Check for extra networking libraries before checking for IPv6. On some platforms, such as SunOS 5.x, building the "do we have IPv6 support?" test program requires the extra networking libraries, so we need to know what extra networking libraries are required before doing that test.
2013-04-07 04:03:58 +08:00
fi
Add -Wpointer-arith to the list of warnings we enable with GCC.
2005-11-08 10:59:40 +08:00
Check for extra networking libraries before checking for IPv6. On some platforms, such as SunOS 5.x, building the "do we have IPv6 support?" test program requires the extra networking libraries, so we need to know what extra networking libraries are required before doing that test.
2013-04-07 04:03:58 +08:00
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
if test -n "$PCAP_CONFIG"; then
#
# The libpcap directory has a pcap-config script.
# Use it to get any additioal libraries needed
# to link with the libpcap archive library in
# that directory.
#
# Please read section 11.6 "Shell Substitutions"
# in the autoconf manual before doing anything
# to this that involves quoting. Especially note
# the statement "There is just no portable way to use
# double-quoted strings inside double-quoted back-quoted
# expressions (pfew!)."
#
additional_libs=`"$PCAP_CONFIG" --additional-libs --static`
libpcap="$libpcap $additional_libs"
fi
Check for extra networking libraries before checking for IPv6. On some platforms, such as SunOS 5.x, building the "do we have IPv6 support?" test program requires the extra networking libraries, so we need to know what extra networking libraries are required before doing that test.
2013-04-07 04:03:58 +08:00
fi
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
LIBS="$libpcap $LIBS"
if ! test -n "$PCAP_CONFIG" ; then
#
# We don't have pcap-config; find out any additional link flags
# we need. (If we have pcap-config, we assume it tells us what
# we need.)
#
case "$host_os" in
Check for extra networking libraries before checking for IPv6. On some platforms, such as SunOS 5.x, building the "do we have IPv6 support?" test program requires the extra networking libraries, so we need to know what extra networking libraries are required before doing that test.
2013-04-07 04:03:58 +08:00
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
aix*)
#
# If libpcap is DLPI-based, we have to use /lib/pse.exp if
# present, as we use the STREAMS routines.
#
# (XXX - true only if we're linking with a static libpcap?)
#
pseexe="/lib/pse.exp"
{ $as_echo "$as_me:${as_lineno-$LINENO}: checking for $pseexe" >&5
$as_echo_n "checking for $pseexe... " >&6; }
if test -f $pseexe ; then
{ $as_echo "$as_me:${as_lineno-$LINENO}: result: yes" >&5
$as_echo "yes" >&6; }
LIBS="$LIBS -I:$pseexe"
fi
Check for extra networking libraries before checking for IPv6. On some platforms, such as SunOS 5.x, building the "do we have IPv6 support?" test program requires the extra networking libraries, so we need to know what extra networking libraries are required before doing that test.
2013-04-07 04:03:58 +08:00
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
#
# If libpcap is BPF-based, we need "-lodm" and "-lcfg", as
# we use them to load the BPF module.
#
# (XXX - true only if we're linking with a static libpcap?)
#
LIBS="$LIBS -lodm -lcfg"
;;
esac
fi
Check for extra networking libraries before checking for IPv6. On some platforms, such as SunOS 5.x, building the "do we have IPv6 support?" test program requires the extra networking libraries, so we need to know what extra networking libraries are required before doing that test.
2013-04-07 04:03:58 +08:00
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
ac_fn_c_check_func "$LINENO" "pcap_loop" "ac_cv_func_pcap_loop"
if test "x$ac_cv_func_pcap_loop" = xyes; then :
Check for extra networking libraries before checking for IPv6. On some platforms, such as SunOS 5.x, building the "do we have IPv6 support?" test program requires the extra networking libraries, so we need to know what extra networking libraries are required before doing that test.
2013-04-07 04:03:58 +08:00
else
refine the feedback guidelines Provide better detailed guidelines in CONTRIBUTING and update a number of other files to refer to that file so that the directions are now more uniform.
2017-02-02 19:23:50 +08:00
as_fn_error $? "This is a bug, please follow the guidelines in CONTRIBUTING and include the
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
config.log file in your report. If you have downloaded libpcap from
tcpdump.org, and built it yourself, please also include the config.log
file from the libpcap source directory, the Makefile from the libpcap
source directory, and the output of the make process for libpcap, as
this could be a problem with the libpcap that was built, and we will
not be able to determine why this is happening, and thus will not be
able to fix it, without that information, as we have not been able to
reproduce this problem ourselves." "$LINENO" 5
Get rid of acconfig.h.
2013-05-13 06:28:28 +08:00
Check for extra networking libraries before checking for IPv6. On some platforms, such as SunOS 5.x, building the "do we have IPv6 support?" test program requires the extra networking libraries, so we need to know what extra networking libraries are required before doing that test.
2013-04-07 04:03:58 +08:00
fi
Some systems (*cough*Irix*cough) not only don't declare "ether_ntohost()" but don't even declare "struct ether_addr"; on those systems, declare "struct ether_addr".
2005-04-20 19:17:18 +08:00
Check for extra networking libraries before checking for IPv6. On some platforms, such as SunOS 5.x, building the "do we have IPv6 support?" test program requires the extra networking libraries, so we need to know what extra networking libraries are required before doing that test.
2013-04-07 04:03:58 +08:00
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
#
# Check for these after AC_LBL_LIBPCAP, so we link with the appropriate
# libraries (e.g., "-lsocket -lnsl" on Solaris).
#
# You are in a twisty little maze of UN*Xes, all different.
# Some might not have ether_ntohost().
# Some might have it, but not declare it in any header file.
# Some might have it, but declare it in <netinet/if_ether.h>.
# Some might have it, but declare it in <netinet/ether.h>
# (And some might have it but document it as something declared in
# <netinet/ethernet.h>, although <netinet/if_ether.h> appears to work.)
#
# Before you is a C compiler.
#
for ac_func in ether_ntohost
do :
ac_fn_c_check_func "$LINENO" "ether_ntohost" "ac_cv_func_ether_ntohost"
if test "x$ac_cv_func_ether_ntohost" = xyes; then :
cat >>confdefs.h <<_ACEOF
#define HAVE_ETHER_NTOHOST 1
Fix build issues with the OpenFlow printer on some systems. Don't assume we have <stdint.h>. Instead, use the AC_TYPE_ macros to ensure we have the C99 intN_t and uintN_t types; we already include <inttypes.h> in tcpdump-stdinc.h iff we have it. Get rid of the structure declarations in openflow-1.0.h, as they have zero-length arrays (not supported by all the compilers people might be using) and as 1) they're only used in sizeof() and 2) after each one there's an assertion to check that sizeof() returns a specific numerical value so, instead, just #define various _LEN items to those numerical values and use them. Add an openflow.h header with a #define for the length of the basic header, and move the declaration of of10_header_body_print() there.
2013-06-24 05:03:38 +08:00
_ACEOF
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
{ $as_echo "$as_me:${as_lineno-$LINENO}: checking for buggy ether_ntohost" >&5
$as_echo_n "checking for buggy ether_ntohost... " >&6; }
if ${ac_cv_buggy_ether_ntohost+:} false; then :
$as_echo_n "(cached) " >&6
else
if test "$cross_compiling" = yes; then :
ac_cv_buggy_ether_ntohost="not while cross-compiling"
else
cat confdefs.h - <<_ACEOF >conftest.$ac_ext
Fix build issues with the OpenFlow printer on some systems. Don't assume we have <stdint.h>. Instead, use the AC_TYPE_ macros to ensure we have the C99 intN_t and uintN_t types; we already include <inttypes.h> in tcpdump-stdinc.h iff we have it. Get rid of the structure declarations in openflow-1.0.h, as they have zero-length arrays (not supported by all the compilers people might be using) and as 1) they're only used in sizeof() and 2) after each one there's an assertion to check that sizeof() returns a specific numerical value so, instead, just #define various _LEN items to those numerical values and use them. Add an openflow.h header with a #define for the length of the basic header, and move the declaration of of10_header_body_print() there.
2013-06-24 05:03:38 +08:00
/* end confdefs.h. */
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
#include <netdb.h>
#include <sys/types.h>
#include <sys/param.h>
#include <sys/socket.h>
int
main(int argc, char **argv)
{
u_char ea[6] = { 0xff, 0xff, 0xff, 0xff, 0xff };
char name[MAXHOSTNAMELEN];
ether_ntohost(name, (struct ether_addr *)ea);
exit(0);
}
Fix build issues with the OpenFlow printer on some systems. Don't assume we have <stdint.h>. Instead, use the AC_TYPE_ macros to ensure we have the C99 intN_t and uintN_t types; we already include <inttypes.h> in tcpdump-stdinc.h iff we have it. Get rid of the structure declarations in openflow-1.0.h, as they have zero-length arrays (not supported by all the compilers people might be using) and as 1) they're only used in sizeof() and 2) after each one there's an assertion to check that sizeof() returns a specific numerical value so, instead, just #define various _LEN items to those numerical values and use them. Add an openflow.h header with a #define for the length of the basic header, and move the declaration of of10_header_body_print() there.
2013-06-24 05:03:38 +08:00
_ACEOF
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
if ac_fn_c_try_run "$LINENO"; then :
ac_cv_buggy_ether_ntohost=no
Check for extra networking libraries before checking for IPv6. On some platforms, such as SunOS 5.x, building the "do we have IPv6 support?" test program requires the extra networking libraries, so we need to know what extra networking libraries are required before doing that test.
2013-04-07 04:03:58 +08:00
else
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
ac_cv_buggy_ether_ntohost=yes
fi
rm -f core *.core core.conftest.* gmon.out bb.out conftest$ac_exeext \
conftest.$ac_objext conftest.beam conftest.$ac_ext
fi
Check for extra networking libraries before checking for IPv6. On some platforms, such as SunOS 5.x, building the "do we have IPv6 support?" test program requires the extra networking libraries, so we need to know what extra networking libraries are required before doing that test.
2013-04-07 04:03:58 +08:00
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
fi
{ $as_echo "$as_me:${as_lineno-$LINENO}: result: $ac_cv_buggy_ether_ntohost" >&5
$as_echo "$ac_cv_buggy_ether_ntohost" >&6; }
if test "$ac_cv_buggy_ether_ntohost" = "no"; then
$as_echo "#define USE_ETHER_NTOHOST 1" >>confdefs.h
fi
Fix build issues with the OpenFlow printer on some systems. Don't assume we have <stdint.h>. Instead, use the AC_TYPE_ macros to ensure we have the C99 intN_t and uintN_t types; we already include <inttypes.h> in tcpdump-stdinc.h iff we have it. Get rid of the structure declarations in openflow-1.0.h, as they have zero-length arrays (not supported by all the compilers people might be using) and as 1) they're only used in sizeof() and 2) after each one there's an assertion to check that sizeof() returns a specific numerical value so, instead, just #define various _LEN items to those numerical values and use them. Add an openflow.h header with a #define for the length of the basic header, and move the declaration of of10_header_body_print() there.
2013-06-24 05:03:38 +08:00
Check for extra networking libraries before checking for IPv6. On some platforms, such as SunOS 5.x, building the "do we have IPv6 support?" test program requires the extra networking libraries, so we need to know what extra networking libraries are required before doing that test.
2013-04-07 04:03:58 +08:00
fi
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
done
Some systems (*cough*Irix*cough) not only don't declare "ether_ntohost()" but don't even declare "struct ether_addr"; on those systems, declare "struct ether_addr".
2005-04-20 19:17:18 +08:00
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
if test "$ac_cv_func_ether_ntohost" = yes -a \
"$ac_cv_buggy_ether_ntohost" = "no"; then
#
# OK, we have ether_ntohost(). Do we have <netinet/if_ether.h>?
#
if test "$ac_cv_header_netinet_if_ether_h" = yes; then
#
# Yes. Does it declare ether_ntohost()?
#
ac_fn_c_check_decl "$LINENO" "ether_ntohost" "ac_cv_have_decl_ether_ntohost" "
#include <sys/types.h>
#include <sys/socket.h>
#include <netinet/in.h>
#include <arpa/inet.h>
struct mbuf;
struct rtentry;
#include <net/if.h>
#include <netinet/if_ether.h>
"
if test "x$ac_cv_have_decl_ether_ntohost" = xyes; then :
$as_echo "#define NETINET_IF_ETHER_H_DECLARES_ETHER_NTOHOST /**/" >>confdefs.h
Check for extra networking libraries before checking for IPv6. On some platforms, such as SunOS 5.x, building the "do we have IPv6 support?" test program requires the extra networking libraries, so we need to know what extra networking libraries are required before doing that test.
2013-04-07 04:03:58 +08:00
Fix build issues with the OpenFlow printer on some systems. Don't assume we have <stdint.h>. Instead, use the AC_TYPE_ macros to ensure we have the C99 intN_t and uintN_t types; we already include <inttypes.h> in tcpdump-stdinc.h iff we have it. Get rid of the structure declarations in openflow-1.0.h, as they have zero-length arrays (not supported by all the compilers people might be using) and as 1) they're only used in sizeof() and 2) after each one there's an assertion to check that sizeof() returns a specific numerical value so, instead, just #define various _LEN items to those numerical values and use them. Add an openflow.h header with a #define for the length of the basic header, and move the declaration of of10_header_body_print() there.
2013-06-24 05:03:38 +08:00
fi
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
fi
#
# Did that succeed?
#
if test "$ac_cv_have_decl_ether_ntohost" != yes; then
#
# No, how about <netinet/ether.h>, as on Linux?
#
for ac_header in netinet/ether.h
do :
ac_fn_c_check_header_mongrel "$LINENO" "netinet/ether.h" "ac_cv_header_netinet_ether_h" "$ac_includes_default"
if test "x$ac_cv_header_netinet_ether_h" = xyes; then :
cat >>confdefs.h <<_ACEOF
#define HAVE_NETINET_ETHER_H 1
_ACEOF
Fix build issues with the OpenFlow printer on some systems. Don't assume we have <stdint.h>. Instead, use the AC_TYPE_ macros to ensure we have the C99 intN_t and uintN_t types; we already include <inttypes.h> in tcpdump-stdinc.h iff we have it. Get rid of the structure declarations in openflow-1.0.h, as they have zero-length arrays (not supported by all the compilers people might be using) and as 1) they're only used in sizeof() and 2) after each one there's an assertion to check that sizeof() returns a specific numerical value so, instead, just #define various _LEN items to those numerical values and use them. Add an openflow.h header with a #define for the length of the basic header, and move the declaration of of10_header_body_print() there.
2013-06-24 05:03:38 +08:00
fi
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
done
if test "$ac_cv_header_netinet_ether_h" = yes; then
#
# We have it - does it declare ether_ntohost()?
# Unset ac_cv_have_decl_ether_ntohost so we don't
# treat the previous failure as a cached value and
# suppress the next test.
#
unset ac_cv_have_decl_ether_ntohost
ac_fn_c_check_decl "$LINENO" "ether_ntohost" "ac_cv_have_decl_ether_ntohost" "
#include <netinet/ether.h>
"
if test "x$ac_cv_have_decl_ether_ntohost" = xyes; then :
$as_echo "#define NETINET_ETHER_H_DECLARES_ETHER_NTOHOST /**/" >>confdefs.h
fi
fi
fi
#
# Is ether_ntohost() declared?
#
if test "$ac_cv_have_decl_ether_ntohost" != yes; then
#
# No, we'll have to declare it ourselves.
# Do we have "struct ether_addr"?
#
ac_fn_c_check_type "$LINENO" "struct ether_addr" "ac_cv_type_struct_ether_addr" "
#include <sys/types.h>
#include <sys/socket.h>
#include <netinet/in.h>
#include <arpa/inet.h>
struct mbuf;
struct rtentry;
#include <net/if.h>
#include <netinet/if_ether.h>
"
if test "x$ac_cv_type_struct_ether_addr" = xyes; then :
Fix build issues with the OpenFlow printer on some systems. Don't assume we have <stdint.h>. Instead, use the AC_TYPE_ macros to ensure we have the C99 intN_t and uintN_t types; we already include <inttypes.h> in tcpdump-stdinc.h iff we have it. Get rid of the structure declarations in openflow-1.0.h, as they have zero-length arrays (not supported by all the compilers people might be using) and as 1) they're only used in sizeof() and 2) after each one there's an assertion to check that sizeof() returns a specific numerical value so, instead, just #define various _LEN items to those numerical values and use them. Add an openflow.h header with a #define for the length of the basic header, and move the declaration of of10_header_body_print() there.
2013-06-24 05:03:38 +08:00
cat >>confdefs.h <<_ACEOF
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
#define HAVE_STRUCT_ETHER_ADDR 1
Fix build issues with the OpenFlow printer on some systems. Don't assume we have <stdint.h>. Instead, use the AC_TYPE_ macros to ensure we have the C99 intN_t and uintN_t types; we already include <inttypes.h> in tcpdump-stdinc.h iff we have it. Get rid of the structure declarations in openflow-1.0.h, as they have zero-length arrays (not supported by all the compilers people might be using) and as 1) they're only used in sizeof() and 2) after each one there's an assertion to check that sizeof() returns a specific numerical value so, instead, just #define various _LEN items to those numerical values and use them. Add an openflow.h header with a #define for the length of the basic header, and move the declaration of of10_header_body_print() there.
2013-06-24 05:03:38 +08:00
_ACEOF
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
fi
$as_echo "#define HAVE_DECL_ETHER_NTOHOST 0" >>confdefs.h
else
$as_echo "#define HAVE_DECL_ETHER_NTOHOST 1" >>confdefs.h
fi
fi
# libdlpi is needed for Solaris 11 and later.
{ $as_echo "$as_me:${as_lineno-$LINENO}: checking for dlpi_walk in -ldlpi" >&5
$as_echo_n "checking for dlpi_walk in -ldlpi... " >&6; }
if ${ac_cv_lib_dlpi_dlpi_walk+:} false; then :
$as_echo_n "(cached) " >&6
Fix build issues with the OpenFlow printer on some systems. Don't assume we have <stdint.h>. Instead, use the AC_TYPE_ macros to ensure we have the C99 intN_t and uintN_t types; we already include <inttypes.h> in tcpdump-stdinc.h iff we have it. Get rid of the structure declarations in openflow-1.0.h, as they have zero-length arrays (not supported by all the compilers people might be using) and as 1) they're only used in sizeof() and 2) after each one there's an assertion to check that sizeof() returns a specific numerical value so, instead, just #define various _LEN items to those numerical values and use them. Add an openflow.h header with a #define for the length of the basic header, and move the declaration of of10_header_body_print() there.
2013-06-24 05:03:38 +08:00
else
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
ac_check_lib_save_LIBS=$LIBS
LIBS="-ldlpi -L/lib $LIBS"
cat confdefs.h - <<_ACEOF >conftest.$ac_ext
Check for extra networking libraries before checking for IPv6. On some platforms, such as SunOS 5.x, building the "do we have IPv6 support?" test program requires the extra networking libraries, so we need to know what extra networking libraries are required before doing that test.
2013-04-07 04:03:58 +08:00
/* end confdefs.h. */
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
/* Override any GCC internal prototype to avoid an error.
Use char because int might match the return type of a GCC
builtin and then its argument prototype would still apply. */
#ifdef __cplusplus
extern "C"
#endif
char dlpi_walk ();
Fix build issues with the OpenFlow printer on some systems. Don't assume we have <stdint.h>. Instead, use the AC_TYPE_ macros to ensure we have the C99 intN_t and uintN_t types; we already include <inttypes.h> in tcpdump-stdinc.h iff we have it. Get rid of the structure declarations in openflow-1.0.h, as they have zero-length arrays (not supported by all the compilers people might be using) and as 1) they're only used in sizeof() and 2) after each one there's an assertion to check that sizeof() returns a specific numerical value so, instead, just #define various _LEN items to those numerical values and use them. Add an openflow.h header with a #define for the length of the basic header, and move the declaration of of10_header_body_print() there.
2013-06-24 05:03:38 +08:00
int
main ()
{
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
return dlpi_walk ();
Fix build issues with the OpenFlow printer on some systems. Don't assume we have <stdint.h>. Instead, use the AC_TYPE_ macros to ensure we have the C99 intN_t and uintN_t types; we already include <inttypes.h> in tcpdump-stdinc.h iff we have it. Get rid of the structure declarations in openflow-1.0.h, as they have zero-length arrays (not supported by all the compilers people might be using) and as 1) they're only used in sizeof() and 2) after each one there's an assertion to check that sizeof() returns a specific numerical value so, instead, just #define various _LEN items to those numerical values and use them. Add an openflow.h header with a #define for the length of the basic header, and move the declaration of of10_header_body_print() there.
2013-06-24 05:03:38 +08:00
;
return 0;
}
Check for extra networking libraries before checking for IPv6. On some platforms, such as SunOS 5.x, building the "do we have IPv6 support?" test program requires the extra networking libraries, so we need to know what extra networking libraries are required before doing that test.
2013-04-07 04:03:58 +08:00
_ACEOF
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
if ac_fn_c_try_link "$LINENO"; then :
ac_cv_lib_dlpi_dlpi_walk=yes
else
ac_cv_lib_dlpi_dlpi_walk=no
fi
rm -f core conftest.err conftest.$ac_objext \
conftest$ac_exeext conftest.$ac_ext
LIBS=$ac_check_lib_save_LIBS
fi
{ $as_echo "$as_me:${as_lineno-$LINENO}: result: $ac_cv_lib_dlpi_dlpi_walk" >&5
$as_echo "$ac_cv_lib_dlpi_dlpi_walk" >&6; }
if test "x$ac_cv_lib_dlpi_dlpi_walk" = xyes; then :
LIBS="$LIBS -ldlpi" LDFLAGS="-L/lib $LDFLAGS"
fi
Move pcap function checks to configure.in. It was doing some of the function checks; move the remaining ones out of AC_LBL_LIBPCAP(), which is now solely responsible for finding libpcap, making sure it'll work, and setting compiler and linker flags appropriately. Checks for functions that were introduced in later versions of libpcap, which we use if available, are all done in configure.in.
2015-02-11 05:52:51 +08:00
ac_fn_c_check_func "$LINENO" "pcap_list_datalinks" "ac_cv_func_pcap_list_datalinks"
if test "x$ac_cv_func_pcap_list_datalinks" = xyes; then :
$as_echo "#define HAVE_PCAP_LIST_DATALINKS 1" >>confdefs.h
for ac_func in pcap_free_datalinks
do :
ac_fn_c_check_func "$LINENO" "pcap_free_datalinks" "ac_cv_func_pcap_free_datalinks"
if test "x$ac_cv_func_pcap_free_datalinks" = xyes; then :
cat >>confdefs.h <<_ACEOF
#define HAVE_PCAP_FREE_DATALINKS 1
_ACEOF
fi
done
else
case " $LIBOBJS " in
*" datalinks.$ac_objext "* ) ;;
*) LIBOBJS="$LIBOBJS datalinks.$ac_objext"
;;
esac
fi
for ac_func in pcap_set_datalink
do :
ac_fn_c_check_func "$LINENO" "pcap_set_datalink" "ac_cv_func_pcap_set_datalink"
if test "x$ac_cv_func_pcap_set_datalink" = xyes; then :
cat >>confdefs.h <<_ACEOF
#define HAVE_PCAP_SET_DATALINK 1
_ACEOF
fi
done
ac_fn_c_check_func "$LINENO" "pcap_datalink_name_to_val" "ac_cv_func_pcap_datalink_name_to_val"
if test "x$ac_cv_func_pcap_datalink_name_to_val" = xyes; then :
$as_echo "#define HAVE_PCAP_DATALINK_NAME_TO_VAL 1" >>confdefs.h
ac_fn_c_check_func "$LINENO" "pcap_datalink_val_to_description" "ac_cv_func_pcap_datalink_val_to_description"
if test "x$ac_cv_func_pcap_datalink_val_to_description" = xyes; then :
$as_echo "#define HAVE_PCAP_DATALINK_VAL_TO_DESCRIPTION 1" >>confdefs.h
else
case " $LIBOBJS " in
*" dlnames.$ac_objext "* ) ;;
*) LIBOBJS="$LIBOBJS dlnames.$ac_objext"
;;
esac
fi
else
case " $LIBOBJS " in
*" dlnames.$ac_objext "* ) ;;
*) LIBOBJS="$LIBOBJS dlnames.$ac_objext"
;;
esac
fi
for ac_func in pcap_breakloop
do :
ac_fn_c_check_func "$LINENO" "pcap_breakloop" "ac_cv_func_pcap_breakloop"
if test "x$ac_cv_func_pcap_breakloop" = xyes; then :
cat >>confdefs.h <<_ACEOF
#define HAVE_PCAP_BREAKLOOP 1
_ACEOF
fi
done
ac_fn_c_check_func "$LINENO" "pcap_dump_ftell" "ac_cv_func_pcap_dump_ftell"
if test "x$ac_cv_func_pcap_dump_ftell" = xyes; then :
$as_echo "#define HAVE_PCAP_DUMP_FTELL 1" >>confdefs.h
else
case " $LIBOBJS " in
*" pcap_dump_ftell.$ac_objext "* ) ;;
*) LIBOBJS="$LIBOBJS pcap_dump_ftell.$ac_objext"
;;
esac
fi
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
#
# Do we have the new open API? Check for pcap_create, and assume that,
# if we do, we also have pcap_activate() and the other new routines
# introduced in libpcap 1.0.0.
#
for ac_func in pcap_create
do :
ac_fn_c_check_func "$LINENO" "pcap_create" "ac_cv_func_pcap_create"
if test "x$ac_cv_func_pcap_create" = xyes; then :
cat >>confdefs.h <<_ACEOF
#define HAVE_PCAP_CREATE 1
_ACEOF
Albert Chin's patch to libpcap's configure.in: AC_CHECK_DECLS will define the HAVE_DECL_xxx variable whether it succeeds or fails, so you can't erase a "no" result and try again with a different header. Use AC_CHECK_DECL, which doesn't define HAVE_DECL_xxx, and then explicitly define it based on whether we found a declaration or not. is required for tcpdump's configure.in as well.
2005-04-24 09:25:23 +08:00
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
fi
done
if test $ac_cv_func_pcap_create = "yes" ; then
#
# OK, do we have pcap_set_tstamp_type? If so, assume we have
# pcap_list_tstamp_types and pcap_free_tstamp_types as well.
#
for ac_func in pcap_set_tstamp_type
do :
ac_fn_c_check_func "$LINENO" "pcap_set_tstamp_type" "ac_cv_func_pcap_set_tstamp_type"
if test "x$ac_cv_func_pcap_set_tstamp_type" = xyes; then :
cat >>confdefs.h <<_ACEOF
#define HAVE_PCAP_SET_TSTAMP_TYPE 1
_ACEOF
Albert Chin's patch to libpcap's configure.in: AC_CHECK_DECLS will define the HAVE_DECL_xxx variable whether it succeeds or fails, so you can't erase a "no" result and try again with a different header. Use AC_CHECK_DECL, which doesn't define HAVE_DECL_xxx, and then explicitly define it based on whether we found a declaration or not. is required for tcpdump's configure.in as well.
2005-04-24 09:25:23 +08:00
Allow builds if libpcap doesn't have pcap_set_tstamp_precision(). Check for pcap_set_tstamp_precision() in the configure script and, if it's not there, don't include the code that allows time stamp precisions to be set.
2014-06-26 03:06:35 +08:00
fi
done
#
# And do we have pcap_set_tstamp_precision? If so, we assume
# we also have pcap_open_offline_with_tstamp_precision.
#
for ac_func in pcap_set_tstamp_precision
do :
ac_fn_c_check_func "$LINENO" "pcap_set_tstamp_precision" "ac_cv_func_pcap_set_tstamp_precision"
if test "x$ac_cv_func_pcap_set_tstamp_precision" = xyes; then :
cat >>confdefs.h <<_ACEOF
#define HAVE_PCAP_SET_TSTAMP_PRECISION 1
_ACEOF
Fix build issues with the OpenFlow printer on some systems. Don't assume we have <stdint.h>. Instead, use the AC_TYPE_ macros to ensure we have the C99 intN_t and uintN_t types; we already include <inttypes.h> in tcpdump-stdinc.h iff we have it. Get rid of the structure declarations in openflow-1.0.h, as they have zero-length arrays (not supported by all the compilers people might be using) and as 1) they're only used in sizeof() and 2) after each one there's an assertion to check that sizeof() returns a specific numerical value so, instead, just #define various _LEN items to those numerical values and use them. Add an openflow.h header with a #define for the length of the basic header, and move the declaration of of10_header_body_print() there.
2013-06-24 05:03:38 +08:00
fi
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
done
Fix build issues with the OpenFlow printer on some systems. Don't assume we have <stdint.h>. Instead, use the AC_TYPE_ macros to ensure we have the C99 intN_t and uintN_t types; we already include <inttypes.h> in tcpdump-stdinc.h iff we have it. Get rid of the structure declarations in openflow-1.0.h, as they have zero-length arrays (not supported by all the compilers people might be using) and as 1) they're only used in sizeof() and 2) after each one there's an assertion to check that sizeof() returns a specific numerical value so, instead, just #define various _LEN items to those numerical values and use them. Add an openflow.h header with a #define for the length of the basic header, and move the declaration of of10_header_body_print() there.
2013-06-24 05:03:38 +08:00
fi
Use immediate mode if available. If libpcap has pcap_set_immediate_mode(), then default to immediate mode if we're printing packets to a terminal, and use immediate mode if --immediate-mode is specified.
2015-02-11 06:55:43 +08:00
#
# Check for a miscellaneous collection of functions which we use
# if we have them.
#
Add support for remote capture if libpcap supports it.
2017-10-21 02:26:57 +08:00
for ac_func in pcap_findalldevs
Use pcap_dump_ftell64() if we have it. That way, even if a file offset doesn't fit in a long, we can still handle a -C flag specifying a maximum file size >=2GB.
2017-09-30 16:10:29 +08:00
do :
Add support for remote capture if libpcap supports it.
2017-10-21 02:26:57 +08:00
ac_fn_c_check_func "$LINENO" "pcap_findalldevs" "ac_cv_func_pcap_findalldevs"
if test "x$ac_cv_func_pcap_findalldevs" = xyes; then :
Use pcap_dump_ftell64() if we have it. That way, even if a file offset doesn't fit in a long, we can still handle a -C flag specifying a maximum file size >=2GB.
2017-09-30 16:10:29 +08:00
cat >>confdefs.h <<_ACEOF
Add support for remote capture if libpcap supports it.
2017-10-21 02:26:57 +08:00
#define HAVE_PCAP_FINDALLDEVS 1
Fix build issues with the OpenFlow printer on some systems. Don't assume we have <stdint.h>. Instead, use the AC_TYPE_ macros to ensure we have the C99 intN_t and uintN_t types; we already include <inttypes.h> in tcpdump-stdinc.h iff we have it. Get rid of the structure declarations in openflow-1.0.h, as they have zero-length arrays (not supported by all the compilers people might be using) and as 1) they're only used in sizeof() and 2) after each one there's an assertion to check that sizeof() returns a specific numerical value so, instead, just #define various _LEN items to those numerical values and use them. Add an openflow.h header with a #define for the length of the basic header, and move the declaration of of10_header_body_print() there.
2013-06-24 05:03:38 +08:00
_ACEOF
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
fi
done
Fix build issues with the OpenFlow printer on some systems. Don't assume we have <stdint.h>. Instead, use the AC_TYPE_ macros to ensure we have the C99 intN_t and uintN_t types; we already include <inttypes.h> in tcpdump-stdinc.h iff we have it. Get rid of the structure declarations in openflow-1.0.h, as they have zero-length arrays (not supported by all the compilers people might be using) and as 1) they're only used in sizeof() and 2) after each one there's an assertion to check that sizeof() returns a specific numerical value so, instead, just #define various _LEN items to those numerical values and use them. Add an openflow.h header with a #define for the length of the basic header, and move the declaration of of10_header_body_print() there.
2013-06-24 05:03:38 +08:00
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
if test $ac_cv_func_pcap_findalldevs = "yes" ; then
savedcppflags="$CPPFLAGS"
CPPFLAGS="$CPPFLAGS $V_INCLS"
ac_fn_c_check_type "$LINENO" "pcap_if_t" "ac_cv_type_pcap_if_t" "#include <pcap.h>
"
if test "x$ac_cv_type_pcap_if_t" = xyes; then :
cat >>confdefs.h <<_ACEOF
#define HAVE_PCAP_IF_T 1
Fix build issues with the OpenFlow printer on some systems. Don't assume we have <stdint.h>. Instead, use the AC_TYPE_ macros to ensure we have the C99 intN_t and uintN_t types; we already include <inttypes.h> in tcpdump-stdinc.h iff we have it. Get rid of the structure declarations in openflow-1.0.h, as they have zero-length arrays (not supported by all the compilers people might be using) and as 1) they're only used in sizeof() and 2) after each one there's an assertion to check that sizeof() returns a specific numerical value so, instead, just #define various _LEN items to those numerical values and use them. Add an openflow.h header with a #define for the length of the basic header, and move the declaration of of10_header_body_print() there.
2013-06-24 05:03:38 +08:00
_ACEOF
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
fi
CPPFLAGS="$savedcppflags"
fi
Add support for remote capture if libpcap supports it.
2017-10-21 02:26:57 +08:00
for ac_func in pcap_dump_flush pcap_lib_version
do :
as_ac_var=`$as_echo "ac_cv_func_$ac_func" | $as_tr_sh`
ac_fn_c_check_func "$LINENO" "$ac_func" "$as_ac_var"
if eval test \"x\$"$as_ac_var"\" = x"yes"; then :
cat >>confdefs.h <<_ACEOF
#define `$as_echo "HAVE_$ac_func" | $as_tr_cpp` 1
_ACEOF
fi
done
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
if test $ac_cv_func_pcap_lib_version = "no" ; then
{ $as_echo "$as_me:${as_lineno-$LINENO}: checking whether pcap_version is defined by libpcap" >&5
$as_echo_n "checking whether pcap_version is defined by libpcap... " >&6; }
cat confdefs.h - <<_ACEOF >conftest.$ac_ext
Fix build issues with the OpenFlow printer on some systems. Don't assume we have <stdint.h>. Instead, use the AC_TYPE_ macros to ensure we have the C99 intN_t and uintN_t types; we already include <inttypes.h> in tcpdump-stdinc.h iff we have it. Get rid of the structure declarations in openflow-1.0.h, as they have zero-length arrays (not supported by all the compilers people might be using) and as 1) they're only used in sizeof() and 2) after each one there's an assertion to check that sizeof() returns a specific numerical value so, instead, just #define various _LEN items to those numerical values and use them. Add an openflow.h header with a #define for the length of the basic header, and move the declaration of of10_header_body_print() there.
2013-06-24 05:03:38 +08:00
/* end confdefs.h. */
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
Fix build issues with the OpenFlow printer on some systems. Don't assume we have <stdint.h>. Instead, use the AC_TYPE_ macros to ensure we have the C99 intN_t and uintN_t types; we already include <inttypes.h> in tcpdump-stdinc.h iff we have it. Get rid of the structure declarations in openflow-1.0.h, as they have zero-length arrays (not supported by all the compilers people might be using) and as 1) they're only used in sizeof() and 2) after each one there's an assertion to check that sizeof() returns a specific numerical value so, instead, just #define various _LEN items to those numerical values and use them. Add an openflow.h header with a #define for the length of the basic header, and move the declaration of of10_header_body_print() there.
2013-06-24 05:03:38 +08:00
int
main ()
{
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
extern char pcap_version[];
return (int)pcap_version;
Fix build issues with the OpenFlow printer on some systems. Don't assume we have <stdint.h>. Instead, use the AC_TYPE_ macros to ensure we have the C99 intN_t and uintN_t types; we already include <inttypes.h> in tcpdump-stdinc.h iff we have it. Get rid of the structure declarations in openflow-1.0.h, as they have zero-length arrays (not supported by all the compilers people might be using) and as 1) they're only used in sizeof() and 2) after each one there's an assertion to check that sizeof() returns a specific numerical value so, instead, just #define various _LEN items to those numerical values and use them. Add an openflow.h header with a #define for the length of the basic header, and move the declaration of of10_header_body_print() there.
2013-06-24 05:03:38 +08:00
;
return 0;
}
_ACEOF
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
if ac_fn_c_try_link "$LINENO"; then :
ac_lbl_cv_pcap_version_defined=yes
else
ac_lbl_cv_pcap_version_defined=no
fi
rm -f core conftest.err conftest.$ac_objext \
conftest$ac_exeext conftest.$ac_ext
if test "$ac_lbl_cv_pcap_version_defined" = yes ; then
configure: add support for cap-ng package It uses '--with-cap-ng', for using libcap-ng [default=yes, if available]
2015-02-15 22:32:23 +08:00
{ $as_echo "$as_me:${as_lineno-$LINENO}: result: yes" >&5
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
$as_echo "yes" >&6; }
$as_echo "#define HAVE_PCAP_VERSION 1" >>confdefs.h
else
{ $as_echo "$as_me:${as_lineno-$LINENO}: result: no" >&5
$as_echo "no" >&6; }
fi
fi
Add support for remote capture if libpcap supports it.
2017-10-21 02:26:57 +08:00
for ac_func in pcap_setdirection pcap_set_immediate_mode pcap_dump_ftell64
do :
as_ac_var=`$as_echo "ac_cv_func_$ac_func" | $as_tr_sh`
ac_fn_c_check_func "$LINENO" "$ac_func" "$as_ac_var"
if eval test \"x\$"$as_ac_var"\" = x"yes"; then :
cat >>confdefs.h <<_ACEOF
#define `$as_echo "HAVE_$ac_func" | $as_tr_cpp` 1
_ACEOF
fi
done
for ac_func in pcap_open pcap_findalldevs_ex
do :
as_ac_var=`$as_echo "ac_cv_func_$ac_func" | $as_tr_sh`
ac_fn_c_check_func "$LINENO" "$ac_func" "$as_ac_var"
if eval test \"x\$"$as_ac_var"\" = x"yes"; then :
cat >>confdefs.h <<_ACEOF
#define `$as_echo "HAVE_$ac_func" | $as_tr_cpp` 1
_ACEOF
fi
done
Use the new debugging routines in libpcap. Newer versions of libpcap, when configured to provide debugging printouts for the filter expression parser or optimizer, provide routines to set the "debug the parser" and "debug the optimizer" flags; use them if the library has them. If the library doesn't have them, do our best to try to use the older mechanisms for requesting debugging, if present.
2015-12-31 10:49:37 +08:00
#
# Check for special debugging functions
#
for ac_func in pcap_set_parser_debug
do :
ac_fn_c_check_func "$LINENO" "pcap_set_parser_debug" "ac_cv_func_pcap_set_parser_debug"
if test "x$ac_cv_func_pcap_set_parser_debug" = xyes; then :
cat >>confdefs.h <<_ACEOF
#define HAVE_PCAP_SET_PARSER_DEBUG 1
_ACEOF
fi
done
if test "$ac_cv_func_pcap_set_parser_debug" = "no" ; then
#
# OK, we don't have pcap_set_parser_debug() to set the libpcap
# filter expression parser debug flag; can we directly set the
# flag?
{ $as_echo "$as_me:${as_lineno-$LINENO}: checking whether pcap_debug is defined by libpcap" >&5
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
$as_echo_n "checking whether pcap_debug is defined by libpcap... " >&6; }
Use the new debugging routines in libpcap. Newer versions of libpcap, when configured to provide debugging printouts for the filter expression parser or optimizer, provide routines to set the "debug the parser" and "debug the optimizer" flags; use them if the library has them. If the library doesn't have them, do our best to try to use the older mechanisms for requesting debugging, if present.
2015-12-31 10:49:37 +08:00
cat confdefs.h - <<_ACEOF >conftest.$ac_ext
Fix build issues with the OpenFlow printer on some systems. Don't assume we have <stdint.h>. Instead, use the AC_TYPE_ macros to ensure we have the C99 intN_t and uintN_t types; we already include <inttypes.h> in tcpdump-stdinc.h iff we have it. Get rid of the structure declarations in openflow-1.0.h, as they have zero-length arrays (not supported by all the compilers people might be using) and as 1) they're only used in sizeof() and 2) after each one there's an assertion to check that sizeof() returns a specific numerical value so, instead, just #define various _LEN items to those numerical values and use them. Add an openflow.h header with a #define for the length of the basic header, and move the declaration of of10_header_body_print() there.
2013-06-24 05:03:38 +08:00
/* end confdefs.h. */
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
Fix build issues with the OpenFlow printer on some systems. Don't assume we have <stdint.h>. Instead, use the AC_TYPE_ macros to ensure we have the C99 intN_t and uintN_t types; we already include <inttypes.h> in tcpdump-stdinc.h iff we have it. Get rid of the structure declarations in openflow-1.0.h, as they have zero-length arrays (not supported by all the compilers people might be using) and as 1) they're only used in sizeof() and 2) after each one there's an assertion to check that sizeof() returns a specific numerical value so, instead, just #define various _LEN items to those numerical values and use them. Add an openflow.h header with a #define for the length of the basic header, and move the declaration of of10_header_body_print() there.
2013-06-24 05:03:38 +08:00
int
main ()
{
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
Use the new debugging routines in libpcap. Newer versions of libpcap, when configured to provide debugging printouts for the filter expression parser or optimizer, provide routines to set the "debug the parser" and "debug the optimizer" flags; use them if the library has them. If the library doesn't have them, do our best to try to use the older mechanisms for requesting debugging, if present.
2015-12-31 10:49:37 +08:00
extern int pcap_debug;
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
Use the new debugging routines in libpcap. Newer versions of libpcap, when configured to provide debugging printouts for the filter expression parser or optimizer, provide routines to set the "debug the parser" and "debug the optimizer" flags; use them if the library has them. If the library doesn't have them, do our best to try to use the older mechanisms for requesting debugging, if present.
2015-12-31 10:49:37 +08:00
return pcap_debug;
Fix build issues with the OpenFlow printer on some systems. Don't assume we have <stdint.h>. Instead, use the AC_TYPE_ macros to ensure we have the C99 intN_t and uintN_t types; we already include <inttypes.h> in tcpdump-stdinc.h iff we have it. Get rid of the structure declarations in openflow-1.0.h, as they have zero-length arrays (not supported by all the compilers people might be using) and as 1) they're only used in sizeof() and 2) after each one there's an assertion to check that sizeof() returns a specific numerical value so, instead, just #define various _LEN items to those numerical values and use them. Add an openflow.h header with a #define for the length of the basic header, and move the declaration of of10_header_body_print() there.
2013-06-24 05:03:38 +08:00
;
return 0;
}
_ACEOF
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
if ac_fn_c_try_link "$LINENO"; then :
ac_lbl_cv_pcap_debug_defined=yes
Fix build issues with the OpenFlow printer on some systems. Don't assume we have <stdint.h>. Instead, use the AC_TYPE_ macros to ensure we have the C99 intN_t and uintN_t types; we already include <inttypes.h> in tcpdump-stdinc.h iff we have it. Get rid of the structure declarations in openflow-1.0.h, as they have zero-length arrays (not supported by all the compilers people might be using) and as 1) they're only used in sizeof() and 2) after each one there's an assertion to check that sizeof() returns a specific numerical value so, instead, just #define various _LEN items to those numerical values and use them. Add an openflow.h header with a #define for the length of the basic header, and move the declaration of of10_header_body_print() there.
2013-06-24 05:03:38 +08:00
else
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
ac_lbl_cv_pcap_debug_defined=no
Fix build issues with the OpenFlow printer on some systems. Don't assume we have <stdint.h>. Instead, use the AC_TYPE_ macros to ensure we have the C99 intN_t and uintN_t types; we already include <inttypes.h> in tcpdump-stdinc.h iff we have it. Get rid of the structure declarations in openflow-1.0.h, as they have zero-length arrays (not supported by all the compilers people might be using) and as 1) they're only used in sizeof() and 2) after each one there's an assertion to check that sizeof() returns a specific numerical value so, instead, just #define various _LEN items to those numerical values and use them. Add an openflow.h header with a #define for the length of the basic header, and move the declaration of of10_header_body_print() there.
2013-06-24 05:03:38 +08:00
fi
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
rm -f core conftest.err conftest.$ac_objext \
conftest$ac_exeext conftest.$ac_ext
Use the new debugging routines in libpcap. Newer versions of libpcap, when configured to provide debugging printouts for the filter expression parser or optimizer, provide routines to set the "debug the parser" and "debug the optimizer" flags; use them if the library has them. If the library doesn't have them, do our best to try to use the older mechanisms for requesting debugging, if present.
2015-12-31 10:49:37 +08:00
if test "$ac_lbl_cv_pcap_debug_defined" = yes ; then
{ $as_echo "$as_me:${as_lineno-$LINENO}: result: yes" >&5
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
$as_echo "yes" >&6; }
Fix build issues with the OpenFlow printer on some systems. Don't assume we have <stdint.h>. Instead, use the AC_TYPE_ macros to ensure we have the C99 intN_t and uintN_t types; we already include <inttypes.h> in tcpdump-stdinc.h iff we have it. Get rid of the structure declarations in openflow-1.0.h, as they have zero-length arrays (not supported by all the compilers people might be using) and as 1) they're only used in sizeof() and 2) after each one there's an assertion to check that sizeof() returns a specific numerical value so, instead, just #define various _LEN items to those numerical values and use them. Add an openflow.h header with a #define for the length of the basic header, and move the declaration of of10_header_body_print() there.
2013-06-24 05:03:38 +08:00
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
$as_echo "#define HAVE_PCAP_DEBUG 1" >>confdefs.h
Fix build issues with the OpenFlow printer on some systems. Don't assume we have <stdint.h>. Instead, use the AC_TYPE_ macros to ensure we have the C99 intN_t and uintN_t types; we already include <inttypes.h> in tcpdump-stdinc.h iff we have it. Get rid of the structure declarations in openflow-1.0.h, as they have zero-length arrays (not supported by all the compilers people might be using) and as 1) they're only used in sizeof() and 2) after each one there's an assertion to check that sizeof() returns a specific numerical value so, instead, just #define various _LEN items to those numerical values and use them. Add an openflow.h header with a #define for the length of the basic header, and move the declaration of of10_header_body_print() there.
2013-06-24 05:03:38 +08:00
Use the new debugging routines in libpcap. Newer versions of libpcap, when configured to provide debugging printouts for the filter expression parser or optimizer, provide routines to set the "debug the parser" and "debug the optimizer" flags; use them if the library has them. If the library doesn't have them, do our best to try to use the older mechanisms for requesting debugging, if present.
2015-12-31 10:49:37 +08:00
else
{ $as_echo "$as_me:${as_lineno-$LINENO}: result: no" >&5
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
$as_echo "no" >&6; }
Use the new debugging routines in libpcap. Newer versions of libpcap, when configured to provide debugging printouts for the filter expression parser or optimizer, provide routines to set the "debug the parser" and "debug the optimizer" flags; use them if the library has them. If the library doesn't have them, do our best to try to use the older mechanisms for requesting debugging, if present.
2015-12-31 10:49:37 +08:00
#
# OK, what about "yydebug"?
#
{ $as_echo "$as_me:${as_lineno-$LINENO}: checking whether yydebug is defined by libpcap" >&5
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
$as_echo_n "checking whether yydebug is defined by libpcap... " >&6; }
Use the new debugging routines in libpcap. Newer versions of libpcap, when configured to provide debugging printouts for the filter expression parser or optimizer, provide routines to set the "debug the parser" and "debug the optimizer" flags; use them if the library has them. If the library doesn't have them, do our best to try to use the older mechanisms for requesting debugging, if present.
2015-12-31 10:49:37 +08:00
cat confdefs.h - <<_ACEOF >conftest.$ac_ext
Fix build issues with the OpenFlow printer on some systems. Don't assume we have <stdint.h>. Instead, use the AC_TYPE_ macros to ensure we have the C99 intN_t and uintN_t types; we already include <inttypes.h> in tcpdump-stdinc.h iff we have it. Get rid of the structure declarations in openflow-1.0.h, as they have zero-length arrays (not supported by all the compilers people might be using) and as 1) they're only used in sizeof() and 2) after each one there's an assertion to check that sizeof() returns a specific numerical value so, instead, just #define various _LEN items to those numerical values and use them. Add an openflow.h header with a #define for the length of the basic header, and move the declaration of of10_header_body_print() there.
2013-06-24 05:03:38 +08:00
/* end confdefs.h. */
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
Fix build issues with the OpenFlow printer on some systems. Don't assume we have <stdint.h>. Instead, use the AC_TYPE_ macros to ensure we have the C99 intN_t and uintN_t types; we already include <inttypes.h> in tcpdump-stdinc.h iff we have it. Get rid of the structure declarations in openflow-1.0.h, as they have zero-length arrays (not supported by all the compilers people might be using) and as 1) they're only used in sizeof() and 2) after each one there's an assertion to check that sizeof() returns a specific numerical value so, instead, just #define various _LEN items to those numerical values and use them. Add an openflow.h header with a #define for the length of the basic header, and move the declaration of of10_header_body_print() there.
2013-06-24 05:03:38 +08:00
int
main ()
{
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
Use the new debugging routines in libpcap. Newer versions of libpcap, when configured to provide debugging printouts for the filter expression parser or optimizer, provide routines to set the "debug the parser" and "debug the optimizer" flags; use them if the library has them. If the library doesn't have them, do our best to try to use the older mechanisms for requesting debugging, if present.
2015-12-31 10:49:37 +08:00
extern int yydebug;
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
Use the new debugging routines in libpcap. Newer versions of libpcap, when configured to provide debugging printouts for the filter expression parser or optimizer, provide routines to set the "debug the parser" and "debug the optimizer" flags; use them if the library has them. If the library doesn't have them, do our best to try to use the older mechanisms for requesting debugging, if present.
2015-12-31 10:49:37 +08:00
return yydebug;
Fix build issues with the OpenFlow printer on some systems. Don't assume we have <stdint.h>. Instead, use the AC_TYPE_ macros to ensure we have the C99 intN_t and uintN_t types; we already include <inttypes.h> in tcpdump-stdinc.h iff we have it. Get rid of the structure declarations in openflow-1.0.h, as they have zero-length arrays (not supported by all the compilers people might be using) and as 1) they're only used in sizeof() and 2) after each one there's an assertion to check that sizeof() returns a specific numerical value so, instead, just #define various _LEN items to those numerical values and use them. Add an openflow.h header with a #define for the length of the basic header, and move the declaration of of10_header_body_print() there.
2013-06-24 05:03:38 +08:00
;
return 0;
}
_ACEOF
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
if ac_fn_c_try_link "$LINENO"; then :
ac_lbl_cv_yydebug_defined=yes
else
ac_lbl_cv_yydebug_defined=no
fi
rm -f core conftest.err conftest.$ac_objext \
conftest$ac_exeext conftest.$ac_ext
Use the new debugging routines in libpcap. Newer versions of libpcap, when configured to provide debugging printouts for the filter expression parser or optimizer, provide routines to set the "debug the parser" and "debug the optimizer" flags; use them if the library has them. If the library doesn't have them, do our best to try to use the older mechanisms for requesting debugging, if present.
2015-12-31 10:49:37 +08:00
if test "$ac_lbl_cv_yydebug_defined" = yes ; then
{ $as_echo "$as_me:${as_lineno-$LINENO}: result: yes" >&5
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
$as_echo "yes" >&6; }
$as_echo "#define HAVE_YYDEBUG 1" >>confdefs.h
Use the new debugging routines in libpcap. Newer versions of libpcap, when configured to provide debugging printouts for the filter expression parser or optimizer, provide routines to set the "debug the parser" and "debug the optimizer" flags; use them if the library has them. If the library doesn't have them, do our best to try to use the older mechanisms for requesting debugging, if present.
2015-12-31 10:49:37 +08:00
else
{ $as_echo "$as_me:${as_lineno-$LINENO}: result: no" >&5
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
$as_echo "no" >&6; }
Use the new debugging routines in libpcap. Newer versions of libpcap, when configured to provide debugging printouts for the filter expression parser or optimizer, provide routines to set the "debug the parser" and "debug the optimizer" flags; use them if the library has them. If the library doesn't have them, do our best to try to use the older mechanisms for requesting debugging, if present.
2015-12-31 10:49:37 +08:00
fi
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
fi
fi
Use the new debugging routines in libpcap. Newer versions of libpcap, when configured to provide debugging printouts for the filter expression parser or optimizer, provide routines to set the "debug the parser" and "debug the optimizer" flags; use them if the library has them. If the library doesn't have them, do our best to try to use the older mechanisms for requesting debugging, if present.
2015-12-31 10:49:37 +08:00
for ac_func in pcap_set_optimizer_debug
do :
ac_fn_c_check_func "$LINENO" "pcap_set_optimizer_debug" "ac_cv_func_pcap_set_optimizer_debug"
if test "x$ac_cv_func_pcap_set_optimizer_debug" = xyes; then :
cat >>confdefs.h <<_ACEOF
#define HAVE_PCAP_SET_OPTIMIZER_DEBUG 1
_ACEOF
fi
done
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
ac_fn_c_check_func "$LINENO" "bpf_dump" "ac_cv_func_bpf_dump"
if test "x$ac_cv_func_bpf_dump" = xyes; then :
$as_echo "#define HAVE_BPF_DUMP 1" >>confdefs.h
Fix build issues with the OpenFlow printer on some systems. Don't assume we have <stdint.h>. Instead, use the AC_TYPE_ macros to ensure we have the C99 intN_t and uintN_t types; we already include <inttypes.h> in tcpdump-stdinc.h iff we have it. Get rid of the structure declarations in openflow-1.0.h, as they have zero-length arrays (not supported by all the compilers people might be using) and as 1) they're only used in sizeof() and 2) after each one there's an assertion to check that sizeof() returns a specific numerical value so, instead, just #define various _LEN items to those numerical values and use them. Add an openflow.h header with a #define for the length of the basic header, and move the declaration of of10_header_body_print() there.
2013-06-24 05:03:38 +08:00
else
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
case " $LIBOBJS " in
*" bpf_dump.$ac_objext "* ) ;;
*) LIBOBJS="$LIBOBJS bpf_dump.$ac_objext"
;;
esac
fi
V_GROUP=0
if test -f /etc/group -a ! -z "`grep '^wheel:' /etc/group`" ; then
V_GROUP=wheel
fi
#
# Assume V7/BSD convention for man pages (file formats in section 5,
# miscellaneous info in section 7).
#
MAN_FILE_FORMATS=5
MAN_MISC_INFO=7
case "$host_os" in
aix*)
$as_echo "#define _SUN 1" >>confdefs.h
;;
hpux*)
#
# Use System V conventions for man pages.
#
MAN_FILE_FORMATS=4
MAN_MISC_INFO=5
;;
irix*)
V_GROUP=sys
#
# Use System V conventions for man pages.
#
MAN_FILE_FORMATS=4
MAN_MISC_INFO=5
;;
osf*)
V_GROUP=system
#
# Use System V conventions for man pages.
#
MAN_FILE_FORMATS=4
MAN_MISC_INFO=5
;;
solaris*)
V_GROUP=sys
Fix build issues with the OpenFlow printer on some systems. Don't assume we have <stdint.h>. Instead, use the AC_TYPE_ macros to ensure we have the C99 intN_t and uintN_t types; we already include <inttypes.h> in tcpdump-stdinc.h iff we have it. Get rid of the structure declarations in openflow-1.0.h, as they have zero-length arrays (not supported by all the compilers people might be using) and as 1) they're only used in sizeof() and 2) after each one there's an assertion to check that sizeof() returns a specific numerical value so, instead, just #define various _LEN items to those numerical values and use them. Add an openflow.h header with a #define for the length of the basic header, and move the declaration of of10_header_body_print() there.
2013-06-24 05:03:38 +08:00
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
#
# Use System V conventions for man pages.
#
MAN_FILE_FORMATS=4
MAN_MISC_INFO=5
;;
esac
Fix build issues with the OpenFlow printer on some systems. Don't assume we have <stdint.h>. Instead, use the AC_TYPE_ macros to ensure we have the C99 intN_t and uintN_t types; we already include <inttypes.h> in tcpdump-stdinc.h iff we have it. Get rid of the structure declarations in openflow-1.0.h, as they have zero-length arrays (not supported by all the compilers people might be using) and as 1) they're only used in sizeof() and 2) after each one there's an assertion to check that sizeof() returns a specific numerical value so, instead, just #define various _LEN items to those numerical values and use them. Add an openflow.h header with a #define for the length of the basic header, and move the declaration of of10_header_body_print() there.
2013-06-24 05:03:38 +08:00
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
if test -f /dev/bpf0 ; then
V_GROUP=bpf
Check for extra networking libraries before checking for IPv6. On some platforms, such as SunOS 5.x, building the "do we have IPv6 support?" test program requires the extra networking libraries, so we need to know what extra networking libraries are required before doing that test.
2013-04-07 04:03:58 +08:00
fi
Albert Chin's patch to libpcap's configure.in: AC_CHECK_DECLS will define the HAVE_DECL_xxx variable whether it succeeds or fails, so you can't erase a "no" result and try again with a different header. Use AC_CHECK_DECL, which doesn't define HAVE_DECL_xxx, and then explicitly define it based on whether we found a declaration or not. is required for tcpdump's configure.in as well.
2005-04-24 09:25:23 +08:00
C compilers can, and some do, optimize away pointer underflow checks. Cast the pointers to uintptr_t; use AC_TYPE_UINTPTR_T to get uintptr_t defined on older platforms that don't define it themselves.
2015-03-03 05:25:12 +08:00
#
# Make sure we have a definition for C99's uintptr_t (regardless of
# whether the environment is a C99 environment or not).
#
ac_fn_c_check_type "$LINENO" "uintptr_t" "ac_cv_type_uintptr_t" "$ac_includes_default"
if test "x$ac_cv_type_uintptr_t" = xyes; then :
$as_echo "#define HAVE_UINTPTR_T 1" >>confdefs.h
else
for ac_type in 'unsigned int' 'unsigned long int' \
'unsigned long long int'; do
cat confdefs.h - <<_ACEOF >conftest.$ac_ext
/* end confdefs.h. */
$ac_includes_default
int
main ()
{
static int test_array [1 - 2 * !(sizeof (void *) <= sizeof ($ac_type))];
test_array [0] = 0;
return test_array [0];
;
return 0;
}
_ACEOF
if ac_fn_c_try_compile "$LINENO"; then :
cat >>confdefs.h <<_ACEOF
#define uintptr_t $ac_type
_ACEOF
ac_type=
fi
rm -f core conftest.err conftest.$ac_objext conftest.$ac_ext
test -z "$ac_type" && break
done
fi
Clean up the stuff we do to get <inttypes.h> stuff defined. If we have a libpcap with <pcap/pcap-inttypes.h>, include it, so that we don't have to worry about definitions colliding if we later include a pcap header file that includes pcap/pcap-inttypes.h. Otherwise, do the same stuff pcap-inttypes.h does. This means that, on UN*X, we require that there be an <inttypes.h> that defines everything we need. Don't bother doing checks that are no longer necessary as a result of those changes.
2017-09-15 09:53:34 +08:00
#
# Check whether we have pcap/pcap-inttypes.h.
# If we do, we use that to get the C99 types defined.
#
savedcppflags="$CPPFLAGS"
CPPFLAGS="$CPPFLAGS $V_INCLS"
for ac_header in pcap/pcap-inttypes.h
do :
ac_fn_c_check_header_mongrel "$LINENO" "pcap/pcap-inttypes.h" "ac_cv_header_pcap_pcap_inttypes_h" "$ac_includes_default"
if test "x$ac_cv_header_pcap_pcap_inttypes_h" = xyes; then :
cat >>confdefs.h <<_ACEOF
#define HAVE_PCAP_PCAP_INTTYPES_H 1
_ACEOF
fi
done
CPPFLAGS="$savedcppflags"
Fix build issues with the OpenFlow printer on some systems. Don't assume we have <stdint.h>. Instead, use the AC_TYPE_ macros to ensure we have the C99 intN_t and uintN_t types; we already include <inttypes.h> in tcpdump-stdinc.h iff we have it. Get rid of the structure declarations in openflow-1.0.h, as they have zero-length arrays (not supported by all the compilers people might be using) and as 1) they're only used in sizeof() and 2) after each one there's an assertion to check that sizeof() returns a specific numerical value so, instead, just #define various _LEN items to those numerical values and use them. Add an openflow.h header with a #define for the length of the basic header, and move the declaration of of10_header_body_print() there.
2013-06-24 05:03:38 +08:00
#
We still need u_intN_t. Some libpcap headers use them, and even if we change libpcap to use uintN_t, we don't require that tcpdump 4.x go with libpcap 1.x - we allow people to install the latest tcpdump even if they have an older libpcap and don't want to install a newer one. However, we now define them in terms of the C99 uintN_t types, rather than trying to guess what's appropriate; using unsigned long long for u_int64_t meant that, on some platforms, u_int64_t didn't match PRI[doux]64, and using unsigned long obviously won't work on ILP32 platforms. Also, we already had calls to the autoconf macros for C99 types; get rid of the ones we added. Also also, clean up a comment in tcpdump-stdinc.h.
2014-04-24 01:56:20 +08:00
# Define the old BSD specified-width types in terms of the C99 types;
# we may need them with libpcap include files.
Fix build issues with the OpenFlow printer on some systems. Don't assume we have <stdint.h>. Instead, use the AC_TYPE_ macros to ensure we have the C99 intN_t and uintN_t types; we already include <inttypes.h> in tcpdump-stdinc.h iff we have it. Get rid of the structure declarations in openflow-1.0.h, as they have zero-length arrays (not supported by all the compilers people might be using) and as 1) they're only used in sizeof() and 2) after each one there's an assertion to check that sizeof() returns a specific numerical value so, instead, just #define various _LEN items to those numerical values and use them. Add an openflow.h header with a #define for the length of the basic header, and move the declaration of of10_header_body_print() there.
2013-06-24 05:03:38 +08:00
#
We still need u_intN_t. Some libpcap headers use them, and even if we change libpcap to use uintN_t, we don't require that tcpdump 4.x go with libpcap 1.x - we allow people to install the latest tcpdump even if they have an older libpcap and don't want to install a newer one. However, we now define them in terms of the C99 uintN_t types, rather than trying to guess what's appropriate; using unsigned long long for u_int64_t meant that, on some platforms, u_int64_t didn't match PRI[doux]64, and using unsigned long obviously won't work on ILP32 platforms. Also, we already had calls to the autoconf macros for C99 types; get rid of the ones we added. Also also, clean up a comment in tcpdump-stdinc.h.
2014-04-24 01:56:20 +08:00
ac_fn_c_check_type "$LINENO" "u_int8_t" "ac_cv_type_u_int8_t" "$ac_includes_default
#include <sys/types.h>
u_intN_t is dead, long live uintN_t. And, as we require at least autoconf 2.61, and as autoconf 2.61 and later have AC_TYPE_UINTn_T and AC_TYPE_INTn_T macros, we use them to define the uintN_t and intN_t macros if the system doesn't define them for us. This lets us get rid of bitypes.h as well.
2014-04-23 15:20:40 +08:00
We still need u_intN_t. Some libpcap headers use them, and even if we change libpcap to use uintN_t, we don't require that tcpdump 4.x go with libpcap 1.x - we allow people to install the latest tcpdump even if they have an older libpcap and don't want to install a newer one. However, we now define them in terms of the C99 uintN_t types, rather than trying to guess what's appropriate; using unsigned long long for u_int64_t meant that, on some platforms, u_int64_t didn't match PRI[doux]64, and using unsigned long obviously won't work on ILP32 platforms. Also, we already had calls to the autoconf macros for C99 types; get rid of the ones we added. Also also, clean up a comment in tcpdump-stdinc.h.
2014-04-24 01:56:20 +08:00
"
if test "x$ac_cv_type_u_int8_t" = xyes; then :
respect AC_LBL_CHECK_TYPE.
1999-10-30 15:33:45 +08:00
We still need u_intN_t. Some libpcap headers use them, and even if we change libpcap to use uintN_t, we don't require that tcpdump 4.x go with libpcap 1.x - we allow people to install the latest tcpdump even if they have an older libpcap and don't want to install a newer one. However, we now define them in terms of the C99 uintN_t types, rather than trying to guess what's appropriate; using unsigned long long for u_int64_t meant that, on some platforms, u_int64_t didn't match PRI[doux]64, and using unsigned long obviously won't work on ILP32 platforms. Also, we already had calls to the autoconf macros for C99 types; get rid of the ones we added. Also also, clean up a comment in tcpdump-stdinc.h.
2014-04-24 01:56:20 +08:00
else
From Andrew Church <andrew@users.sourceforge.net>: when testing for "pcap_version", "pcap_debug", and "yydebug", don't add our own functions referring to those variables - GCC 3.4.1 optimizes the test code out before the link is done, as it's in a function that's not called.
2004-08-27 15:17:03 +08:00
We still need u_intN_t. Some libpcap headers use them, and even if we change libpcap to use uintN_t, we don't require that tcpdump 4.x go with libpcap 1.x - we allow people to install the latest tcpdump even if they have an older libpcap and don't want to install a newer one. However, we now define them in terms of the C99 uintN_t types, rather than trying to guess what's appropriate; using unsigned long long for u_int64_t meant that, on some platforms, u_int64_t didn't match PRI[doux]64, and using unsigned long obviously won't work on ILP32 platforms. Also, we already had calls to the autoconf macros for C99 types; get rid of the ones we added. Also also, clean up a comment in tcpdump-stdinc.h.
2014-04-24 01:56:20 +08:00
$as_echo "#define u_int8_t uint8_t" >>confdefs.h
We support building tcpdump with versions of libpcap other than the one with which it was released, and DLT_BLUETOOTH_HCI_H4_WITH_PHDR might be defined by pcap-bpf.h without pcap/bluetooth.h being present (as appears to be the case on Fedora 9, for example), so check whether <pcap/bluetooth.h> is usable. Update a comment - F9 appears to have a "/usr/include/pcap.h" if you install the libpcap headers. When adding -I flags when running a compiler-based test, add them to CPPFLAGS, not CFLAGS - the latter doesn't work right with AC_CHECK_HEADERS, as the "gcc -E" run doesn't have the -I flags added.
2008-09-26 05:45:50 +08:00
We still need u_intN_t. Some libpcap headers use them, and even if we change libpcap to use uintN_t, we don't require that tcpdump 4.x go with libpcap 1.x - we allow people to install the latest tcpdump even if they have an older libpcap and don't want to install a newer one. However, we now define them in terms of the C99 uintN_t types, rather than trying to guess what's appropriate; using unsigned long long for u_int64_t meant that, on some platforms, u_int64_t didn't match PRI[doux]64, and using unsigned long obviously won't work on ILP32 platforms. Also, we already had calls to the autoconf macros for C99 types; get rid of the ones we added. Also also, clean up a comment in tcpdump-stdinc.h.
2014-04-24 01:56:20 +08:00
fi
Simplify the detection of OpenSSL libcrypto by using standard autoconf macros rather than a local copy of AC_LBL_SSLEAY. AC_LBL_SSLEAY is old and has not kept pace with some more recent developments in packaging like Debian and Ubuntu's multiarch support. The autoconf macros have been updated to handle multiarch so using them means that tcpdump gains the ability to be built with libcrypto on these new multiarch distros and to work successfully with Travis CI, which uses Ubuntu 12, which is one such multiarch distro (see GH-32). Fixes GH-33
2012-10-14 02:21:45 +08:00
We still need u_intN_t. Some libpcap headers use them, and even if we change libpcap to use uintN_t, we don't require that tcpdump 4.x go with libpcap 1.x - we allow people to install the latest tcpdump even if they have an older libpcap and don't want to install a newer one. However, we now define them in terms of the C99 uintN_t types, rather than trying to guess what's appropriate; using unsigned long long for u_int64_t meant that, on some platforms, u_int64_t didn't match PRI[doux]64, and using unsigned long obviously won't work on ILP32 platforms. Also, we already had calls to the autoconf macros for C99 types; get rid of the ones we added. Also also, clean up a comment in tcpdump-stdinc.h.
2014-04-24 01:56:20 +08:00
ac_fn_c_check_type "$LINENO" "u_int16_t" "ac_cv_type_u_int16_t" "$ac_includes_default
#include <sys/types.h>
Simplify the detection of OpenSSL libcrypto by using standard autoconf macros rather than a local copy of AC_LBL_SSLEAY. AC_LBL_SSLEAY is old and has not kept pace with some more recent developments in packaging like Debian and Ubuntu's multiarch support. The autoconf macros have been updated to handle multiarch so using them means that tcpdump gains the ability to be built with libcrypto on these new multiarch distros and to work successfully with Travis CI, which uses Ubuntu 12, which is one such multiarch distro (see GH-32). Fixes GH-33
2012-10-14 02:21:45 +08:00
We still need u_intN_t. Some libpcap headers use them, and even if we change libpcap to use uintN_t, we don't require that tcpdump 4.x go with libpcap 1.x - we allow people to install the latest tcpdump even if they have an older libpcap and don't want to install a newer one. However, we now define them in terms of the C99 uintN_t types, rather than trying to guess what's appropriate; using unsigned long long for u_int64_t meant that, on some platforms, u_int64_t didn't match PRI[doux]64, and using unsigned long obviously won't work on ILP32 platforms. Also, we already had calls to the autoconf macros for C99 types; get rid of the ones we added. Also also, clean up a comment in tcpdump-stdinc.h.
2014-04-24 01:56:20 +08:00
"
if test "x$ac_cv_type_u_int16_t" = xyes; then :
Initial revision
1999-10-08 07:47:09 +08:00
We still need u_intN_t. Some libpcap headers use them, and even if we change libpcap to use uintN_t, we don't require that tcpdump 4.x go with libpcap 1.x - we allow people to install the latest tcpdump even if they have an older libpcap and don't want to install a newer one. However, we now define them in terms of the C99 uintN_t types, rather than trying to guess what's appropriate; using unsigned long long for u_int64_t meant that, on some platforms, u_int64_t didn't match PRI[doux]64, and using unsigned long obviously won't work on ILP32 platforms. Also, we already had calls to the autoconf macros for C99 types; get rid of the ones we added. Also also, clean up a comment in tcpdump-stdinc.h.
2014-04-24 01:56:20 +08:00
else
From Albert Chin: 1. On AIX, AC_LBL_C_INLINE detected the compiler supported the inline keyword which is wrong. AC_C_INLINE from autoconf-2.59 worked. 2. AC_CHECK_TYPE from autoconf-2.5x is no longer broken. Replaced AC_LBL_CHECK_TYPE with it, mainly to use <sys/bitypes.h> for Tru64 UNIX where some of the u_int#_t types are defined. 3. Tru64 UNIX 4.0D doesn't support %llx; however, it does support %lx. 4. Added <stdint.h> to interface.h for int#_t types on Tru64 UNIX 4.0D (required for missing/snprintf.c). 5. Reworked includes in tcpdump-stdinc.h for int#_t types.
2005-04-20 17:44:30 +08:00
We still need u_intN_t. Some libpcap headers use them, and even if we change libpcap to use uintN_t, we don't require that tcpdump 4.x go with libpcap 1.x - we allow people to install the latest tcpdump even if they have an older libpcap and don't want to install a newer one. However, we now define them in terms of the C99 uintN_t types, rather than trying to guess what's appropriate; using unsigned long long for u_int64_t meant that, on some platforms, u_int64_t didn't match PRI[doux]64, and using unsigned long obviously won't work on ILP32 platforms. Also, we already had calls to the autoconf macros for C99 types; get rid of the ones we added. Also also, clean up a comment in tcpdump-stdinc.h.
2014-04-24 01:56:20 +08:00
$as_echo "#define u_int16_t uint16_t" >>confdefs.h
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
We still need u_intN_t. Some libpcap headers use them, and even if we change libpcap to use uintN_t, we don't require that tcpdump 4.x go with libpcap 1.x - we allow people to install the latest tcpdump even if they have an older libpcap and don't want to install a newer one. However, we now define them in terms of the C99 uintN_t types, rather than trying to guess what's appropriate; using unsigned long long for u_int64_t meant that, on some platforms, u_int64_t didn't match PRI[doux]64, and using unsigned long obviously won't work on ILP32 platforms. Also, we already had calls to the autoconf macros for C99 types; get rid of the ones we added. Also also, clean up a comment in tcpdump-stdinc.h.
2014-04-24 01:56:20 +08:00
fi
Simplify the detection of OpenSSL libcrypto by using standard autoconf macros rather than a local copy of AC_LBL_SSLEAY. AC_LBL_SSLEAY is old and has not kept pace with some more recent developments in packaging like Debian and Ubuntu's multiarch support. The autoconf macros have been updated to handle multiarch so using them means that tcpdump gains the ability to be built with libcrypto on these new multiarch distros and to work successfully with Travis CI, which uses Ubuntu 12, which is one such multiarch distro (see GH-32). Fixes GH-33
2012-10-14 02:21:45 +08:00
We still need u_intN_t. Some libpcap headers use them, and even if we change libpcap to use uintN_t, we don't require that tcpdump 4.x go with libpcap 1.x - we allow people to install the latest tcpdump even if they have an older libpcap and don't want to install a newer one. However, we now define them in terms of the C99 uintN_t types, rather than trying to guess what's appropriate; using unsigned long long for u_int64_t meant that, on some platforms, u_int64_t didn't match PRI[doux]64, and using unsigned long obviously won't work on ILP32 platforms. Also, we already had calls to the autoconf macros for C99 types; get rid of the ones we added. Also also, clean up a comment in tcpdump-stdinc.h.
2014-04-24 01:56:20 +08:00
ac_fn_c_check_type "$LINENO" "u_int32_t" "ac_cv_type_u_int32_t" "$ac_includes_default
#include <sys/types.h>
Simplify the detection of OpenSSL libcrypto by using standard autoconf macros rather than a local copy of AC_LBL_SSLEAY. AC_LBL_SSLEAY is old and has not kept pace with some more recent developments in packaging like Debian and Ubuntu's multiarch support. The autoconf macros have been updated to handle multiarch so using them means that tcpdump gains the ability to be built with libcrypto on these new multiarch distros and to work successfully with Travis CI, which uses Ubuntu 12, which is one such multiarch distro (see GH-32). Fixes GH-33
2012-10-14 02:21:45 +08:00
We still need u_intN_t. Some libpcap headers use them, and even if we change libpcap to use uintN_t, we don't require that tcpdump 4.x go with libpcap 1.x - we allow people to install the latest tcpdump even if they have an older libpcap and don't want to install a newer one. However, we now define them in terms of the C99 uintN_t types, rather than trying to guess what's appropriate; using unsigned long long for u_int64_t meant that, on some platforms, u_int64_t didn't match PRI[doux]64, and using unsigned long obviously won't work on ILP32 platforms. Also, we already had calls to the autoconf macros for C99 types; get rid of the ones we added. Also also, clean up a comment in tcpdump-stdinc.h.
2014-04-24 01:56:20 +08:00
"
if test "x$ac_cv_type_u_int32_t" = xyes; then :
We support building tcpdump with versions of libpcap other than the one with which it was released, and DLT_BLUETOOTH_HCI_H4_WITH_PHDR might be defined by pcap-bpf.h without pcap/bluetooth.h being present (as appears to be the case on Fedora 9, for example), so check whether <pcap/bluetooth.h> is usable. Update a comment - F9 appears to have a "/usr/include/pcap.h" if you install the libpcap headers. When adding -I flags when running a compiler-based test, add them to CPPFLAGS, not CFLAGS - the latter doesn't work right with AC_CHECK_HEADERS, as the "gcc -E" run doesn't have the -I flags added.
2008-09-26 05:45:50 +08:00
We still need u_intN_t. Some libpcap headers use them, and even if we change libpcap to use uintN_t, we don't require that tcpdump 4.x go with libpcap 1.x - we allow people to install the latest tcpdump even if they have an older libpcap and don't want to install a newer one. However, we now define them in terms of the C99 uintN_t types, rather than trying to guess what's appropriate; using unsigned long long for u_int64_t meant that, on some platforms, u_int64_t didn't match PRI[doux]64, and using unsigned long obviously won't work on ILP32 platforms. Also, we already had calls to the autoconf macros for C99 types; get rid of the ones we added. Also also, clean up a comment in tcpdump-stdinc.h.
2014-04-24 01:56:20 +08:00
else
Simplify the detection of OpenSSL libcrypto by using standard autoconf macros rather than a local copy of AC_LBL_SSLEAY. AC_LBL_SSLEAY is old and has not kept pace with some more recent developments in packaging like Debian and Ubuntu's multiarch support. The autoconf macros have been updated to handle multiarch so using them means that tcpdump gains the ability to be built with libcrypto on these new multiarch distros and to work successfully with Travis CI, which uses Ubuntu 12, which is one such multiarch distro (see GH-32). Fixes GH-33
2012-10-14 02:21:45 +08:00
We still need u_intN_t. Some libpcap headers use them, and even if we change libpcap to use uintN_t, we don't require that tcpdump 4.x go with libpcap 1.x - we allow people to install the latest tcpdump even if they have an older libpcap and don't want to install a newer one. However, we now define them in terms of the C99 uintN_t types, rather than trying to guess what's appropriate; using unsigned long long for u_int64_t meant that, on some platforms, u_int64_t didn't match PRI[doux]64, and using unsigned long obviously won't work on ILP32 platforms. Also, we already had calls to the autoconf macros for C99 types; get rid of the ones we added. Also also, clean up a comment in tcpdump-stdinc.h.
2014-04-24 01:56:20 +08:00
$as_echo "#define u_int32_t uint32_t" >>confdefs.h
Initial revision
1999-10-08 07:47:09 +08:00
We still need u_intN_t. Some libpcap headers use them, and even if we change libpcap to use uintN_t, we don't require that tcpdump 4.x go with libpcap 1.x - we allow people to install the latest tcpdump even if they have an older libpcap and don't want to install a newer one. However, we now define them in terms of the C99 uintN_t types, rather than trying to guess what's appropriate; using unsigned long long for u_int64_t meant that, on some platforms, u_int64_t didn't match PRI[doux]64, and using unsigned long obviously won't work on ILP32 platforms. Also, we already had calls to the autoconf macros for C99 types; get rid of the ones we added. Also also, clean up a comment in tcpdump-stdinc.h.
2014-04-24 01:56:20 +08:00
fi
From Albert Chin: 1. On AIX, AC_LBL_C_INLINE detected the compiler supported the inline keyword which is wrong. AC_C_INLINE from autoconf-2.59 worked. 2. AC_CHECK_TYPE from autoconf-2.5x is no longer broken. Replaced AC_LBL_CHECK_TYPE with it, mainly to use <sys/bitypes.h> for Tru64 UNIX where some of the u_int#_t types are defined. 3. Tru64 UNIX 4.0D doesn't support %llx; however, it does support %lx. 4. Added <stdint.h> to interface.h for int#_t types on Tru64 UNIX 4.0D (required for missing/snprintf.c). 5. Reworked includes in tcpdump-stdinc.h for int#_t types.
2005-04-20 17:44:30 +08:00
We still need u_intN_t. Some libpcap headers use them, and even if we change libpcap to use uintN_t, we don't require that tcpdump 4.x go with libpcap 1.x - we allow people to install the latest tcpdump even if they have an older libpcap and don't want to install a newer one. However, we now define them in terms of the C99 uintN_t types, rather than trying to guess what's appropriate; using unsigned long long for u_int64_t meant that, on some platforms, u_int64_t didn't match PRI[doux]64, and using unsigned long obviously won't work on ILP32 platforms. Also, we already had calls to the autoconf macros for C99 types; get rid of the ones we added. Also also, clean up a comment in tcpdump-stdinc.h.
2014-04-24 01:56:20 +08:00
ac_fn_c_check_type "$LINENO" "u_int64_t" "ac_cv_type_u_int64_t" "$ac_includes_default
#include <sys/types.h>
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
We still need u_intN_t. Some libpcap headers use them, and even if we change libpcap to use uintN_t, we don't require that tcpdump 4.x go with libpcap 1.x - we allow people to install the latest tcpdump even if they have an older libpcap and don't want to install a newer one. However, we now define them in terms of the C99 uintN_t types, rather than trying to guess what's appropriate; using unsigned long long for u_int64_t meant that, on some platforms, u_int64_t didn't match PRI[doux]64, and using unsigned long obviously won't work on ILP32 platforms. Also, we already had calls to the autoconf macros for C99 types; get rid of the ones we added. Also also, clean up a comment in tcpdump-stdinc.h.
2014-04-24 01:56:20 +08:00
"
if test "x$ac_cv_type_u_int64_t" = xyes; then :
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
We still need u_intN_t. Some libpcap headers use them, and even if we change libpcap to use uintN_t, we don't require that tcpdump 4.x go with libpcap 1.x - we allow people to install the latest tcpdump even if they have an older libpcap and don't want to install a newer one. However, we now define them in terms of the C99 uintN_t types, rather than trying to guess what's appropriate; using unsigned long long for u_int64_t meant that, on some platforms, u_int64_t didn't match PRI[doux]64, and using unsigned long obviously won't work on ILP32 platforms. Also, we already had calls to the autoconf macros for C99 types; get rid of the ones we added. Also also, clean up a comment in tcpdump-stdinc.h.
2014-04-24 01:56:20 +08:00
else
From Andrew Church <andrew@users.sourceforge.net>: when testing for "pcap_version", "pcap_debug", and "yydebug", don't add our own functions referring to those variables - GCC 3.4.1 optimizes the test code out before the link is done, as it's in a function that's not called.
2004-08-27 15:17:03 +08:00
We still need u_intN_t. Some libpcap headers use them, and even if we change libpcap to use uintN_t, we don't require that tcpdump 4.x go with libpcap 1.x - we allow people to install the latest tcpdump even if they have an older libpcap and don't want to install a newer one. However, we now define them in terms of the C99 uintN_t types, rather than trying to guess what's appropriate; using unsigned long long for u_int64_t meant that, on some platforms, u_int64_t didn't match PRI[doux]64, and using unsigned long obviously won't work on ILP32 platforms. Also, we already had calls to the autoconf macros for C99 types; get rid of the ones we added. Also also, clean up a comment in tcpdump-stdinc.h.
2014-04-24 01:56:20 +08:00
$as_echo "#define u_int64_t uint64_t" >>confdefs.h
We support building tcpdump with versions of libpcap other than the one with which it was released, and DLT_BLUETOOTH_HCI_H4_WITH_PHDR might be defined by pcap-bpf.h without pcap/bluetooth.h being present (as appears to be the case on Fedora 9, for example), so check whether <pcap/bluetooth.h> is usable. Update a comment - F9 appears to have a "/usr/include/pcap.h" if you install the libpcap headers. When adding -I flags when running a compiler-based test, add them to CPPFLAGS, not CFLAGS - the latter doesn't work right with AC_CHECK_HEADERS, as the "gcc -E" run doesn't have the -I flags added.
2008-09-26 05:45:50 +08:00
We still need u_intN_t. Some libpcap headers use them, and even if we change libpcap to use uintN_t, we don't require that tcpdump 4.x go with libpcap 1.x - we allow people to install the latest tcpdump even if they have an older libpcap and don't want to install a newer one. However, we now define them in terms of the C99 uintN_t types, rather than trying to guess what's appropriate; using unsigned long long for u_int64_t meant that, on some platforms, u_int64_t didn't match PRI[doux]64, and using unsigned long obviously won't work on ILP32 platforms. Also, we already had calls to the autoconf macros for C99 types; get rid of the ones we added. Also also, clean up a comment in tcpdump-stdinc.h.
2014-04-24 01:56:20 +08:00
fi
Simplify the detection of OpenSSL libcrypto by using standard autoconf macros rather than a local copy of AC_LBL_SSLEAY. AC_LBL_SSLEAY is old and has not kept pace with some more recent developments in packaging like Debian and Ubuntu's multiarch support. The autoconf macros have been updated to handle multiarch so using them means that tcpdump gains the ability to be built with libcrypto on these new multiarch distros and to work successfully with Travis CI, which uses Ubuntu 12, which is one such multiarch distro (see GH-32). Fixes GH-33
2012-10-14 02:21:45 +08:00
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
#
# Check for some headers introduced in later versions of libpcap
# and used by some printers.
#
Clean up the stuff we do to get <inttypes.h> stuff defined. If we have a libpcap with <pcap/pcap-inttypes.h>, include it, so that we don't have to worry about definitions colliding if we later include a pcap header file that includes pcap/pcap-inttypes.h. Otherwise, do the same stuff pcap-inttypes.h does. This means that, on UN*X, we require that there be an <inttypes.h> that defines everything we need. Don't bother doing checks that are no longer necessary as a result of those changes.
2017-09-15 09:53:34 +08:00
# Those headers might use the {u_}intN_t types, so we must do this
# after we check for what's needed to get them defined.
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
#
savedcppflags="$CPPFLAGS"
CPPFLAGS="$CPPFLAGS $V_INCLS"
for ac_header in pcap/bluetooth.h
do :
Rename 'tcpdump-stdinc.h' to 'netdissect-stdinc.h' Get the full log via: git log --follow netdissect-stdinc.h
2015-09-10 04:42:38 +08:00
ac_fn_c_check_header_compile "$LINENO" "pcap/bluetooth.h" "ac_cv_header_pcap_bluetooth_h" "#include \"netdissect-stdinc.h\"
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
"
if test "x$ac_cv_header_pcap_bluetooth_h" = xyes; then :
cat >>confdefs.h <<_ACEOF
#define HAVE_PCAP_BLUETOOTH_H 1
_ACEOF
Check for extra networking libraries before checking for IPv6. On some platforms, such as SunOS 5.x, building the "do we have IPv6 support?" test program requires the extra networking libraries, so we need to know what extra networking libraries are required before doing that test.
2013-04-07 04:03:58 +08:00
fi
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
done
Use the new libpcap <pcap/nflog.h> for NFLOG definitions and declarations. Use the header file for information about LINKTYPE_NFLOG files. Don't build the NFLOG printer if we don't have that header file. Fix some checks for pcap/XXX.h header files to look for "tcpdump-stdinc.h" rather than <tcpdump-stdinc.h>, so that we don't fail to find that header.
2014-02-03 12:14:26 +08:00
for ac_header in pcap/nflog.h
do :
Rename 'tcpdump-stdinc.h' to 'netdissect-stdinc.h' Get the full log via: git log --follow netdissect-stdinc.h
2015-09-10 04:42:38 +08:00
ac_fn_c_check_header_compile "$LINENO" "pcap/nflog.h" "ac_cv_header_pcap_nflog_h" "#include \"netdissect-stdinc.h\"
Use the new libpcap <pcap/nflog.h> for NFLOG definitions and declarations. Use the header file for information about LINKTYPE_NFLOG files. Don't build the NFLOG printer if we don't have that header file. Fix some checks for pcap/XXX.h header files to look for "tcpdump-stdinc.h" rather than <tcpdump-stdinc.h>, so that we don't fail to find that header.
2014-02-03 12:14:26 +08:00
"
if test "x$ac_cv_header_pcap_nflog_h" = xyes; then :
cat >>confdefs.h <<_ACEOF
#define HAVE_PCAP_NFLOG_H 1
_ACEOF
fi
done
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
for ac_header in pcap/usb.h
do :
Rename 'tcpdump-stdinc.h' to 'netdissect-stdinc.h' Get the full log via: git log --follow netdissect-stdinc.h
2015-09-10 04:42:38 +08:00
ac_fn_c_check_header_compile "$LINENO" "pcap/usb.h" "ac_cv_header_pcap_usb_h" "#include \"netdissect-stdinc.h\"
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
"
if test "x$ac_cv_header_pcap_usb_h" = xyes; then :
Include <tcpdump-stdinc.h> when checking for headers. Now that we're setting V_INCLS correctly, we don't need to include "tcpdump-stdinc.h" - including <tcpdump-stdinc.h> works. This also picks up configure changes from the previous configure.in change.
2011-04-05 03:07:11 +08:00
cat >>confdefs.h <<_ACEOF
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
#define HAVE_PCAP_USB_H 1
Include <tcpdump-stdinc.h> when checking for headers. Now that we're setting V_INCLS correctly, we don't need to include "tcpdump-stdinc.h" - including <tcpdump-stdinc.h> works. This also picks up configure changes from the previous configure.in change.
2011-04-05 03:07:11 +08:00
_ACEOF
fi
done
CPPFLAGS="$savedcppflags"
Run ranlib on libnetdissect.a if necessary. Remove it before building it, so we discard any stuff already in the archive.
2008-02-05 04:42:09 +08:00
if test -n "$ac_tool_prefix"; then
# Extract the first word of "${ac_tool_prefix}ranlib", so it can be a program name with args.
set dummy ${ac_tool_prefix}ranlib; ac_word=$2
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
{ $as_echo "$as_me:${as_lineno-$LINENO}: checking for $ac_word" >&5
$as_echo_n "checking for $ac_word... " >&6; }
if ${ac_cv_prog_RANLIB+:} false; then :
$as_echo_n "(cached) " >&6
Run ranlib on libnetdissect.a if necessary. Remove it before building it, so we discard any stuff already in the archive.
2008-02-05 04:42:09 +08:00
else
if test -n "$RANLIB"; then
ac_cv_prog_RANLIB="$RANLIB" # Let the user override the test.
else
as_save_IFS=$IFS; IFS=$PATH_SEPARATOR
for as_dir in $PATH
do
IFS=$as_save_IFS
test -z "$as_dir" && as_dir=.
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
for ac_exec_ext in '' $ac_executable_extensions; do
if as_fn_executable_p "$as_dir/$ac_word$ac_exec_ext"; then
Run ranlib on libnetdissect.a if necessary. Remove it before building it, so we discard any stuff already in the archive.
2008-02-05 04:42:09 +08:00
ac_cv_prog_RANLIB="${ac_tool_prefix}ranlib"
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
$as_echo "$as_me:${as_lineno-$LINENO}: found $as_dir/$ac_word$ac_exec_ext" >&5
Run ranlib on libnetdissect.a if necessary. Remove it before building it, so we discard any stuff already in the archive.
2008-02-05 04:42:09 +08:00
break 2
fi
done
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
done
We support building tcpdump with versions of libpcap other than the one with which it was released, and DLT_BLUETOOTH_HCI_H4_WITH_PHDR might be defined by pcap-bpf.h without pcap/bluetooth.h being present (as appears to be the case on Fedora 9, for example), so check whether <pcap/bluetooth.h> is usable. Update a comment - F9 appears to have a "/usr/include/pcap.h" if you install the libpcap headers. When adding -I flags when running a compiler-based test, add them to CPPFLAGS, not CFLAGS - the latter doesn't work right with AC_CHECK_HEADERS, as the "gcc -E" run doesn't have the -I flags added.
2008-09-26 05:45:50 +08:00
IFS=$as_save_IFS
From Max Laier: check whether the system has <net/pfvar.h> and: if it does, use that for the pf definitions; if it doesn't, don't compile in pf support; as both OpenBSD and FreeBSD have changed the pf definitions and header format without changing the DLT value, so you can't reliably read pflog-format libpcap files on a machine running an OS version other than the one on which the file was generated.
2007-09-13 03:36:18 +08:00
Second stage of adding support for 64-bit integral data types - this causes the configure script to attempt to define the PRI[doux]64 macros if they're not defined by including <inttypes.h>, and causes "missing/bittypes.h" to attempt to define them, if undefined, in a fashion that should, with any luck, work on MSVC++ and various flavors of GNU C on Windows. Fix the spelling of "Mac OS X".
2004-04-17 16:44:49 +08:00
fi
Run ranlib on libnetdissect.a if necessary. Remove it before building it, so we discard any stuff already in the archive.
2008-02-05 04:42:09 +08:00
fi
RANLIB=$ac_cv_prog_RANLIB
if test -n "$RANLIB"; then
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
{ $as_echo "$as_me:${as_lineno-$LINENO}: result: $RANLIB" >&5
$as_echo "$RANLIB" >&6; }
Run ranlib on libnetdissect.a if necessary. Remove it before building it, so we discard any stuff already in the archive.
2008-02-05 04:42:09 +08:00
else
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
{ $as_echo "$as_me:${as_lineno-$LINENO}: result: no" >&5
$as_echo "no" >&6; }
Second stage of adding support for 64-bit integral data types - this causes the configure script to attempt to define the PRI[doux]64 macros if they're not defined by including <inttypes.h>, and causes "missing/bittypes.h" to attempt to define them, if undefined, in a fashion that should, with any luck, work on MSVC++ and various flavors of GNU C on Windows. Fix the spelling of "Mac OS X".
2004-04-17 16:44:49 +08:00
fi
We support building tcpdump with versions of libpcap other than the one with which it was released, and DLT_BLUETOOTH_HCI_H4_WITH_PHDR might be defined by pcap-bpf.h without pcap/bluetooth.h being present (as appears to be the case on Fedora 9, for example), so check whether <pcap/bluetooth.h> is usable. Update a comment - F9 appears to have a "/usr/include/pcap.h" if you install the libpcap headers. When adding -I flags when running a compiler-based test, add them to CPPFLAGS, not CFLAGS - the latter doesn't work right with AC_CHECK_HEADERS, as the "gcc -E" run doesn't have the -I flags added.
2008-09-26 05:45:50 +08:00
Run ranlib on libnetdissect.a if necessary. Remove it before building it, so we discard any stuff already in the archive.
2008-02-05 04:42:09 +08:00
fi
if test -z "$ac_cv_prog_RANLIB"; then
ac_ct_RANLIB=$RANLIB
# Extract the first word of "ranlib", so it can be a program name with args.
set dummy ranlib; ac_word=$2
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
{ $as_echo "$as_me:${as_lineno-$LINENO}: checking for $ac_word" >&5
$as_echo_n "checking for $ac_word... " >&6; }
if ${ac_cv_prog_ac_ct_RANLIB+:} false; then :
$as_echo_n "(cached) " >&6
Run ranlib on libnetdissect.a if necessary. Remove it before building it, so we discard any stuff already in the archive.
2008-02-05 04:42:09 +08:00
else
if test -n "$ac_ct_RANLIB"; then
ac_cv_prog_ac_ct_RANLIB="$ac_ct_RANLIB" # Let the user override the test.
else
as_save_IFS=$IFS; IFS=$PATH_SEPARATOR
for as_dir in $PATH
do
IFS=$as_save_IFS
test -z "$as_dir" && as_dir=.
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
for ac_exec_ext in '' $ac_executable_extensions; do
if as_fn_executable_p "$as_dir/$ac_word$ac_exec_ext"; then
Run ranlib on libnetdissect.a if necessary. Remove it before building it, so we discard any stuff already in the archive.
2008-02-05 04:42:09 +08:00
ac_cv_prog_ac_ct_RANLIB="ranlib"
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
$as_echo "$as_me:${as_lineno-$LINENO}: found $as_dir/$ac_word$ac_exec_ext" >&5
Run ranlib on libnetdissect.a if necessary. Remove it before building it, so we discard any stuff already in the archive.
2008-02-05 04:42:09 +08:00
break 2
fi
done
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
done
We support building tcpdump with versions of libpcap other than the one with which it was released, and DLT_BLUETOOTH_HCI_H4_WITH_PHDR might be defined by pcap-bpf.h without pcap/bluetooth.h being present (as appears to be the case on Fedora 9, for example), so check whether <pcap/bluetooth.h> is usable. Update a comment - F9 appears to have a "/usr/include/pcap.h" if you install the libpcap headers. When adding -I flags when running a compiler-based test, add them to CPPFLAGS, not CFLAGS - the latter doesn't work right with AC_CHECK_HEADERS, as the "gcc -E" run doesn't have the -I flags added.
2008-09-26 05:45:50 +08:00
IFS=$as_save_IFS
From Max Laier: check whether the system has <net/pfvar.h> and: if it does, use that for the pf definitions; if it doesn't, don't compile in pf support; as both OpenBSD and FreeBSD have changed the pf definitions and header format without changing the DLT value, so you can't reliably read pflog-format libpcap files on a machine running an OS version other than the one on which the file was generated.
2007-09-13 03:36:18 +08:00
Run ranlib on libnetdissect.a if necessary. Remove it before building it, so we discard any stuff already in the archive.
2008-02-05 04:42:09 +08:00
fi
fi
ac_ct_RANLIB=$ac_cv_prog_ac_ct_RANLIB
if test -n "$ac_ct_RANLIB"; then
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
{ $as_echo "$as_me:${as_lineno-$LINENO}: result: $ac_ct_RANLIB" >&5
$as_echo "$ac_ct_RANLIB" >&6; }
Run ranlib on libnetdissect.a if necessary. Remove it before building it, so we discard any stuff already in the archive.
2008-02-05 04:42:09 +08:00
else
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
{ $as_echo "$as_me:${as_lineno-$LINENO}: result: no" >&5
$as_echo "no" >&6; }
Run ranlib on libnetdissect.a if necessary. Remove it before building it, so we discard any stuff already in the archive.
2008-02-05 04:42:09 +08:00
fi
From Max Laier: check whether the system has <net/pfvar.h> and: if it does, use that for the pf definitions; if it doesn't, don't compile in pf support; as both OpenBSD and FreeBSD have changed the pf definitions and header format without changing the DLT value, so you can't reliably read pflog-format libpcap files on a machine running an OS version other than the one on which the file was generated.
2007-09-13 03:36:18 +08:00
We support building tcpdump with versions of libpcap other than the one with which it was released, and DLT_BLUETOOTH_HCI_H4_WITH_PHDR might be defined by pcap-bpf.h without pcap/bluetooth.h being present (as appears to be the case on Fedora 9, for example), so check whether <pcap/bluetooth.h> is usable. Update a comment - F9 appears to have a "/usr/include/pcap.h" if you install the libpcap headers. When adding -I flags when running a compiler-based test, add them to CPPFLAGS, not CFLAGS - the latter doesn't work right with AC_CHECK_HEADERS, as the "gcc -E" run doesn't have the -I flags added.
2008-09-26 05:45:50 +08:00
if test "x$ac_ct_RANLIB" = x; then
RANLIB=":"
else
case $cross_compiling:$ac_tool_warned in
yes:)
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
{ $as_echo "$as_me:${as_lineno-$LINENO}: WARNING: using cross tools not prefixed with host triplet" >&5
$as_echo "$as_me: WARNING: using cross tools not prefixed with host triplet" >&2;}
We support building tcpdump with versions of libpcap other than the one with which it was released, and DLT_BLUETOOTH_HCI_H4_WITH_PHDR might be defined by pcap-bpf.h without pcap/bluetooth.h being present (as appears to be the case on Fedora 9, for example), so check whether <pcap/bluetooth.h> is usable. Update a comment - F9 appears to have a "/usr/include/pcap.h" if you install the libpcap headers. When adding -I flags when running a compiler-based test, add them to CPPFLAGS, not CFLAGS - the latter doesn't work right with AC_CHECK_HEADERS, as the "gcc -E" run doesn't have the -I flags added.
2008-09-26 05:45:50 +08:00
ac_tool_warned=yes ;;
esac
RANLIB=$ac_ct_RANLIB
fi
Run ranlib on libnetdissect.a if necessary. Remove it before building it, so we discard any stuff already in the archive.
2008-02-05 04:42:09 +08:00
else
RANLIB="$ac_cv_prog_RANLIB"
Second stage of adding support for 64-bit integral data types - this causes the configure script to attempt to define the PRI[doux]64 macros if they're not defined by including <inttypes.h>, and causes "missing/bittypes.h" to attempt to define them, if undefined, in a fashion that should, with any luck, work on MSVC++ and various flavors of GNU C on Windows. Fix the spelling of "Mac OS X".
2004-04-17 16:44:49 +08:00
fi
Use AC_CHECK_TOOL to find ar. On some platforms, such as at least some versions of HP-UX, AR isn't automatically set by make.
2014-01-17 06:40:46 +08:00
if test -n "$ac_tool_prefix"; then
# Extract the first word of "${ac_tool_prefix}ar", so it can be a program name with args.
set dummy ${ac_tool_prefix}ar; ac_word=$2
{ $as_echo "$as_me:${as_lineno-$LINENO}: checking for $ac_word" >&5
$as_echo_n "checking for $ac_word... " >&6; }
if ${ac_cv_prog_AR+:} false; then :
$as_echo_n "(cached) " >&6
else
if test -n "$AR"; then
ac_cv_prog_AR="$AR" # Let the user override the test.
else
as_save_IFS=$IFS; IFS=$PATH_SEPARATOR
for as_dir in $PATH
do
IFS=$as_save_IFS
test -z "$as_dir" && as_dir=.
for ac_exec_ext in '' $ac_executable_extensions; do
if as_fn_executable_p "$as_dir/$ac_word$ac_exec_ext"; then
ac_cv_prog_AR="${ac_tool_prefix}ar"
$as_echo "$as_me:${as_lineno-$LINENO}: found $as_dir/$ac_word$ac_exec_ext" >&5
break 2
fi
done
done
IFS=$as_save_IFS
fi
fi
AR=$ac_cv_prog_AR
if test -n "$AR"; then
{ $as_echo "$as_me:${as_lineno-$LINENO}: result: $AR" >&5
$as_echo "$AR" >&6; }
else
{ $as_echo "$as_me:${as_lineno-$LINENO}: result: no" >&5
$as_echo "no" >&6; }
fi
fi
if test -z "$ac_cv_prog_AR"; then
ac_ct_AR=$AR
# Extract the first word of "ar", so it can be a program name with args.
set dummy ar; ac_word=$2
{ $as_echo "$as_me:${as_lineno-$LINENO}: checking for $ac_word" >&5
$as_echo_n "checking for $ac_word... " >&6; }
if ${ac_cv_prog_ac_ct_AR+:} false; then :
$as_echo_n "(cached) " >&6
else
if test -n "$ac_ct_AR"; then
ac_cv_prog_ac_ct_AR="$ac_ct_AR" # Let the user override the test.
else
as_save_IFS=$IFS; IFS=$PATH_SEPARATOR
for as_dir in $PATH
do
IFS=$as_save_IFS
test -z "$as_dir" && as_dir=.
for ac_exec_ext in '' $ac_executable_extensions; do
if as_fn_executable_p "$as_dir/$ac_word$ac_exec_ext"; then
ac_cv_prog_ac_ct_AR="ar"
$as_echo "$as_me:${as_lineno-$LINENO}: found $as_dir/$ac_word$ac_exec_ext" >&5
break 2
fi
done
done
IFS=$as_save_IFS
fi
fi
ac_ct_AR=$ac_cv_prog_ac_ct_AR
if test -n "$ac_ct_AR"; then
{ $as_echo "$as_me:${as_lineno-$LINENO}: result: $ac_ct_AR" >&5
$as_echo "$ac_ct_AR" >&6; }
else
{ $as_echo "$as_me:${as_lineno-$LINENO}: result: no" >&5
$as_echo "no" >&6; }
fi
if test "x$ac_ct_AR" = x; then
AR=""
else
case $cross_compiling:$ac_tool_warned in
yes:)
{ $as_echo "$as_me:${as_lineno-$LINENO}: WARNING: using cross tools not prefixed with host triplet" >&5
$as_echo "$as_me: WARNING: using cross tools not prefixed with host triplet" >&2;}
ac_tool_warned=yes ;;
esac
AR=$ac_ct_AR
fi
else
AR="$ac_cv_prog_AR"
fi
Run ranlib on libnetdissect.a if necessary. Remove it before building it, so we discard any stuff already in the archive.
2008-02-05 04:42:09 +08:00
Initial revision
1999-10-08 07:47:09 +08:00
rm -f os-proto.h
if test "${LBL_CFLAGS+set}" = set; then
V_CCOPT="$V_CCOPT ${LBL_CFLAGS}"
fi
if test -f .devel ; then
Don't try -W flags with HP's C compiler. HP's C compiler cannot be made to exit with a non-zero exit status when given an unknown compiler flag, so you can't use that to figure out if a flag is supported, but it *will* print a warning, which we don't want. In addition, it doesn't support -W flags for warnings in any case, so let's not bother with them.
2013-05-08 14:58:51 +08:00
#
Update a comment.
2013-05-13 07:10:09 +08:00
# Skip all the warning option stuff on some compilers.
Don't try -W flags with HP's C compiler. HP's C compiler cannot be made to exit with a non-zero exit status when given an unknown compiler flag, so you can't use that to figure out if a flag is supported, but it *will* print a warning, which we don't want. In addition, it doesn't support -W flags for warnings in any case, so let's not bother with them.
2013-05-08 14:58:51 +08:00
#
HP C isn't the only compiler on which we must avoid GCC-style -W flags. MIPS C and DEC C also can't be made to reliably Just Say No to those flags, and they don't support those flags, so don't try them with those compilers either.
2013-05-13 03:30:01 +08:00
if test "$ac_lbl_cc_dont_try_gcc_dashW" != yes; then
With .devel, use -W flags iff the compiler supports them. Don't base the question of whether to use a particular -W flag on whether we're compiling with GCC or not, and on which version of GCC we're using; some compilers, such as clang, also support many of those -W flags. Base it on whether the compiler complains if we use it (which means, for clang, that we have to force it to exit with a non-zero exit status if it doesn't like a flag; otherwise, we'll specify it, and clang will warn about it on every compile).
2013-05-07 14:54:20 +08:00
Fix incorrect detection of '-Wstrict-prototypes' option Revert "Simplify AC_LBL_CHECK_COMPILER_OPT a bit." (commit 43e88cd5b8e9d9d643bbad585743123492452041) The problem shows itself because 'configure' displays "checking whether the compiler supports the -Wstrict-prototypes option... no" even if '-Wstrict-prototypes' option is supported. Moreover: Update configure accordingly. Fix a trailing space.
2015-09-09 13:04:28 +08:00
{ $as_echo "$as_me:${as_lineno-$LINENO}: checking whether the compiler fails when given an unknown warning option" >&5
$as_echo_n "checking whether the compiler fails when given an unknown warning option... " >&6; }
save_CFLAGS="$CFLAGS"
CFLAGS="$CFLAGS -Wxyzzy-this-will-never-succeed-xyzzy"
cat confdefs.h - <<_ACEOF >conftest.$ac_ext
/* end confdefs.h. */
int
main ()
{
return 0
;
return 0;
}
_ACEOF
if ac_fn_c_try_compile "$LINENO"; then :
{ $as_echo "$as_me:${as_lineno-$LINENO}: result: no" >&5
$as_echo "no" >&6; }
#
# We're assuming this is clang, where
# -Werror=unknown-warning-option is the appropriate
# option to force the compiler to fail.
#
ac_lbl_unknown_warning_option_error="-Werror=unknown-warning-option"
else
{ $as_echo "$as_me:${as_lineno-$LINENO}: result: yes" >&5
$as_echo "yes" >&6; }
fi
rm -f core conftest.err conftest.$ac_objext conftest.$ac_ext
CFLAGS="$save_CFLAGS"
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
{ $as_echo "$as_me:${as_lineno-$LINENO}: checking whether the compiler supports the -Wall option" >&5
$as_echo_n "checking whether the compiler supports the -Wall option... " >&6; }
With .devel, use -W flags iff the compiler supports them. Don't base the question of whether to use a particular -W flag on whether we're compiling with GCC or not, and on which version of GCC we're using; some compilers, such as clang, also support many of those -W flags. Base it on whether the compiler complains if we use it (which means, for clang, that we have to force it to exit with a non-zero exit status if it doesn't like a flag; otherwise, we'll specify it, and clang will warn about it on every compile).
2013-05-07 14:54:20 +08:00
save_CFLAGS="$CFLAGS"
We need -Werror when testing whether -f or -m flags work. Thank you, clang, for treating unknown -f flags as warnings, only failing with them if run with -Werror, and spewing out warning messages whenever they're used.
2015-09-29 16:15:53 +08:00
if expr "x-Wall" : "x-W.*" >/dev/null
then
CFLAGS="$CFLAGS $ac_lbl_unknown_warning_option_error -Wall"
elif expr "x-Wall" : "x-f.*" >/dev/null
then
CFLAGS="$CFLAGS -Werror -Wall"
elif expr "x-Wall" : "x-m.*" >/dev/null
then
CFLAGS="$CFLAGS -Werror -Wall"
else
CFLAGS="$CFLAGS -Wall"
fi
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
cat confdefs.h - <<_ACEOF >conftest.$ac_ext
With .devel, use -W flags iff the compiler supports them. Don't base the question of whether to use a particular -W flag on whether we're compiling with GCC or not, and on which version of GCC we're using; some compilers, such as clang, also support many of those -W flags. Base it on whether the compiler complains if we use it (which means, for clang, that we have to force it to exit with a non-zero exit status if it doesn't like a flag; otherwise, we'll specify it, and clang will warn about it on every compile).
2013-05-07 14:54:20 +08:00
/* end confdefs.h. */
int
main ()
{
return 0
;
return 0;
}
_ACEOF
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
if ac_fn_c_try_compile "$LINENO"; then :
With .devel, use -W flags iff the compiler supports them. Don't base the question of whether to use a particular -W flag on whether we're compiling with GCC or not, and on which version of GCC we're using; some compilers, such as clang, also support many of those -W flags. Base it on whether the compiler complains if we use it (which means, for clang, that we have to force it to exit with a non-zero exit status if it doesn't like a flag; otherwise, we'll specify it, and clang will warn about it on every compile).
2013-05-07 14:54:20 +08:00
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
{ $as_echo "$as_me:${as_lineno-$LINENO}: result: yes" >&5
$as_echo "yes" >&6; }
With .devel, use -W flags iff the compiler supports them. Don't base the question of whether to use a particular -W flag on whether we're compiling with GCC or not, and on which version of GCC we're using; some compilers, such as clang, also support many of those -W flags. Base it on whether the compiler complains if we use it (which means, for clang, that we have to force it to exit with a non-zero exit status if it doesn't like a flag; otherwise, we'll specify it, and clang will warn about it on every compile).
2013-05-07 14:54:20 +08:00
CFLAGS="$save_CFLAGS"
V_CCOPT="$V_CCOPT -Wall"
else
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
{ $as_echo "$as_me:${as_lineno-$LINENO}: result: no" >&5
$as_echo "no" >&6; }
With .devel, use -W flags iff the compiler supports them. Don't base the question of whether to use a particular -W flag on whether we're compiling with GCC or not, and on which version of GCC we're using; some compilers, such as clang, also support many of those -W flags. Base it on whether the compiler complains if we use it (which means, for clang, that we have to force it to exit with a non-zero exit status if it doesn't like a flag; otherwise, we'll specify it, and clang will warn about it on every compile).
2013-05-07 14:54:20 +08:00
CFLAGS="$save_CFLAGS"
fi
rm -f core conftest.err conftest.$ac_objext conftest.$ac_ext
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
{ $as_echo "$as_me:${as_lineno-$LINENO}: checking whether the compiler supports the -Wmissing-prototypes option" >&5
$as_echo_n "checking whether the compiler supports the -Wmissing-prototypes option... " >&6; }
With .devel, use -W flags iff the compiler supports them. Don't base the question of whether to use a particular -W flag on whether we're compiling with GCC or not, and on which version of GCC we're using; some compilers, such as clang, also support many of those -W flags. Base it on whether the compiler complains if we use it (which means, for clang, that we have to force it to exit with a non-zero exit status if it doesn't like a flag; otherwise, we'll specify it, and clang will warn about it on every compile).
2013-05-07 14:54:20 +08:00
save_CFLAGS="$CFLAGS"
We need -Werror when testing whether -f or -m flags work. Thank you, clang, for treating unknown -f flags as warnings, only failing with them if run with -Werror, and spewing out warning messages whenever they're used.
2015-09-29 16:15:53 +08:00
if expr "x-Wmissing-prototypes" : "x-W.*" >/dev/null
then
CFLAGS="$CFLAGS $ac_lbl_unknown_warning_option_error -Wmissing-prototypes"
elif expr "x-Wmissing-prototypes" : "x-f.*" >/dev/null
then
CFLAGS="$CFLAGS -Werror -Wmissing-prototypes"
elif expr "x-Wmissing-prototypes" : "x-m.*" >/dev/null
then
CFLAGS="$CFLAGS -Werror -Wmissing-prototypes"
else
CFLAGS="$CFLAGS -Wmissing-prototypes"
fi
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
cat confdefs.h - <<_ACEOF >conftest.$ac_ext
With .devel, use -W flags iff the compiler supports them. Don't base the question of whether to use a particular -W flag on whether we're compiling with GCC or not, and on which version of GCC we're using; some compilers, such as clang, also support many of those -W flags. Base it on whether the compiler complains if we use it (which means, for clang, that we have to force it to exit with a non-zero exit status if it doesn't like a flag; otherwise, we'll specify it, and clang will warn about it on every compile).
2013-05-07 14:54:20 +08:00
/* end confdefs.h. */
int
main ()
{
return 0
;
return 0;
}
_ACEOF
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
if ac_fn_c_try_compile "$LINENO"; then :
With .devel, use -W flags iff the compiler supports them. Don't base the question of whether to use a particular -W flag on whether we're compiling with GCC or not, and on which version of GCC we're using; some compilers, such as clang, also support many of those -W flags. Base it on whether the compiler complains if we use it (which means, for clang, that we have to force it to exit with a non-zero exit status if it doesn't like a flag; otherwise, we'll specify it, and clang will warn about it on every compile).
2013-05-07 14:54:20 +08:00
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
{ $as_echo "$as_me:${as_lineno-$LINENO}: result: yes" >&5
$as_echo "yes" >&6; }
With .devel, use -W flags iff the compiler supports them. Don't base the question of whether to use a particular -W flag on whether we're compiling with GCC or not, and on which version of GCC we're using; some compilers, such as clang, also support many of those -W flags. Base it on whether the compiler complains if we use it (which means, for clang, that we have to force it to exit with a non-zero exit status if it doesn't like a flag; otherwise, we'll specify it, and clang will warn about it on every compile).
2013-05-07 14:54:20 +08:00
CFLAGS="$save_CFLAGS"
V_CCOPT="$V_CCOPT -Wmissing-prototypes"
else
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
{ $as_echo "$as_me:${as_lineno-$LINENO}: result: no" >&5
$as_echo "no" >&6; }
With .devel, use -W flags iff the compiler supports them. Don't base the question of whether to use a particular -W flag on whether we're compiling with GCC or not, and on which version of GCC we're using; some compilers, such as clang, also support many of those -W flags. Base it on whether the compiler complains if we use it (which means, for clang, that we have to force it to exit with a non-zero exit status if it doesn't like a flag; otherwise, we'll specify it, and clang will warn about it on every compile).
2013-05-07 14:54:20 +08:00
CFLAGS="$save_CFLAGS"
fi
rm -f core conftest.err conftest.$ac_objext conftest.$ac_ext
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
{ $as_echo "$as_me:${as_lineno-$LINENO}: checking whether the compiler supports the -Wstrict-prototypes option" >&5
$as_echo_n "checking whether the compiler supports the -Wstrict-prototypes option... " >&6; }
With .devel, use -W flags iff the compiler supports them. Don't base the question of whether to use a particular -W flag on whether we're compiling with GCC or not, and on which version of GCC we're using; some compilers, such as clang, also support many of those -W flags. Base it on whether the compiler complains if we use it (which means, for clang, that we have to force it to exit with a non-zero exit status if it doesn't like a flag; otherwise, we'll specify it, and clang will warn about it on every compile).
2013-05-07 14:54:20 +08:00
save_CFLAGS="$CFLAGS"
We need -Werror when testing whether -f or -m flags work. Thank you, clang, for treating unknown -f flags as warnings, only failing with them if run with -Werror, and spewing out warning messages whenever they're used.
2015-09-29 16:15:53 +08:00
if expr "x-Wstrict-prototypes" : "x-W.*" >/dev/null
then
CFLAGS="$CFLAGS $ac_lbl_unknown_warning_option_error -Wstrict-prototypes"
elif expr "x-Wstrict-prototypes" : "x-f.*" >/dev/null
then
CFLAGS="$CFLAGS -Werror -Wstrict-prototypes"
elif expr "x-Wstrict-prototypes" : "x-m.*" >/dev/null
then
CFLAGS="$CFLAGS -Werror -Wstrict-prototypes"
else
CFLAGS="$CFLAGS -Wstrict-prototypes"
fi
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
cat confdefs.h - <<_ACEOF >conftest.$ac_ext
With .devel, use -W flags iff the compiler supports them. Don't base the question of whether to use a particular -W flag on whether we're compiling with GCC or not, and on which version of GCC we're using; some compilers, such as clang, also support many of those -W flags. Base it on whether the compiler complains if we use it (which means, for clang, that we have to force it to exit with a non-zero exit status if it doesn't like a flag; otherwise, we'll specify it, and clang will warn about it on every compile).
2013-05-07 14:54:20 +08:00
/* end confdefs.h. */
int
main ()
{
return 0
;
return 0;
}
_ACEOF
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
if ac_fn_c_try_compile "$LINENO"; then :
With .devel, use -W flags iff the compiler supports them. Don't base the question of whether to use a particular -W flag on whether we're compiling with GCC or not, and on which version of GCC we're using; some compilers, such as clang, also support many of those -W flags. Base it on whether the compiler complains if we use it (which means, for clang, that we have to force it to exit with a non-zero exit status if it doesn't like a flag; otherwise, we'll specify it, and clang will warn about it on every compile).
2013-05-07 14:54:20 +08:00
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
{ $as_echo "$as_me:${as_lineno-$LINENO}: result: yes" >&5
$as_echo "yes" >&6; }
With .devel, use -W flags iff the compiler supports them. Don't base the question of whether to use a particular -W flag on whether we're compiling with GCC or not, and on which version of GCC we're using; some compilers, such as clang, also support many of those -W flags. Base it on whether the compiler complains if we use it (which means, for clang, that we have to force it to exit with a non-zero exit status if it doesn't like a flag; otherwise, we'll specify it, and clang will warn about it on every compile).
2013-05-07 14:54:20 +08:00
CFLAGS="$save_CFLAGS"
V_CCOPT="$V_CCOPT -Wstrict-prototypes"
else
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
{ $as_echo "$as_me:${as_lineno-$LINENO}: result: no" >&5
$as_echo "no" >&6; }
With .devel, use -W flags iff the compiler supports them. Don't base the question of whether to use a particular -W flag on whether we're compiling with GCC or not, and on which version of GCC we're using; some compilers, such as clang, also support many of those -W flags. Base it on whether the compiler complains if we use it (which means, for clang, that we have to force it to exit with a non-zero exit status if it doesn't like a flag; otherwise, we'll specify it, and clang will warn about it on every compile).
2013-05-07 14:54:20 +08:00
CFLAGS="$save_CFLAGS"
fi
rm -f core conftest.err conftest.$ac_objext conftest.$ac_ext
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
{ $as_echo "$as_me:${as_lineno-$LINENO}: checking whether the compiler supports the -Wwrite-strings option" >&5
$as_echo_n "checking whether the compiler supports the -Wwrite-strings option... " >&6; }
With .devel, use -W flags iff the compiler supports them. Don't base the question of whether to use a particular -W flag on whether we're compiling with GCC or not, and on which version of GCC we're using; some compilers, such as clang, also support many of those -W flags. Base it on whether the compiler complains if we use it (which means, for clang, that we have to force it to exit with a non-zero exit status if it doesn't like a flag; otherwise, we'll specify it, and clang will warn about it on every compile).
2013-05-07 14:54:20 +08:00
save_CFLAGS="$CFLAGS"
We need -Werror when testing whether -f or -m flags work. Thank you, clang, for treating unknown -f flags as warnings, only failing with them if run with -Werror, and spewing out warning messages whenever they're used.
2015-09-29 16:15:53 +08:00
if expr "x-Wwrite-strings" : "x-W.*" >/dev/null
then
CFLAGS="$CFLAGS $ac_lbl_unknown_warning_option_error -Wwrite-strings"
elif expr "x-Wwrite-strings" : "x-f.*" >/dev/null
then
CFLAGS="$CFLAGS -Werror -Wwrite-strings"
elif expr "x-Wwrite-strings" : "x-m.*" >/dev/null
then
CFLAGS="$CFLAGS -Werror -Wwrite-strings"
else
CFLAGS="$CFLAGS -Wwrite-strings"
fi
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
cat confdefs.h - <<_ACEOF >conftest.$ac_ext
With .devel, use -W flags iff the compiler supports them. Don't base the question of whether to use a particular -W flag on whether we're compiling with GCC or not, and on which version of GCC we're using; some compilers, such as clang, also support many of those -W flags. Base it on whether the compiler complains if we use it (which means, for clang, that we have to force it to exit with a non-zero exit status if it doesn't like a flag; otherwise, we'll specify it, and clang will warn about it on every compile).
2013-05-07 14:54:20 +08:00
/* end confdefs.h. */
int
main ()
{
return 0
;
return 0;
}
_ACEOF
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
if ac_fn_c_try_compile "$LINENO"; then :
With .devel, use -W flags iff the compiler supports them. Don't base the question of whether to use a particular -W flag on whether we're compiling with GCC or not, and on which version of GCC we're using; some compilers, such as clang, also support many of those -W flags. Base it on whether the compiler complains if we use it (which means, for clang, that we have to force it to exit with a non-zero exit status if it doesn't like a flag; otherwise, we'll specify it, and clang will warn about it on every compile).
2013-05-07 14:54:20 +08:00
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
{ $as_echo "$as_me:${as_lineno-$LINENO}: result: yes" >&5
$as_echo "yes" >&6; }
With .devel, use -W flags iff the compiler supports them. Don't base the question of whether to use a particular -W flag on whether we're compiling with GCC or not, and on which version of GCC we're using; some compilers, such as clang, also support many of those -W flags. Base it on whether the compiler complains if we use it (which means, for clang, that we have to force it to exit with a non-zero exit status if it doesn't like a flag; otherwise, we'll specify it, and clang will warn about it on every compile).
2013-05-07 14:54:20 +08:00
CFLAGS="$save_CFLAGS"
V_CCOPT="$V_CCOPT -Wwrite-strings"
else
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
{ $as_echo "$as_me:${as_lineno-$LINENO}: result: no" >&5
$as_echo "no" >&6; }
With .devel, use -W flags iff the compiler supports them. Don't base the question of whether to use a particular -W flag on whether we're compiling with GCC or not, and on which version of GCC we're using; some compilers, such as clang, also support many of those -W flags. Base it on whether the compiler complains if we use it (which means, for clang, that we have to force it to exit with a non-zero exit status if it doesn't like a flag; otherwise, we'll specify it, and clang will warn about it on every compile).
2013-05-07 14:54:20 +08:00
CFLAGS="$save_CFLAGS"
fi
rm -f core conftest.err conftest.$ac_objext conftest.$ac_ext
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
{ $as_echo "$as_me:${as_lineno-$LINENO}: checking whether the compiler supports the -Wpointer-arith option" >&5
$as_echo_n "checking whether the compiler supports the -Wpointer-arith option... " >&6; }
With .devel, use -W flags iff the compiler supports them. Don't base the question of whether to use a particular -W flag on whether we're compiling with GCC or not, and on which version of GCC we're using; some compilers, such as clang, also support many of those -W flags. Base it on whether the compiler complains if we use it (which means, for clang, that we have to force it to exit with a non-zero exit status if it doesn't like a flag; otherwise, we'll specify it, and clang will warn about it on every compile).
2013-05-07 14:54:20 +08:00
save_CFLAGS="$CFLAGS"
We need -Werror when testing whether -f or -m flags work. Thank you, clang, for treating unknown -f flags as warnings, only failing with them if run with -Werror, and spewing out warning messages whenever they're used.
2015-09-29 16:15:53 +08:00
if expr "x-Wpointer-arith" : "x-W.*" >/dev/null
then
CFLAGS="$CFLAGS $ac_lbl_unknown_warning_option_error -Wpointer-arith"
elif expr "x-Wpointer-arith" : "x-f.*" >/dev/null
then
CFLAGS="$CFLAGS -Werror -Wpointer-arith"
elif expr "x-Wpointer-arith" : "x-m.*" >/dev/null
then
CFLAGS="$CFLAGS -Werror -Wpointer-arith"
else
CFLAGS="$CFLAGS -Wpointer-arith"
fi
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
cat confdefs.h - <<_ACEOF >conftest.$ac_ext
With .devel, use -W flags iff the compiler supports them. Don't base the question of whether to use a particular -W flag on whether we're compiling with GCC or not, and on which version of GCC we're using; some compilers, such as clang, also support many of those -W flags. Base it on whether the compiler complains if we use it (which means, for clang, that we have to force it to exit with a non-zero exit status if it doesn't like a flag; otherwise, we'll specify it, and clang will warn about it on every compile).
2013-05-07 14:54:20 +08:00
/* end confdefs.h. */
int
main ()
{
return 0
;
return 0;
}
_ACEOF
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
if ac_fn_c_try_compile "$LINENO"; then :
With .devel, use -W flags iff the compiler supports them. Don't base the question of whether to use a particular -W flag on whether we're compiling with GCC or not, and on which version of GCC we're using; some compilers, such as clang, also support many of those -W flags. Base it on whether the compiler complains if we use it (which means, for clang, that we have to force it to exit with a non-zero exit status if it doesn't like a flag; otherwise, we'll specify it, and clang will warn about it on every compile).
2013-05-07 14:54:20 +08:00
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
{ $as_echo "$as_me:${as_lineno-$LINENO}: result: yes" >&5
$as_echo "yes" >&6; }
With .devel, use -W flags iff the compiler supports them. Don't base the question of whether to use a particular -W flag on whether we're compiling with GCC or not, and on which version of GCC we're using; some compilers, such as clang, also support many of those -W flags. Base it on whether the compiler complains if we use it (which means, for clang, that we have to force it to exit with a non-zero exit status if it doesn't like a flag; otherwise, we'll specify it, and clang will warn about it on every compile).
2013-05-07 14:54:20 +08:00
CFLAGS="$save_CFLAGS"
V_CCOPT="$V_CCOPT -Wpointer-arith"
else
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
{ $as_echo "$as_me:${as_lineno-$LINENO}: result: no" >&5
$as_echo "no" >&6; }
With .devel, use -W flags iff the compiler supports them. Don't base the question of whether to use a particular -W flag on whether we're compiling with GCC or not, and on which version of GCC we're using; some compilers, such as clang, also support many of those -W flags. Base it on whether the compiler complains if we use it (which means, for clang, that we have to force it to exit with a non-zero exit status if it doesn't like a flag; otherwise, we'll specify it, and clang will warn about it on every compile).
2013-05-07 14:54:20 +08:00
CFLAGS="$save_CFLAGS"
fi
rm -f core conftest.err conftest.$ac_objext conftest.$ac_ext
Compile with -Wcast-qual. That let me find what might have been the bulk of the 579(!) instances of "Deconst" reported in http://www.cl.cam.ac.uk/~dc552/papers/asplos15-memory-safe-c.pdf and, hopefully, will prevent more from creeping in. There are some remaining ones - and they represent attempts to overwrite the packet bytes handed to tcpdump by libpcap, which could well *fail* with, for example, memory-mapped capture mechanisms!
2015-04-27 09:50:49 +08:00
{ $as_echo "$as_me:${as_lineno-$LINENO}: checking whether the compiler supports the -Wcast-qual option" >&5
$as_echo_n "checking whether the compiler supports the -Wcast-qual option... " >&6; }
save_CFLAGS="$CFLAGS"
We need -Werror when testing whether -f or -m flags work. Thank you, clang, for treating unknown -f flags as warnings, only failing with them if run with -Werror, and spewing out warning messages whenever they're used.
2015-09-29 16:15:53 +08:00
if expr "x-Wcast-qual" : "x-W.*" >/dev/null
then
CFLAGS="$CFLAGS $ac_lbl_unknown_warning_option_error -Wcast-qual"
elif expr "x-Wcast-qual" : "x-f.*" >/dev/null
then
CFLAGS="$CFLAGS -Werror -Wcast-qual"
elif expr "x-Wcast-qual" : "x-m.*" >/dev/null
then
CFLAGS="$CFLAGS -Werror -Wcast-qual"
else
CFLAGS="$CFLAGS -Wcast-qual"
fi
Compile with -Wcast-qual. That let me find what might have been the bulk of the 579(!) instances of "Deconst" reported in http://www.cl.cam.ac.uk/~dc552/papers/asplos15-memory-safe-c.pdf and, hopefully, will prevent more from creeping in. There are some remaining ones - and they represent attempts to overwrite the packet bytes handed to tcpdump by libpcap, which could well *fail* with, for example, memory-mapped capture mechanisms!
2015-04-27 09:50:49 +08:00
cat confdefs.h - <<_ACEOF >conftest.$ac_ext
/* end confdefs.h. */
int
main ()
{
return 0
;
return 0;
}
_ACEOF
if ac_fn_c_try_compile "$LINENO"; then :
{ $as_echo "$as_me:${as_lineno-$LINENO}: result: yes" >&5
$as_echo "yes" >&6; }
CFLAGS="$save_CFLAGS"
V_CCOPT="$V_CCOPT -Wcast-qual"
else
{ $as_echo "$as_me:${as_lineno-$LINENO}: result: no" >&5
$as_echo "no" >&6; }
CFLAGS="$save_CFLAGS"
fi
rm -f core conftest.err conftest.$ac_objext conftest.$ac_ext
Compile with -Wshadow
2015-07-29 19:50:38 +08:00
{ $as_echo "$as_me:${as_lineno-$LINENO}: checking whether the compiler supports the -Wshadow option" >&5
$as_echo_n "checking whether the compiler supports the -Wshadow option... " >&6; }
save_CFLAGS="$CFLAGS"
We need -Werror when testing whether -f or -m flags work. Thank you, clang, for treating unknown -f flags as warnings, only failing with them if run with -Werror, and spewing out warning messages whenever they're used.
2015-09-29 16:15:53 +08:00
if expr "x-Wshadow" : "x-W.*" >/dev/null
then
CFLAGS="$CFLAGS $ac_lbl_unknown_warning_option_error -Wshadow"
elif expr "x-Wshadow" : "x-f.*" >/dev/null
then
CFLAGS="$CFLAGS -Werror -Wshadow"
elif expr "x-Wshadow" : "x-m.*" >/dev/null
then
CFLAGS="$CFLAGS -Werror -Wshadow"
else
CFLAGS="$CFLAGS -Wshadow"
fi
Compile with -Wshadow
2015-07-29 19:50:38 +08:00
cat confdefs.h - <<_ACEOF >conftest.$ac_ext
/* end confdefs.h. */
int
main ()
{
return 0
;
return 0;
}
_ACEOF
if ac_fn_c_try_compile "$LINENO"; then :
{ $as_echo "$as_me:${as_lineno-$LINENO}: result: yes" >&5
$as_echo "yes" >&6; }
CFLAGS="$save_CFLAGS"
V_CCOPT="$V_CCOPT -Wshadow"
else
{ $as_echo "$as_me:${as_lineno-$LINENO}: result: no" >&5
$as_echo "no" >&6; }
CFLAGS="$save_CFLAGS"
fi
rm -f core conftest.err conftest.$ac_objext conftest.$ac_ext
Compile with '-Wdeclaration-after-statement' in devel mode
2015-08-19 02:49:32 +08:00
{ $as_echo "$as_me:${as_lineno-$LINENO}: checking whether the compiler supports the -Wdeclaration-after-statement option" >&5
$as_echo_n "checking whether the compiler supports the -Wdeclaration-after-statement option... " >&6; }
save_CFLAGS="$CFLAGS"
We need -Werror when testing whether -f or -m flags work. Thank you, clang, for treating unknown -f flags as warnings, only failing with them if run with -Werror, and spewing out warning messages whenever they're used.
2015-09-29 16:15:53 +08:00
if expr "x-Wdeclaration-after-statement" : "x-W.*" >/dev/null
then
CFLAGS="$CFLAGS $ac_lbl_unknown_warning_option_error -Wdeclaration-after-statement"
elif expr "x-Wdeclaration-after-statement" : "x-f.*" >/dev/null
then
CFLAGS="$CFLAGS -Werror -Wdeclaration-after-statement"
elif expr "x-Wdeclaration-after-statement" : "x-m.*" >/dev/null
then
CFLAGS="$CFLAGS -Werror -Wdeclaration-after-statement"
else
CFLAGS="$CFLAGS -Wdeclaration-after-statement"
fi
Compile with '-Wdeclaration-after-statement' in devel mode
2015-08-19 02:49:32 +08:00
cat confdefs.h - <<_ACEOF >conftest.$ac_ext
/* end confdefs.h. */
int
main ()
{
return 0
;
return 0;
}
_ACEOF
if ac_fn_c_try_compile "$LINENO"; then :
{ $as_echo "$as_me:${as_lineno-$LINENO}: result: yes" >&5
$as_echo "yes" >&6; }
CFLAGS="$save_CFLAGS"
V_CCOPT="$V_CCOPT -Wdeclaration-after-statement"
else
{ $as_echo "$as_me:${as_lineno-$LINENO}: result: no" >&5
$as_echo "no" >&6; }
CFLAGS="$save_CFLAGS"
fi
rm -f core conftest.err conftest.$ac_objext conftest.$ac_ext
Compile with '-Wpedantic' in devel mode instead of '-pedantic' Avoid 'Undefined symbol _mcount' with some Solaris compilers. The '-pedantic' option is unknown to the comiler, but by coincidence starts with a '-p' (gather performance data). When a file is compiled with '-p' but is linked without '-p', 'Undefined symbol _mcount' occurs.
2016-11-01 21:28:25 +08:00
{ $as_echo "$as_me:${as_lineno-$LINENO}: checking whether the compiler supports the -Wpedantic option" >&5
$as_echo_n "checking whether the compiler supports the -Wpedantic option... " >&6; }
Compile with '-Wpedantic' in devel mode as an attempt to get gcc-ism
2015-08-19 22:50:22 +08:00
save_CFLAGS="$CFLAGS"
Compile with '-Wpedantic' in devel mode instead of '-pedantic' Avoid 'Undefined symbol _mcount' with some Solaris compilers. The '-pedantic' option is unknown to the comiler, but by coincidence starts with a '-p' (gather performance data). When a file is compiled with '-p' but is linked without '-p', 'Undefined symbol _mcount' occurs.
2016-11-01 21:28:25 +08:00
if expr "x-Wpedantic" : "x-W.*" >/dev/null
We need -Werror when testing whether -f or -m flags work. Thank you, clang, for treating unknown -f flags as warnings, only failing with them if run with -Werror, and spewing out warning messages whenever they're used.
2015-09-29 16:15:53 +08:00
then
Compile with '-Wpedantic' in devel mode instead of '-pedantic' Avoid 'Undefined symbol _mcount' with some Solaris compilers. The '-pedantic' option is unknown to the comiler, but by coincidence starts with a '-p' (gather performance data). When a file is compiled with '-p' but is linked without '-p', 'Undefined symbol _mcount' occurs.
2016-11-01 21:28:25 +08:00
CFLAGS="$CFLAGS $ac_lbl_unknown_warning_option_error -Wpedantic"
elif expr "x-Wpedantic" : "x-f.*" >/dev/null
We need -Werror when testing whether -f or -m flags work. Thank you, clang, for treating unknown -f flags as warnings, only failing with them if run with -Werror, and spewing out warning messages whenever they're used.
2015-09-29 16:15:53 +08:00
then
Compile with '-Wpedantic' in devel mode instead of '-pedantic' Avoid 'Undefined symbol _mcount' with some Solaris compilers. The '-pedantic' option is unknown to the comiler, but by coincidence starts with a '-p' (gather performance data). When a file is compiled with '-p' but is linked without '-p', 'Undefined symbol _mcount' occurs.
2016-11-01 21:28:25 +08:00
CFLAGS="$CFLAGS -Werror -Wpedantic"
elif expr "x-Wpedantic" : "x-m.*" >/dev/null
We need -Werror when testing whether -f or -m flags work. Thank you, clang, for treating unknown -f flags as warnings, only failing with them if run with -Werror, and spewing out warning messages whenever they're used.
2015-09-29 16:15:53 +08:00
then
Compile with '-Wpedantic' in devel mode instead of '-pedantic' Avoid 'Undefined symbol _mcount' with some Solaris compilers. The '-pedantic' option is unknown to the comiler, but by coincidence starts with a '-p' (gather performance data). When a file is compiled with '-p' but is linked without '-p', 'Undefined symbol _mcount' occurs.
2016-11-01 21:28:25 +08:00
CFLAGS="$CFLAGS -Werror -Wpedantic"
We need -Werror when testing whether -f or -m flags work. Thank you, clang, for treating unknown -f flags as warnings, only failing with them if run with -Werror, and spewing out warning messages whenever they're used.
2015-09-29 16:15:53 +08:00
else
Compile with '-Wpedantic' in devel mode instead of '-pedantic' Avoid 'Undefined symbol _mcount' with some Solaris compilers. The '-pedantic' option is unknown to the comiler, but by coincidence starts with a '-p' (gather performance data). When a file is compiled with '-p' but is linked without '-p', 'Undefined symbol _mcount' occurs.
2016-11-01 21:28:25 +08:00
CFLAGS="$CFLAGS -Wpedantic"
We need -Werror when testing whether -f or -m flags work. Thank you, clang, for treating unknown -f flags as warnings, only failing with them if run with -Werror, and spewing out warning messages whenever they're used.
2015-09-29 16:15:53 +08:00
fi
Compile with '-Wpedantic' in devel mode as an attempt to get gcc-ism
2015-08-19 22:50:22 +08:00
cat confdefs.h - <<_ACEOF >conftest.$ac_ext
/* end confdefs.h. */
int
main ()
{
return 0
;
return 0;
}
_ACEOF
if ac_fn_c_try_compile "$LINENO"; then :
{ $as_echo "$as_me:${as_lineno-$LINENO}: result: yes" >&5
$as_echo "yes" >&6; }
CFLAGS="$save_CFLAGS"
Compile with '-Wpedantic' in devel mode instead of '-pedantic' Avoid 'Undefined symbol _mcount' with some Solaris compilers. The '-pedantic' option is unknown to the comiler, but by coincidence starts with a '-p' (gather performance data). When a file is compiled with '-p' but is linked without '-p', 'Undefined symbol _mcount' occurs.
2016-11-01 21:28:25 +08:00
V_CCOPT="$V_CCOPT -Wpedantic"
Compile with '-Wpedantic' in devel mode as an attempt to get gcc-ism
2015-08-19 22:50:22 +08:00
else
{ $as_echo "$as_me:${as_lineno-$LINENO}: result: no" >&5
$as_echo "no" >&6; }
CFLAGS="$save_CFLAGS"
fi
rm -f core conftest.err conftest.$ac_objext conftest.$ac_ext
Compile with '-Wold-style-definition' in devel mode
2015-09-09 13:42:39 +08:00
{ $as_echo "$as_me:${as_lineno-$LINENO}: checking whether the compiler supports the -Wold-style-definition option" >&5
$as_echo_n "checking whether the compiler supports the -Wold-style-definition option... " >&6; }
save_CFLAGS="$CFLAGS"
We need -Werror when testing whether -f or -m flags work. Thank you, clang, for treating unknown -f flags as warnings, only failing with them if run with -Werror, and spewing out warning messages whenever they're used.
2015-09-29 16:15:53 +08:00
if expr "x-Wold-style-definition" : "x-W.*" >/dev/null
then
CFLAGS="$CFLAGS $ac_lbl_unknown_warning_option_error -Wold-style-definition"
elif expr "x-Wold-style-definition" : "x-f.*" >/dev/null
then
CFLAGS="$CFLAGS -Werror -Wold-style-definition"
elif expr "x-Wold-style-definition" : "x-m.*" >/dev/null
then
CFLAGS="$CFLAGS -Werror -Wold-style-definition"
else
CFLAGS="$CFLAGS -Wold-style-definition"
fi
Compile with '-Wold-style-definition' in devel mode
2015-09-09 13:42:39 +08:00
cat confdefs.h - <<_ACEOF >conftest.$ac_ext
/* end confdefs.h. */
int
main ()
{
return 0
;
return 0;
}
_ACEOF
if ac_fn_c_try_compile "$LINENO"; then :
{ $as_echo "$as_me:${as_lineno-$LINENO}: result: yes" >&5
$as_echo "yes" >&6; }
CFLAGS="$save_CFLAGS"
V_CCOPT="$V_CCOPT -Wold-style-definition"
else
{ $as_echo "$as_me:${as_lineno-$LINENO}: result: no" >&5
$as_echo "no" >&6; }
CFLAGS="$save_CFLAGS"
fi
rm -f core conftest.err conftest.$ac_objext conftest.$ac_ext
Compile with '-Wused-but-marked-unused' in devel mode if supported f.e. clang version 3.4 support this warning option.
2016-08-19 07:19:51 +08:00
{ $as_echo "$as_me:${as_lineno-$LINENO}: checking whether the compiler supports the -Wused-but-marked-unused option" >&5
$as_echo_n "checking whether the compiler supports the -Wused-but-marked-unused option... " >&6; }
save_CFLAGS="$CFLAGS"
if expr "x-Wused-but-marked-unused" : "x-W.*" >/dev/null
then
CFLAGS="$CFLAGS $ac_lbl_unknown_warning_option_error -Wused-but-marked-unused"
elif expr "x-Wused-but-marked-unused" : "x-f.*" >/dev/null
then
CFLAGS="$CFLAGS -Werror -Wused-but-marked-unused"
elif expr "x-Wused-but-marked-unused" : "x-m.*" >/dev/null
then
CFLAGS="$CFLAGS -Werror -Wused-but-marked-unused"
else
CFLAGS="$CFLAGS -Wused-but-marked-unused"
fi
cat confdefs.h - <<_ACEOF >conftest.$ac_ext
/* end confdefs.h. */
int
main ()
{
return 0
;
return 0;
}
_ACEOF
if ac_fn_c_try_compile "$LINENO"; then :
{ $as_echo "$as_me:${as_lineno-$LINENO}: result: yes" >&5
$as_echo "yes" >&6; }
CFLAGS="$save_CFLAGS"
V_CCOPT="$V_CCOPT -Wused-but-marked-unused"
else
{ $as_echo "$as_me:${as_lineno-$LINENO}: result: no" >&5
$as_echo "no" >&6; }
CFLAGS="$save_CFLAGS"
fi
rm -f core conftest.err conftest.$ac_objext conftest.$ac_ext
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
{ $as_echo "$as_me:${as_lineno-$LINENO}: checking whether the compiler supports the -W option" >&5
$as_echo_n "checking whether the compiler supports the -W option... " >&6; }
With .devel, use -W flags iff the compiler supports them. Don't base the question of whether to use a particular -W flag on whether we're compiling with GCC or not, and on which version of GCC we're using; some compilers, such as clang, also support many of those -W flags. Base it on whether the compiler complains if we use it (which means, for clang, that we have to force it to exit with a non-zero exit status if it doesn't like a flag; otherwise, we'll specify it, and clang will warn about it on every compile).
2013-05-07 14:54:20 +08:00
save_CFLAGS="$CFLAGS"
We need -Werror when testing whether -f or -m flags work. Thank you, clang, for treating unknown -f flags as warnings, only failing with them if run with -Werror, and spewing out warning messages whenever they're used.
2015-09-29 16:15:53 +08:00
if expr "x-W" : "x-W.*" >/dev/null
then
CFLAGS="$CFLAGS $ac_lbl_unknown_warning_option_error -W"
elif expr "x-W" : "x-f.*" >/dev/null
then
CFLAGS="$CFLAGS -Werror -W"
elif expr "x-W" : "x-m.*" >/dev/null
then
CFLAGS="$CFLAGS -Werror -W"
else
CFLAGS="$CFLAGS -W"
fi
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
cat confdefs.h - <<_ACEOF >conftest.$ac_ext
With .devel, use -W flags iff the compiler supports them. Don't base the question of whether to use a particular -W flag on whether we're compiling with GCC or not, and on which version of GCC we're using; some compilers, such as clang, also support many of those -W flags. Base it on whether the compiler complains if we use it (which means, for clang, that we have to force it to exit with a non-zero exit status if it doesn't like a flag; otherwise, we'll specify it, and clang will warn about it on every compile).
2013-05-07 14:54:20 +08:00
/* end confdefs.h. */
int
main ()
{
return 0
;
return 0;
}
_ACEOF
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
if ac_fn_c_try_compile "$LINENO"; then :
With .devel, use -W flags iff the compiler supports them. Don't base the question of whether to use a particular -W flag on whether we're compiling with GCC or not, and on which version of GCC we're using; some compilers, such as clang, also support many of those -W flags. Base it on whether the compiler complains if we use it (which means, for clang, that we have to force it to exit with a non-zero exit status if it doesn't like a flag; otherwise, we'll specify it, and clang will warn about it on every compile).
2013-05-07 14:54:20 +08:00
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
{ $as_echo "$as_me:${as_lineno-$LINENO}: result: yes" >&5
$as_echo "yes" >&6; }
With .devel, use -W flags iff the compiler supports them. Don't base the question of whether to use a particular -W flag on whether we're compiling with GCC or not, and on which version of GCC we're using; some compilers, such as clang, also support many of those -W flags. Base it on whether the compiler complains if we use it (which means, for clang, that we have to force it to exit with a non-zero exit status if it doesn't like a flag; otherwise, we'll specify it, and clang will warn about it on every compile).
2013-05-07 14:54:20 +08:00
CFLAGS="$save_CFLAGS"
V_CCOPT="$V_CCOPT -W"
else
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
{ $as_echo "$as_me:${as_lineno-$LINENO}: result: no" >&5
$as_echo "no" >&6; }
With .devel, use -W flags iff the compiler supports them. Don't base the question of whether to use a particular -W flag on whether we're compiling with GCC or not, and on which version of GCC we're using; some compilers, such as clang, also support many of those -W flags. Base it on whether the compiler complains if we use it (which means, for clang, that we have to force it to exit with a non-zero exit status if it doesn't like a flag; otherwise, we'll specify it, and clang will warn about it on every compile).
2013-05-07 14:54:20 +08:00
CFLAGS="$save_CFLAGS"
Compile with '-Wassign-enum' in devel mode if supported
2016-08-23 22:04:57 +08:00
fi
rm -f core conftest.err conftest.$ac_objext conftest.$ac_ext
{ $as_echo "$as_me:${as_lineno-$LINENO}: checking whether the compiler supports the -Wassign-enum option" >&5
$as_echo_n "checking whether the compiler supports the -Wassign-enum option... " >&6; }
save_CFLAGS="$CFLAGS"
if expr "x-Wassign-enum" : "x-W.*" >/dev/null
then
CFLAGS="$CFLAGS $ac_lbl_unknown_warning_option_error -Wassign-enum"
elif expr "x-Wassign-enum" : "x-f.*" >/dev/null
then
CFLAGS="$CFLAGS -Werror -Wassign-enum"
elif expr "x-Wassign-enum" : "x-m.*" >/dev/null
then
CFLAGS="$CFLAGS -Werror -Wassign-enum"
else
CFLAGS="$CFLAGS -Wassign-enum"
fi
cat confdefs.h - <<_ACEOF >conftest.$ac_ext
/* end confdefs.h. */
int
main ()
{
return 0
;
return 0;
}
_ACEOF
if ac_fn_c_try_compile "$LINENO"; then :
{ $as_echo "$as_me:${as_lineno-$LINENO}: result: yes" >&5
$as_echo "yes" >&6; }
CFLAGS="$save_CFLAGS"
V_CCOPT="$V_CCOPT -Wassign-enum"
else
{ $as_echo "$as_me:${as_lineno-$LINENO}: result: no" >&5
$as_echo "no" >&6; }
CFLAGS="$save_CFLAGS"
With .devel, use -W flags iff the compiler supports them. Don't base the question of whether to use a particular -W flag on whether we're compiling with GCC or not, and on which version of GCC we're using; some compilers, such as clang, also support many of those -W flags. Base it on whether the compiler complains if we use it (which means, for clang, that we have to force it to exit with a non-zero exit status if it doesn't like a flag; otherwise, we'll specify it, and clang will warn about it on every compile).
2013-05-07 14:54:20 +08:00
fi
rm -f core conftest.err conftest.$ac_objext conftest.$ac_ext
Don't try -W flags with HP's C compiler. HP's C compiler cannot be made to exit with a non-zero exit status when given an unknown compiler flag, so you can't use that to figure out if a flag is supported, but it *will* print a warning, which we don't want. In addition, it doesn't support -W flags for warnings in any case, so let's not bother with them.
2013-05-08 14:58:51 +08:00
fi
Support dependency generation with some non-GCC compilers. Also, if we don't support it with a given compiler, have "make depend" not run mkdep, as it won't do anything useful.
2013-05-08 15:08:12 +08:00
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
{ $as_echo "$as_me:${as_lineno-$LINENO}: checking whether the compiler supports generating dependencies" >&5
$as_echo_n "checking whether the compiler supports generating dependencies... " >&6; }
Support dependency generation with some non-GCC compilers. Also, if we don't support it with a given compiler, have "make depend" not run mkdep, as it won't do anything useful.
2013-05-08 15:08:12 +08:00
if test "$GCC" = yes ; then
#
# GCC, or a compiler deemed to be GCC by AC_PROG_CC (even
# though it's not); we assume that, in this case, the flag
# would be -M.
#
ac_lbl_dependency_flag="-M"
else
#
# Not GCC or a compiler deemed to be GCC; what platform is
# this? (We're assuming that if the compiler isn't GCC
# it's the compiler from the vendor of the OS; that won't
# necessarily be true for x86 platforms, where it might be
# the Intel C compiler.)
#
case "$host_os" in
irix*|osf*|darwin*)
#
# MIPS C for IRIX, DEC C, and clang all use -M.
#
ac_lbl_dependency_flag="-M"
;;
solaris*)
#
# Sun C uses -xM.
#
ac_lbl_dependency_flag="-xM"
;;
hpux*)
#
# HP's older C compilers don't support this.
# HP's newer C compilers support this with
# either +M or +Make; the older compilers
# interpret +M as something completely
# different, so we use +Make so we don't
# think it works with the older compilers.
#
ac_lbl_dependency_flag="+Make"
;;
*)
#
# Not one of the above; assume no support for
# generating dependencies.
#
ac_lbl_dependency_flag=""
;;
esac
fi
#
# Is ac_lbl_dependency_flag defined and, if so, does the compiler
# complain about it?
#
# Note: clang doesn't seem to exit with an error status when handed
# an unknown non-warning error, even if you pass it
# -Werror=unknown-warning-option. However, it always supports
# -M, so the fact that this test always succeeds with clang
# isn't an issue.
#
if test ! -z "$ac_lbl_dependency_flag"; then
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
cat confdefs.h - <<_ACEOF >conftest.$ac_ext
Support dependency generation with some non-GCC compilers. Also, if we don't support it with a given compiler, have "make depend" not run mkdep, as it won't do anything useful.
2013-05-08 15:08:12 +08:00
/* end confdefs.h. */
int main(void) { return 0; }
_ACEOF
echo "$CC" $ac_lbl_dependency_flag conftest.c >&5
if "$CC" $ac_lbl_dependency_flag conftest.c >/dev/null 2>&1; then
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
{ $as_echo "$as_me:${as_lineno-$LINENO}: result: yes, with $ac_lbl_dependency_flag" >&5
$as_echo "yes, with $ac_lbl_dependency_flag" >&6; }
Support dependency generation with some non-GCC compilers. Also, if we don't support it with a given compiler, have "make depend" not run mkdep, as it won't do anything useful.
2013-05-08 15:08:12 +08:00
DEPENDENCY_CFLAG="$ac_lbl_dependency_flag"
MKDEP='${srcdir}/mkdep'
else
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
{ $as_echo "$as_me:${as_lineno-$LINENO}: result: no" >&5
$as_echo "no" >&6; }
Support dependency generation with some non-GCC compilers. Also, if we don't support it with a given compiler, have "make depend" not run mkdep, as it won't do anything useful.
2013-05-08 15:08:12 +08:00
#
# We can't run mkdep, so have "make depend" do
# nothing.
#
MKDEP=:
fi
rm -rf conftest*
else
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
{ $as_echo "$as_me:${as_lineno-$LINENO}: result: no" >&5
$as_echo "no" >&6; }
Support dependency generation with some non-GCC compilers. Also, if we don't support it with a given compiler, have "make depend" not run mkdep, as it won't do anything useful.
2013-05-08 15:08:12 +08:00
#
# We can't run mkdep, so have "make depend" do
# nothing.
#
MKDEP=:
fi
AC_SUBST doesn't take a list of macros to substitute.
2013-05-13 07:37:47 +08:00
Add -g3 on some platforms even if .devel isn't present. Now that we're requiring autoconf 2.61 or later, AC_PROG_CC sets -g along with -O2 for GCC-like compilers regardless of whether .devel is present. Add "include debugging symbols" options for MIPS C/DEC C regardless of whether .devel is present; that's -g3, which is the version that doesn't turn optimization off (we also turn on -O). Also, don't change the ABI on IRIX depending on .devel. I'm not sure why we were doing that; if somebody has a good reason to continue doing it, please let us know what it is. Expand some comments while we're at it.
2013-10-22 01:56:33 +08:00
#
# We used to set -n32 for IRIX 6 when not using GCC (presumed
# to mean that we're using MIPS C or MIPSpro C); it specified
# the "new" faster 32-bit ABI, introduced in IRIX 6.2. I'm
# not sure why that would be something to do *only* with a
# .devel file; why should the ABI for which we produce code
# depend on .devel?
#
Replace "target_cpu", "target_os", and AC_CANONICAL_SYSTEM with "host_cpu", "host_os", and AC_CANONICAL_HOST, as per Maciej W. Rozycki's patch.
2001-12-10 16:41:15 +08:00
os=`echo $host_os | sed -e 's/\([0-9][0-9]*\)[^0-9].*$/\1/'`
Initial revision
1999-10-08 07:47:09 +08:00
name="lbl/os-$os.h"
if test -f $name ; then
ln -s $name os-proto.h
Pick up some AC_DEFINE comments from libpcap's aclocal.m4. Remove unused items, and items for which we now have AC_DEFINE() calls that supply a comment, from acconfig.h. Note that a host OS that matches "osf*" is assumed to be DEC OSF1/Digital UNIX/Tru64 UNIX.
2009-07-03 09:59:24 +08:00
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
$as_echo "#define HAVE_OS_PROTO_H 1" >>confdefs.h
Initial revision
1999-10-08 07:47:09 +08:00
else
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
{ $as_echo "$as_me:${as_lineno-$LINENO}: WARNING: can't find $name" >&5
$as_echo "$as_me: WARNING: can't find $name" >&2;}
Initial revision
1999-10-08 07:47:09 +08:00
fi
fi
Allow building with libcrypto not in the default directory. Add support for an argument to --with-crypto, so that if you have one version of libcrypto installed under /usr and another version installed under /usr/local, you can force tcpdump to be built with the /usr/local version. Also, refer both to OpenSSL and libressl in comments and messages.
2016-07-14 08:23:59 +08:00
# Check for OpenSSL/libressl libcrypto
{ $as_echo "$as_me:${as_lineno-$LINENO}: checking whether to use OpenSSL/libressl libcrypto" >&5
$as_echo_n "checking whether to use OpenSSL/libressl libcrypto... " >&6; }
Have --with-crypto take an optional argument, specifying where libcrypto can be found. If --with-crypto is specified, and libcrypto isn't found, fail, as presumably the user expected libcrypto to be available.
2008-02-27 04:47:12 +08:00
# Specify location for both includes and libraries.
Simplify the detection of OpenSSL libcrypto by using standard autoconf macros rather than a local copy of AC_LBL_SSLEAY. AC_LBL_SSLEAY is old and has not kept pace with some more recent developments in packaging like Debian and Ubuntu's multiarch support. The autoconf macros have been updated to handle multiarch so using them means that tcpdump gains the ability to be built with libcrypto on these new multiarch distros and to work successfully with Travis CI, which uses Ubuntu 12, which is one such multiarch distro (see GH-32). Fixes GH-33
2012-10-14 02:21:45 +08:00
want_libcrypto=ifavailable
From Andrew Church <andrew@users.sourceforge.net>: when testing for "pcap_version", "pcap_debug", and "yydebug", don't add our own functions referring to those variables - GCC 3.4.1 optimizes the test code out before the link is done, as it's in a function that's not called.
2004-08-27 15:17:03 +08:00
We support building tcpdump with versions of libpcap other than the one with which it was released, and DLT_BLUETOOTH_HCI_H4_WITH_PHDR might be defined by pcap-bpf.h without pcap/bluetooth.h being present (as appears to be the case on Fedora 9, for example), so check whether <pcap/bluetooth.h> is usable. Update a comment - F9 appears to have a "/usr/include/pcap.h" if you install the libpcap headers. When adding -I flags when running a compiler-based test, add them to CPPFLAGS, not CFLAGS - the latter doesn't work right with AC_CHECK_HEADERS, as the "gcc -E" run doesn't have the -I flags added.
2008-09-26 05:45:50 +08:00
# Check whether --with-crypto was given.
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
if test "${with_crypto+set}" = set; then :
We support building tcpdump with versions of libpcap other than the one with which it was released, and DLT_BLUETOOTH_HCI_H4_WITH_PHDR might be defined by pcap-bpf.h without pcap/bluetooth.h being present (as appears to be the case on Fedora 9, for example), so check whether <pcap/bluetooth.h> is usable. Update a comment - F9 appears to have a "/usr/include/pcap.h" if you install the libpcap headers. When adding -I flags when running a compiler-based test, add them to CPPFLAGS, not CFLAGS - the latter doesn't work right with AC_CHECK_HEADERS, as the "gcc -E" run doesn't have the -I flags added.
2008-09-26 05:45:50 +08:00
withval=$with_crypto;
Have --with-crypto take an optional argument, specifying where libcrypto can be found. If --with-crypto is specified, and libcrypto isn't found, fail, as presumably the user expected libcrypto to be available.
2008-02-27 04:47:12 +08:00
if test $withval = no
then
Allow building with libcrypto not in the default directory. Add support for an argument to --with-crypto, so that if you have one version of libcrypto installed under /usr and another version installed under /usr/local, you can force tcpdump to be built with the /usr/local version. Also, refer both to OpenSSL and libressl in comments and messages.
2016-07-14 08:23:59 +08:00
# User doesn't want to link with libcrypto.
Have --with-crypto take an optional argument, specifying where libcrypto can be found. If --with-crypto is specified, and libcrypto isn't found, fail, as presumably the user expected libcrypto to be available.
2008-02-27 04:47:12 +08:00
want_libcrypto=no
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
{ $as_echo "$as_me:${as_lineno-$LINENO}: result: no" >&5
$as_echo "no" >&6; }
Have --with-crypto take an optional argument, specifying where libcrypto can be found. If --with-crypto is specified, and libcrypto isn't found, fail, as presumably the user expected libcrypto to be available.
2008-02-27 04:47:12 +08:00
elif test $withval = yes
then
Allow building with libcrypto not in the default directory. Add support for an argument to --with-crypto, so that if you have one version of libcrypto installed under /usr and another version installed under /usr/local, you can force tcpdump to be built with the /usr/local version. Also, refer both to OpenSSL and libressl in comments and messages.
2016-07-14 08:23:59 +08:00
# User wants to link with libcrypto but hasn't specified
# a directory.
Have --with-crypto take an optional argument, specifying where libcrypto can be found. If --with-crypto is specified, and libcrypto isn't found, fail, as presumably the user expected libcrypto to be available.
2008-02-27 04:47:12 +08:00
want_libcrypto=yes
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
{ $as_echo "$as_me:${as_lineno-$LINENO}: result: yes" >&5
$as_echo "yes" >&6; }
Allow building with libcrypto not in the default directory. Add support for an argument to --with-crypto, so that if you have one version of libcrypto installed under /usr and another version installed under /usr/local, you can force tcpdump to be built with the /usr/local version. Also, refer both to OpenSSL and libressl in comments and messages.
2016-07-14 08:23:59 +08:00
else
# User wants to link with libcrypto and has specified
# a directory, so use the provided value.
want_libcrypto=yes
libcrypto_root=$withval
{ $as_echo "$as_me:${as_lineno-$LINENO}: result: yes, using the version installed in $withval" >&5
$as_echo "yes, using the version installed in $withval" >&6; }
#
# Put the subdirectories of the libcrypto root directory
# at the front of the header and library search path.
#
CFLAGS="-I$withval/include $CFLAGS"
LIBS="-L$withval/lib $LIBS"
Have --with-crypto take an optional argument, specifying where libcrypto can be found. If --with-crypto is specified, and libcrypto isn't found, fail, as presumably the user expected libcrypto to be available.
2008-02-27 04:47:12 +08:00
fi
add --without-crpyto to arg to configure, to skip partially incompatible/ old crypto libraries.
2000-04-27 17:16:08 +08:00
else
Regenerate with autoconf 2.57.
2004-01-14 11:15:08 +08:00
Have --with-crypto take an optional argument, specifying where libcrypto can be found. If --with-crypto is specified, and libcrypto isn't found, fail, as presumably the user expected libcrypto to be available.
2008-02-27 04:47:12 +08:00
#
Allow building with libcrypto not in the default directory. Add support for an argument to --with-crypto, so that if you have one version of libcrypto installed under /usr and another version installed under /usr/local, you can force tcpdump to be built with the /usr/local version. Also, refer both to OpenSSL and libressl in comments and messages.
2016-07-14 08:23:59 +08:00
# Use libcrypto if it's present, otherwise don't; no directory
# was specified.
Have --with-crypto take an optional argument, specifying where libcrypto can be found. If --with-crypto is specified, and libcrypto isn't found, fail, as presumably the user expected libcrypto to be available.
2008-02-27 04:47:12 +08:00
#
want_libcrypto=ifavailable
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
{ $as_echo "$as_me:${as_lineno-$LINENO}: result: yes, if available" >&5
$as_echo "yes, if available" >&6; }
We support building tcpdump with versions of libpcap other than the one with which it was released, and DLT_BLUETOOTH_HCI_H4_WITH_PHDR might be defined by pcap-bpf.h without pcap/bluetooth.h being present (as appears to be the case on Fedora 9, for example), so check whether <pcap/bluetooth.h> is usable. Update a comment - F9 appears to have a "/usr/include/pcap.h" if you install the libpcap headers. When adding -I flags when running a compiler-based test, add them to CPPFLAGS, not CFLAGS - the latter doesn't work right with AC_CHECK_HEADERS, as the "gcc -E" run doesn't have the -I flags added.
2008-09-26 05:45:50 +08:00
fi
regenerated configure with 2.57.
2004-04-05 08:17:03 +08:00
Have --with-crypto take an optional argument, specifying where libcrypto can be found. If --with-crypto is specified, and libcrypto isn't found, fail, as presumably the user expected libcrypto to be available.
2008-02-27 04:47:12 +08:00
if test "$want_libcrypto" != "no"; then
Don't check for libcrypto if we don't have its headers. Thanks, Apple.
2015-09-28 15:41:01 +08:00
#
# Don't check for libcrypto unless we have its headers;
# Apple, bless their pointy little heads, apparently ship
# libcrypto as a library, but not the header files, in
# El Capitan, probably because they don't want you writing
# nasty portable code that could run on other UN*Xes, they
# want you writing code that uses their Shiny New Crypto
# Library and that only runs on OS X.
#
ac_fn_c_check_header_mongrel "$LINENO" "openssl/crypto.h" "ac_cv_header_openssl_crypto_h" "$ac_includes_default"
if test "x$ac_cv_header_openssl_crypto_h" = xyes; then :
{ $as_echo "$as_me:${as_lineno-$LINENO}: checking for DES_cbc_encrypt in -lcrypto" >&5
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
$as_echo_n "checking for DES_cbc_encrypt in -lcrypto... " >&6; }
if ${ac_cv_lib_crypto_DES_cbc_encrypt+:} false; then :
$as_echo_n "(cached) " >&6
Bring in KAME IPv6 tcpdump. replaces esp/ah/isakmp decoder. Hope I did not break anything. Portability on IPv4-only node needs checking, I'll do this very soon. (sorry for rather jumbo commit) XXx what is _FAVOR_BSD?
1999-10-30 13:11:06 +08:00
else
Regenerate with autoconf 2.57.
2004-01-14 11:15:08 +08:00
ac_check_lib_save_LIBS=$LIBS
Bring in KAME IPv6 tcpdump. replaces esp/ah/isakmp decoder. Hope I did not break anything. Portability on IPv4-only node needs checking, I'll do this very soon. (sorry for rather jumbo commit) XXx what is _FAVOR_BSD?
1999-10-30 13:11:06 +08:00
LIBS="-lcrypto $LIBS"
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
cat confdefs.h - <<_ACEOF >conftest.$ac_ext
From Andrew Church <andrew@users.sourceforge.net>: when testing for "pcap_version", "pcap_debug", and "yydebug", don't add our own functions referring to those variables - GCC 3.4.1 optimizes the test code out before the link is done, as it's in a function that's not called.
2004-08-27 15:17:03 +08:00
/* end confdefs.h. */
Regenerate with autoconf 2.57.
2004-01-14 11:15:08 +08:00
We support building tcpdump with versions of libpcap other than the one with which it was released, and DLT_BLUETOOTH_HCI_H4_WITH_PHDR might be defined by pcap-bpf.h without pcap/bluetooth.h being present (as appears to be the case on Fedora 9, for example), so check whether <pcap/bluetooth.h> is usable. Update a comment - F9 appears to have a "/usr/include/pcap.h" if you install the libpcap headers. When adding -I flags when running a compiler-based test, add them to CPPFLAGS, not CFLAGS - the latter doesn't work right with AC_CHECK_HEADERS, as the "gcc -E" run doesn't have the -I flags added.
2008-09-26 05:45:50 +08:00
/* Override any GCC internal prototype to avoid an error.
Use char because int might match the return type of a GCC
builtin and then its argument prototype would still apply. */
Regenerate with autoconf 2.57.
2004-01-14 11:15:08 +08:00
#ifdef __cplusplus
extern "C"
#endif
regenerated configure with 2.57.
2004-04-05 08:17:03 +08:00
char DES_cbc_encrypt ();
Regenerate with autoconf 2.57.
2004-01-14 11:15:08 +08:00
int
main ()
{
We support building tcpdump with versions of libpcap other than the one with which it was released, and DLT_BLUETOOTH_HCI_H4_WITH_PHDR might be defined by pcap-bpf.h without pcap/bluetooth.h being present (as appears to be the case on Fedora 9, for example), so check whether <pcap/bluetooth.h> is usable. Update a comment - F9 appears to have a "/usr/include/pcap.h" if you install the libpcap headers. When adding -I flags when running a compiler-based test, add them to CPPFLAGS, not CFLAGS - the latter doesn't work right with AC_CHECK_HEADERS, as the "gcc -E" run doesn't have the -I flags added.
2008-09-26 05:45:50 +08:00
return DES_cbc_encrypt ();
Regenerate with autoconf 2.57.
2004-01-14 11:15:08 +08:00
;
return 0;
}
_ACEOF
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
if ac_fn_c_try_link "$LINENO"; then :
regenerated configure with 2.57.
2004-04-05 08:17:03 +08:00
ac_cv_lib_crypto_DES_cbc_encrypt=yes
Regenerate with autoconf 2.57.
2004-01-14 11:15:08 +08:00
else
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
ac_cv_lib_crypto_DES_cbc_encrypt=no
Regenerate with autoconf 2.57.
2004-01-14 11:15:08 +08:00
fi
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
rm -f core conftest.err conftest.$ac_objext \
conftest$ac_exeext conftest.$ac_ext
Regenerate with autoconf 2.57.
2004-01-14 11:15:08 +08:00
LIBS=$ac_check_lib_save_LIBS
fi
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
{ $as_echo "$as_me:${as_lineno-$LINENO}: result: $ac_cv_lib_crypto_DES_cbc_encrypt" >&5
$as_echo "$ac_cv_lib_crypto_DES_cbc_encrypt" >&6; }
if test "x$ac_cv_lib_crypto_DES_cbc_encrypt" = xyes; then :
From Andrew Church <andrew@users.sourceforge.net>: when testing for "pcap_version", "pcap_debug", and "yydebug", don't add our own functions referring to those variables - GCC 3.4.1 optimizes the test code out before the link is done, as it's in a function that's not called.
2004-08-27 15:17:03 +08:00
cat >>confdefs.h <<_ACEOF
Regenerate with autoconf 2.57.
2004-01-14 11:15:08 +08:00
#define HAVE_LIBCRYPTO 1
From Andrew Church <andrew@users.sourceforge.net>: when testing for "pcap_version", "pcap_debug", and "yydebug", don't add our own functions referring to those variables - GCC 3.4.1 optimizes the test code out before the link is done, as it's in a function that's not called.
2004-08-27 15:17:03 +08:00
_ACEOF
Bring in KAME IPv6 tcpdump. replaces esp/ah/isakmp decoder. Hope I did not break anything. Portability on IPv4-only node needs checking, I'll do this very soon. (sorry for rather jumbo commit) XXx what is _FAVOR_BSD?
1999-10-30 13:11:06 +08:00
LIBS="-lcrypto $LIBS"
fi
Handle OpenSSL 1.1.x. In 1.1.x, EVP_CIPHER_CTX is an opaque structure, so we can't declare it on the stack. Instead, if we don't have EVP_CIPHER_CTX_new() and EVP_CIPHER_CTX_free() in libcrypto, define our own versions, with the same signatures as the ones in OpenSSL 1.1.x's libcrypto, and have the code use EVP_CIPHER_CTX_new() to allocate the structure and EVP_CIPHER_CTX_free() to free it.
2016-06-23 12:14:40 +08:00
if test "$ac_cv_lib_crypto_DES_cbc_encrypt" = "yes"; then
for ac_header in openssl/evp.h
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
do :
ac_fn_c_check_header_mongrel "$LINENO" "openssl/evp.h" "ac_cv_header_openssl_evp_h" "$ac_includes_default"
if test "x$ac_cv_header_openssl_evp_h" = xyes; then :
From Andrew Church <andrew@users.sourceforge.net>: when testing for "pcap_version", "pcap_debug", and "yydebug", don't add our own functions referring to those variables - GCC 3.4.1 optimizes the test code out before the link is done, as it's in a function that's not called.
2004-08-27 15:17:03 +08:00
cat >>confdefs.h <<_ACEOF
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
#define HAVE_OPENSSL_EVP_H 1
From Andrew Church <andrew@users.sourceforge.net>: when testing for "pcap_version", "pcap_debug", and "yydebug", don't add our own functions referring to those variables - GCC 3.4.1 optimizes the test code out before the link is done, as it's in a function that's not called.
2004-08-27 15:17:03 +08:00
_ACEOF
Bring in KAME IPv6 tcpdump. replaces esp/ah/isakmp decoder. Hope I did not break anything. Portability on IPv4-only node needs checking, I'll do this very soon. (sorry for rather jumbo commit) XXx what is _FAVOR_BSD?
1999-10-30 13:11:06 +08:00
fi
From Andrew Church <andrew@users.sourceforge.net>: when testing for "pcap_version", "pcap_debug", and "yydebug", don't add our own functions referring to those variables - GCC 3.4.1 optimizes the test code out before the link is done, as it's in a function that's not called.
2004-08-27 15:17:03 +08:00
Regenerate with autoconf 2.57.
2004-01-14 11:15:08 +08:00
done
Handle OpenSSL 1.1.x. In 1.1.x, EVP_CIPHER_CTX is an opaque structure, so we can't declare it on the stack. Instead, if we don't have EVP_CIPHER_CTX_new() and EVP_CIPHER_CTX_free() in libcrypto, define our own versions, with the same signatures as the ones in OpenSSL 1.1.x's libcrypto, and have the code use EVP_CIPHER_CTX_new() to allocate the structure and EVP_CIPHER_CTX_free() to free it.
2016-06-23 12:14:40 +08:00
#
Make the ESP decryption not crash with OpenSSL 1.1. While we're at it, free the cipher context if we fail to allocate the output buffer for decryption.
2017-09-01 19:00:38 +08:00
# OK, then:
#
# 1) do we have EVP_CIPHER_CTX_new?
Handle OpenSSL 1.1.x. In 1.1.x, EVP_CIPHER_CTX is an opaque structure, so we can't declare it on the stack. Instead, if we don't have EVP_CIPHER_CTX_new() and EVP_CIPHER_CTX_free() in libcrypto, define our own versions, with the same signatures as the ones in OpenSSL 1.1.x's libcrypto, and have the code use EVP_CIPHER_CTX_new() to allocate the structure and EVP_CIPHER_CTX_free() to free it.
2016-06-23 12:14:40 +08:00
# If so, we use it to allocate an
# EVP_CIPHER_CTX, as EVP_CIPHER_CTX may be
# opaque; otherwise, we allocate it ourselves.
#
Make the ESP decryption not crash with OpenSSL 1.1. While we're at it, free the cipher context if we fail to allocate the output buffer for decryption.
2017-09-01 19:00:38 +08:00
# 2) do we have EVP_CipherInit_ex()?
# If so, we use it, because we need to be
# able to make two "initialize the cipher"
# calls, one with the cipher and key, and
# one with the IV, and, as of OpenSSL 1.1,
# You Can't Do That with EVP_CipherInit(),
# because a call to EVP_CipherInit() will
# unconditionally clear the context, and
# if you don't supply a cipher, it'll
# clear the cipher, rendering the context
# unusable and causing a crash.
#
for ac_func in EVP_CIPHER_CTX_new EVP_CipherInit_ex
Handle OpenSSL 1.1.x. In 1.1.x, EVP_CIPHER_CTX is an opaque structure, so we can't declare it on the stack. Instead, if we don't have EVP_CIPHER_CTX_new() and EVP_CIPHER_CTX_free() in libcrypto, define our own versions, with the same signatures as the ones in OpenSSL 1.1.x's libcrypto, and have the code use EVP_CIPHER_CTX_new() to allocate the structure and EVP_CIPHER_CTX_free() to free it.
2016-06-23 12:14:40 +08:00
do :
Make the ESP decryption not crash with OpenSSL 1.1. While we're at it, free the cipher context if we fail to allocate the output buffer for decryption.
2017-09-01 19:00:38 +08:00
as_ac_var=`$as_echo "ac_cv_func_$ac_func" | $as_tr_sh`
ac_fn_c_check_func "$LINENO" "$ac_func" "$as_ac_var"
if eval test \"x\$"$as_ac_var"\" = x"yes"; then :
Handle OpenSSL 1.1.x. In 1.1.x, EVP_CIPHER_CTX is an opaque structure, so we can't declare it on the stack. Instead, if we don't have EVP_CIPHER_CTX_new() and EVP_CIPHER_CTX_free() in libcrypto, define our own versions, with the same signatures as the ones in OpenSSL 1.1.x's libcrypto, and have the code use EVP_CIPHER_CTX_new() to allocate the structure and EVP_CIPHER_CTX_free() to free it.
2016-06-23 12:14:40 +08:00
cat >>confdefs.h <<_ACEOF
Make the ESP decryption not crash with OpenSSL 1.1. While we're at it, free the cipher context if we fail to allocate the output buffer for decryption.
2017-09-01 19:00:38 +08:00
#define `$as_echo "HAVE_$ac_func" | $as_tr_cpp` 1
Handle OpenSSL 1.1.x. In 1.1.x, EVP_CIPHER_CTX is an opaque structure, so we can't declare it on the stack. Instead, if we don't have EVP_CIPHER_CTX_new() and EVP_CIPHER_CTX_free() in libcrypto, define our own versions, with the same signatures as the ones in OpenSSL 1.1.x's libcrypto, and have the code use EVP_CIPHER_CTX_new() to allocate the structure and EVP_CIPHER_CTX_free() to free it.
2016-06-23 12:14:40 +08:00
_ACEOF
fi
done
fi
Don't check for libcrypto if we don't have its headers. Thanks, Apple.
2015-09-28 15:41:01 +08:00
fi
add --without-crpyto to arg to configure, to skip partially incompatible/ old crypto libraries.
2000-04-27 17:16:08 +08:00
fi
configure: add support for cap-ng package It uses '--with-cap-ng', for using libcap-ng [default=yes, if available]
2015-02-15 22:32:23 +08:00
# Check for libcap-ng
{ $as_echo "$as_me:${as_lineno-$LINENO}: checking whether to use libcap-ng" >&5
$as_echo_n "checking whether to use libcap-ng... " >&6; }
# Specify location for both includes and libraries.
want_libcap_ng=ifavailable
# Check whether --with-cap_ng was given.
if test "${with_cap_ng+set}" = set; then :
withval=$with_cap_ng;
if test $withval = no
then
want_libcap_ng=no
{ $as_echo "$as_me:${as_lineno-$LINENO}: result: no" >&5
$as_echo "no" >&6; }
elif test $withval = yes
then
want_libcap_ng=yes
{ $as_echo "$as_me:${as_lineno-$LINENO}: result: yes" >&5
$as_echo "yes" >&6; }
fi
else
#
# Use libcap-ng if it's present, otherwise don't.
#
want_libcap_ng=ifavailable
{ $as_echo "$as_me:${as_lineno-$LINENO}: result: yes, if available" >&5
$as_echo "yes, if available" >&6; }
fi
if test "$want_libcap_ng" != "no"; then
{ $as_echo "$as_me:${as_lineno-$LINENO}: checking for capng_change_id in -lcap-ng" >&5
$as_echo_n "checking for capng_change_id in -lcap-ng... " >&6; }
if ${ac_cv_lib_cap_ng_capng_change_id+:} false; then :
$as_echo_n "(cached) " >&6
else
ac_check_lib_save_LIBS=$LIBS
LIBS="-lcap-ng $LIBS"
cat confdefs.h - <<_ACEOF >conftest.$ac_ext
/* end confdefs.h. */
/* Override any GCC internal prototype to avoid an error.
Use char because int might match the return type of a GCC
builtin and then its argument prototype would still apply. */
#ifdef __cplusplus
extern "C"
#endif
char capng_change_id ();
int
main ()
{
return capng_change_id ();
;
return 0;
}
_ACEOF
if ac_fn_c_try_link "$LINENO"; then :
ac_cv_lib_cap_ng_capng_change_id=yes
else
ac_cv_lib_cap_ng_capng_change_id=no
fi
rm -f core conftest.err conftest.$ac_objext \
conftest$ac_exeext conftest.$ac_ext
LIBS=$ac_check_lib_save_LIBS
fi
{ $as_echo "$as_me:${as_lineno-$LINENO}: result: $ac_cv_lib_cap_ng_capng_change_id" >&5
$as_echo "$ac_cv_lib_cap_ng_capng_change_id" >&6; }
if test "x$ac_cv_lib_cap_ng_capng_change_id" = xyes; then :
cat >>confdefs.h <<_ACEOF
#define HAVE_LIBCAP_NG 1
_ACEOF
LIBS="-lcap-ng $LIBS"
fi
for ac_header in cap-ng.h
do :
ac_fn_c_check_header_mongrel "$LINENO" "cap-ng.h" "ac_cv_header_cap_ng_h" "$ac_includes_default"
if test "x$ac_cv_header_cap_ng_h" = xyes; then :
cat >>confdefs.h <<_ACEOF
#define HAVE_CAP_NG_H 1
_ACEOF
fi
done
fi
From Albert Chin <china@thewrittenword.com>: propagate CPPFLAGS to Makefile.in; move the CPPFLAGS and V_INCLS change to the end of the configure run so users don't see "-I$(srcdir)/missing" in their config.log output.
2003-12-15 10:12:40 +08:00
if test "$missing_includes" = "yes"; then
Expand srcdir in V_INCLS at configure time, not make time. That way, if we temporarily set CPPFLAGS to include V_INCLS, it'll work correctly.
2011-04-05 02:49:41 +08:00
CPPFLAGS="$CPPFLAGS -I$srcdir/missing"
V_INCLS="$V_INCLS -I$srcdir/missing"
From Albert Chin <china@thewrittenword.com>: propagate CPPFLAGS to Makefile.in; move the CPPFLAGS and V_INCLS change to the end of the configure run so users don't see "-I$(srcdir)/missing" in their config.log output.
2003-12-15 10:12:40 +08:00
fi
From Andrew Church <andrew@users.sourceforge.net>: when testing for "pcap_version", "pcap_debug", and "yydebug", don't add our own functions referring to those variables - GCC 3.4.1 optimizes the test code out before the link is done, as it's in a function that's not called.
2004-08-27 15:17:03 +08:00
Run the tcpdump man page through config, so that it refers to the right man page sections. Have it refer to the new pcap-savefile man page for a description of the savefile format.
2008-10-28 05:20:16 +08:00
Initial revision
1999-10-08 07:47:09 +08:00
# Find a good install program. We prefer a C program (faster),
# so one script is as good as another. But avoid the broken or
# incompatible versions:
# SysV /etc/install, /usr/sbin/install
# SunOS /usr/etc/install
# IRIX /sbin/install
# AIX /bin/install
Regenerate with autoconf 2.57.
2004-01-14 11:15:08 +08:00
# AmigaOS /C/install, which installs bootblocks on floppy discs
Bring in KAME IPv6 tcpdump. replaces esp/ah/isakmp decoder. Hope I did not break anything. Portability on IPv4-only node needs checking, I'll do this very soon. (sorry for rather jumbo commit) XXx what is _FAVOR_BSD?
1999-10-30 13:11:06 +08:00
# AIX 4 /usr/bin/installbsd, which doesn't work without a -g flag
Initial revision
1999-10-08 07:47:09 +08:00
# AFS /usr/afsws/bin/install, which mishandles nonexistent args
# SVR4 /usr/ucb/install, which tries to use the nonexistent group "staff"
Add -Wpointer-arith to the list of warnings we enable with GCC.
2005-11-08 10:59:40 +08:00
# OS/2's system install, which has a completely different semantic
Initial revision
1999-10-08 07:47:09 +08:00
# ./install, which can be erroneously created by make from ./install.sh.
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
# Reject install programs that cannot install multiple files.
{ $as_echo "$as_me:${as_lineno-$LINENO}: checking for a BSD-compatible install" >&5
$as_echo_n "checking for a BSD-compatible install... " >&6; }
Initial revision
1999-10-08 07:47:09 +08:00
if test -z "$INSTALL"; then
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
if ${ac_cv_path_install+:} false; then :
$as_echo_n "(cached) " >&6
Regenerate with autoconf 2.57.
2004-01-14 11:15:08 +08:00
else
From Andrew Church <andrew@users.sourceforge.net>: when testing for "pcap_version", "pcap_debug", and "yydebug", don't add our own functions referring to those variables - GCC 3.4.1 optimizes the test code out before the link is done, as it's in a function that's not called.
2004-08-27 15:17:03 +08:00
as_save_IFS=$IFS; IFS=$PATH_SEPARATOR
for as_dir in $PATH
do
IFS=$as_save_IFS
test -z "$as_dir" && as_dir=.
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
# Account for people who put trailing slashes in PATH elements.
case $as_dir/ in #((
./ | .// | /[cC]/* | \
From Andrew Church <andrew@users.sourceforge.net>: when testing for "pcap_version", "pcap_debug", and "yydebug", don't add our own functions referring to those variables - GCC 3.4.1 optimizes the test code out before the link is done, as it's in a function that's not called.
2004-08-27 15:17:03 +08:00
/etc/* | /usr/sbin/* | /usr/etc/* | /sbin/* | /usr/afsws/bin/* | \
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
?:[\\/]os2[\\/]install[\\/]* | ?:[\\/]OS2[\\/]INSTALL[\\/]* | \
From Andrew Church <andrew@users.sourceforge.net>: when testing for "pcap_version", "pcap_debug", and "yydebug", don't add our own functions referring to those variables - GCC 3.4.1 optimizes the test code out before the link is done, as it's in a function that's not called.
2004-08-27 15:17:03 +08:00
/usr/ucb/* ) ;;
*)
# OSF1 and SCO ODT 3.0 have their own names for install.
# Don't use installbsd from OSF since it installs stuff as root
# by default.
for ac_prog in ginstall scoinst install; do
for ac_exec_ext in '' $ac_executable_extensions; do
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
if as_fn_executable_p "$as_dir/$ac_prog$ac_exec_ext"; then
Add -Wpointer-arith to the list of warnings we enable with GCC.
2005-11-08 10:59:40 +08:00
if test $ac_prog = install &&
grep dspmsg "$as_dir/$ac_prog$ac_exec_ext" >/dev/null 2>&1; then
# AIX install. It has an incompatible calling convention.
:
elif test $ac_prog = install &&
grep pwplus "$as_dir/$ac_prog$ac_exec_ext" >/dev/null 2>&1; then
# program-specific install script used by HP pwplus--don't use.
:
else
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
rm -rf conftest.one conftest.two conftest.dir
echo one > conftest.one
echo two > conftest.two
mkdir conftest.dir
if "$as_dir/$ac_prog$ac_exec_ext" -c conftest.one conftest.two "`pwd`/conftest.dir" &&
test -s conftest.one && test -s conftest.two &&
test -s conftest.dir/conftest.one &&
test -s conftest.dir/conftest.two
then
ac_cv_path_install="$as_dir/$ac_prog$ac_exec_ext -c"
break 3
fi
Add -Wpointer-arith to the list of warnings we enable with GCC.
2005-11-08 10:59:40 +08:00
fi
fi
Initial revision
1999-10-08 07:47:09 +08:00
done
From Andrew Church <andrew@users.sourceforge.net>: when testing for "pcap_version", "pcap_debug", and "yydebug", don't add our own functions referring to those variables - GCC 3.4.1 optimizes the test code out before the link is done, as it's in a function that's not called.
2004-08-27 15:17:03 +08:00
done
;;
esac
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
done
We support building tcpdump with versions of libpcap other than the one with which it was released, and DLT_BLUETOOTH_HCI_H4_WITH_PHDR might be defined by pcap-bpf.h without pcap/bluetooth.h being present (as appears to be the case on Fedora 9, for example), so check whether <pcap/bluetooth.h> is usable. Update a comment - F9 appears to have a "/usr/include/pcap.h" if you install the libpcap headers. When adding -I flags when running a compiler-based test, add them to CPPFLAGS, not CFLAGS - the latter doesn't work right with AC_CHECK_HEADERS, as the "gcc -E" run doesn't have the -I flags added.
2008-09-26 05:45:50 +08:00
IFS=$as_save_IFS
From Andrew Church <andrew@users.sourceforge.net>: when testing for "pcap_version", "pcap_debug", and "yydebug", don't add our own functions referring to those variables - GCC 3.4.1 optimizes the test code out before the link is done, as it's in a function that's not called.
2004-08-27 15:17:03 +08:00
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
rm -rf conftest.one conftest.two conftest.dir
Initial revision
1999-10-08 07:47:09 +08:00
fi
if test "${ac_cv_path_install+set}" = set; then
Regenerate with autoconf 2.57.
2004-01-14 11:15:08 +08:00
INSTALL=$ac_cv_path_install
Initial revision
1999-10-08 07:47:09 +08:00
else
We support building tcpdump with versions of libpcap other than the one with which it was released, and DLT_BLUETOOTH_HCI_H4_WITH_PHDR might be defined by pcap-bpf.h without pcap/bluetooth.h being present (as appears to be the case on Fedora 9, for example), so check whether <pcap/bluetooth.h> is usable. Update a comment - F9 appears to have a "/usr/include/pcap.h" if you install the libpcap headers. When adding -I flags when running a compiler-based test, add them to CPPFLAGS, not CFLAGS - the latter doesn't work right with AC_CHECK_HEADERS, as the "gcc -E" run doesn't have the -I flags added.
2008-09-26 05:45:50 +08:00
# As a last resort, use the slow shell script. Don't cache a
# value for INSTALL within a source directory, because that will
Initial revision
1999-10-08 07:47:09 +08:00
# break other packages using the cache if that directory is
We support building tcpdump with versions of libpcap other than the one with which it was released, and DLT_BLUETOOTH_HCI_H4_WITH_PHDR might be defined by pcap-bpf.h without pcap/bluetooth.h being present (as appears to be the case on Fedora 9, for example), so check whether <pcap/bluetooth.h> is usable. Update a comment - F9 appears to have a "/usr/include/pcap.h" if you install the libpcap headers. When adding -I flags when running a compiler-based test, add them to CPPFLAGS, not CFLAGS - the latter doesn't work right with AC_CHECK_HEADERS, as the "gcc -E" run doesn't have the -I flags added.
2008-09-26 05:45:50 +08:00
# removed, or if the value is a relative name.
Regenerate with autoconf 2.57.
2004-01-14 11:15:08 +08:00
INSTALL=$ac_install_sh
Initial revision
1999-10-08 07:47:09 +08:00
fi
fi
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
{ $as_echo "$as_me:${as_lineno-$LINENO}: result: $INSTALL" >&5
$as_echo "$INSTALL" >&6; }
Initial revision
1999-10-08 07:47:09 +08:00
# Use test -z because SunOS4 sh mishandles braces in ${var-val}.
# It thinks the first close brace ends the variable substitution.
test -z "$INSTALL_PROGRAM" && INSTALL_PROGRAM='${INSTALL}'
Regenerate with autoconf 2.57.
2004-01-14 11:15:08 +08:00
test -z "$INSTALL_SCRIPT" && INSTALL_SCRIPT='${INSTALL}'
Bring in KAME IPv6 tcpdump. replaces esp/ah/isakmp decoder. Hope I did not break anything. Portability on IPv4-only node needs checking, I'll do this very soon. (sorry for rather jumbo commit) XXx what is _FAVOR_BSD?
1999-10-30 13:11:06 +08:00
Initial revision
1999-10-08 07:47:09 +08:00
test -z "$INSTALL_DATA" && INSTALL_DATA='${INSTALL} -m 644'
We support building tcpdump with versions of libpcap other than the one with which it was released, and DLT_BLUETOOTH_HCI_H4_WITH_PHDR might be defined by pcap-bpf.h without pcap/bluetooth.h being present (as appears to be the case on Fedora 9, for example), so check whether <pcap/bluetooth.h> is usable. Update a comment - F9 appears to have a "/usr/include/pcap.h" if you install the libpcap headers. When adding -I flags when running a compiler-based test, add them to CPPFLAGS, not CFLAGS - the latter doesn't work right with AC_CHECK_HEADERS, as the "gcc -E" run doesn't have the -I flags added.
2008-09-26 05:45:50 +08:00
ac_config_headers="$ac_config_headers config.h"
From Andrew Church <andrew@users.sourceforge.net>: when testing for "pcap_version", "pcap_debug", and "yydebug", don't add our own functions referring to those variables - GCC 3.4.1 optimizes the test code out before the link is done, as it's in a function that's not called.
2004-08-27 15:17:03 +08:00
Switch to config.h instead of passing defines in DEFS.
1999-11-21 17:36:43 +08:00
We support building tcpdump with versions of libpcap other than the one with which it was released, and DLT_BLUETOOTH_HCI_H4_WITH_PHDR might be defined by pcap-bpf.h without pcap/bluetooth.h being present (as appears to be the case on Fedora 9, for example), so check whether <pcap/bluetooth.h> is usable. Update a comment - F9 appears to have a "/usr/include/pcap.h" if you install the libpcap headers. When adding -I flags when running a compiler-based test, add them to CPPFLAGS, not CFLAGS - the latter doesn't work right with AC_CHECK_HEADERS, as the "gcc -E" run doesn't have the -I flags added.
2008-09-26 05:45:50 +08:00
ac_config_commands="$ac_config_commands default-1"
Run the tcpdump man page through config, so that it refers to the right man page sections. Have it refer to the new pcap-savefile man page for a description of the savefile format.
2008-10-28 05:20:16 +08:00
ac_config_files="$ac_config_files Makefile tcpdump.1"
From Andrew Church <andrew@users.sourceforge.net>: when testing for "pcap_version", "pcap_debug", and "yydebug", don't add our own functions referring to those variables - GCC 3.4.1 optimizes the test code out before the link is done, as it's in a function that's not called.
2004-08-27 15:17:03 +08:00
Regenerate with autoconf 2.57.
2004-01-14 11:15:08 +08:00
cat >confcache <<\_ACEOF
Initial revision
1999-10-08 07:47:09 +08:00
# This file is a shell script that caches the results of configure
# tests run on this system so they can be shared between configure
Regenerate with autoconf 2.57.
2004-01-14 11:15:08 +08:00
# scripts and configure runs, see configure's option --config-cache.
# It is not useful on other systems. If it contains results you don't
# want to keep, you may remove or edit it.
Initial revision
1999-10-08 07:47:09 +08:00
#
Regenerate with autoconf 2.57.
2004-01-14 11:15:08 +08:00
# config.status only pays attention to the cache file if you give it
# the --recheck option to rerun configure.
Initial revision
1999-10-08 07:47:09 +08:00
#
From Andrew Church <andrew@users.sourceforge.net>: when testing for "pcap_version", "pcap_debug", and "yydebug", don't add our own functions referring to those variables - GCC 3.4.1 optimizes the test code out before the link is done, as it's in a function that's not called.
2004-08-27 15:17:03 +08:00
# `ac_cv_env_foo' variables (set or unset) will be overridden when
Regenerate with autoconf 2.57.
2004-01-14 11:15:08 +08:00
# loading this file, other *unset* `ac_cv_foo' will be assigned the
# following values.
_ACEOF
Initial revision
1999-10-08 07:47:09 +08:00
# The following way of writing the cache mishandles newlines in values,
# but we know of no workaround that is simple, portable, and efficient.
We support building tcpdump with versions of libpcap other than the one with which it was released, and DLT_BLUETOOTH_HCI_H4_WITH_PHDR might be defined by pcap-bpf.h without pcap/bluetooth.h being present (as appears to be the case on Fedora 9, for example), so check whether <pcap/bluetooth.h> is usable. Update a comment - F9 appears to have a "/usr/include/pcap.h" if you install the libpcap headers. When adding -I flags when running a compiler-based test, add them to CPPFLAGS, not CFLAGS - the latter doesn't work right with AC_CHECK_HEADERS, as the "gcc -E" run doesn't have the -I flags added.
2008-09-26 05:45:50 +08:00
# So, we kill variables containing newlines.
Initial revision
1999-10-08 07:47:09 +08:00
# Ultrix sh set writes to stderr and can't be redirected directly,
# and sets the high bit in the cache file unless we assign to the vars.
We support building tcpdump with versions of libpcap other than the one with which it was released, and DLT_BLUETOOTH_HCI_H4_WITH_PHDR might be defined by pcap-bpf.h without pcap/bluetooth.h being present (as appears to be the case on Fedora 9, for example), so check whether <pcap/bluetooth.h> is usable. Update a comment - F9 appears to have a "/usr/include/pcap.h" if you install the libpcap headers. When adding -I flags when running a compiler-based test, add them to CPPFLAGS, not CFLAGS - the latter doesn't work right with AC_CHECK_HEADERS, as the "gcc -E" run doesn't have the -I flags added.
2008-09-26 05:45:50 +08:00
(
for ac_var in `(set) 2>&1 | sed -n 's/^\([a-zA-Z_][a-zA-Z0-9_]*\)=.*/\1/p'`; do
eval ac_val=\$$ac_var
case $ac_val in #(
*${as_nl}*)
case $ac_var in #(
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
*_cv_*) { $as_echo "$as_me:${as_lineno-$LINENO}: WARNING: cache variable $ac_var contains a newline" >&5
$as_echo "$as_me: WARNING: cache variable $ac_var contains a newline" >&2;} ;;
We support building tcpdump with versions of libpcap other than the one with which it was released, and DLT_BLUETOOTH_HCI_H4_WITH_PHDR might be defined by pcap-bpf.h without pcap/bluetooth.h being present (as appears to be the case on Fedora 9, for example), so check whether <pcap/bluetooth.h> is usable. Update a comment - F9 appears to have a "/usr/include/pcap.h" if you install the libpcap headers. When adding -I flags when running a compiler-based test, add them to CPPFLAGS, not CFLAGS - the latter doesn't work right with AC_CHECK_HEADERS, as the "gcc -E" run doesn't have the -I flags added.
2008-09-26 05:45:50 +08:00
esac
case $ac_var in #(
_ | IFS | as_nl) ;; #(
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
BASH_ARGV | BASH_SOURCE) eval $ac_var= ;; #(
*) { eval $ac_var=; unset $ac_var;} ;;
We support building tcpdump with versions of libpcap other than the one with which it was released, and DLT_BLUETOOTH_HCI_H4_WITH_PHDR might be defined by pcap-bpf.h without pcap/bluetooth.h being present (as appears to be the case on Fedora 9, for example), so check whether <pcap/bluetooth.h> is usable. Update a comment - F9 appears to have a "/usr/include/pcap.h" if you install the libpcap headers. When adding -I flags when running a compiler-based test, add them to CPPFLAGS, not CFLAGS - the latter doesn't work right with AC_CHECK_HEADERS, as the "gcc -E" run doesn't have the -I flags added.
2008-09-26 05:45:50 +08:00
esac ;;
esac
done
(set) 2>&1 |
case $as_nl`(ac_space=' '; set) 2>&1` in #(
*${as_nl}ac_space=\ *)
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
# `set' does not quote correctly, so add quotes: double-quote
# substitution turns \\\\ into \\, and sed turns \\ into \.
Regenerate with autoconf 2.57.
2004-01-14 11:15:08 +08:00
sed -n \
Add -Wpointer-arith to the list of warnings we enable with GCC.
2005-11-08 10:59:40 +08:00
"s/'/'\\\\''/g;
s/^\\([_$as_cr_alnum]*_cv_[_$as_cr_alnum]*\\)=\\(.*\\)/\\1='\\2'/p"
We support building tcpdump with versions of libpcap other than the one with which it was released, and DLT_BLUETOOTH_HCI_H4_WITH_PHDR might be defined by pcap-bpf.h without pcap/bluetooth.h being present (as appears to be the case on Fedora 9, for example), so check whether <pcap/bluetooth.h> is usable. Update a comment - F9 appears to have a "/usr/include/pcap.h" if you install the libpcap headers. When adding -I flags when running a compiler-based test, add them to CPPFLAGS, not CFLAGS - the latter doesn't work right with AC_CHECK_HEADERS, as the "gcc -E" run doesn't have the -I flags added.
2008-09-26 05:45:50 +08:00
;; #(
Regenerate with autoconf 2.57.
2004-01-14 11:15:08 +08:00
*)
# `set' quotes correctly as required by POSIX, so do not add quotes.
We support building tcpdump with versions of libpcap other than the one with which it was released, and DLT_BLUETOOTH_HCI_H4_WITH_PHDR might be defined by pcap-bpf.h without pcap/bluetooth.h being present (as appears to be the case on Fedora 9, for example), so check whether <pcap/bluetooth.h> is usable. Update a comment - F9 appears to have a "/usr/include/pcap.h" if you install the libpcap headers. When adding -I flags when running a compiler-based test, add them to CPPFLAGS, not CFLAGS - the latter doesn't work right with AC_CHECK_HEADERS, as the "gcc -E" run doesn't have the -I flags added.
2008-09-26 05:45:50 +08:00
sed -n "/^[_$as_cr_alnum]*_cv_[_$as_cr_alnum]*=/p"
Regenerate with autoconf 2.57.
2004-01-14 11:15:08 +08:00
;;
We support building tcpdump with versions of libpcap other than the one with which it was released, and DLT_BLUETOOTH_HCI_H4_WITH_PHDR might be defined by pcap-bpf.h without pcap/bluetooth.h being present (as appears to be the case on Fedora 9, for example), so check whether <pcap/bluetooth.h> is usable. Update a comment - F9 appears to have a "/usr/include/pcap.h" if you install the libpcap headers. When adding -I flags when running a compiler-based test, add them to CPPFLAGS, not CFLAGS - the latter doesn't work right with AC_CHECK_HEADERS, as the "gcc -E" run doesn't have the -I flags added.
2008-09-26 05:45:50 +08:00
esac |
sort
) |
Regenerate with autoconf 2.57.
2004-01-14 11:15:08 +08:00
sed '
We support building tcpdump with versions of libpcap other than the one with which it was released, and DLT_BLUETOOTH_HCI_H4_WITH_PHDR might be defined by pcap-bpf.h without pcap/bluetooth.h being present (as appears to be the case on Fedora 9, for example), so check whether <pcap/bluetooth.h> is usable. Update a comment - F9 appears to have a "/usr/include/pcap.h" if you install the libpcap headers. When adding -I flags when running a compiler-based test, add them to CPPFLAGS, not CFLAGS - the latter doesn't work right with AC_CHECK_HEADERS, as the "gcc -E" run doesn't have the -I flags added.
2008-09-26 05:45:50 +08:00
/^ac_cv_env_/b end
Regenerate with autoconf 2.57.
2004-01-14 11:15:08 +08:00
t clear
We support building tcpdump with versions of libpcap other than the one with which it was released, and DLT_BLUETOOTH_HCI_H4_WITH_PHDR might be defined by pcap-bpf.h without pcap/bluetooth.h being present (as appears to be the case on Fedora 9, for example), so check whether <pcap/bluetooth.h> is usable. Update a comment - F9 appears to have a "/usr/include/pcap.h" if you install the libpcap headers. When adding -I flags when running a compiler-based test, add them to CPPFLAGS, not CFLAGS - the latter doesn't work right with AC_CHECK_HEADERS, as the "gcc -E" run doesn't have the -I flags added.
2008-09-26 05:45:50 +08:00
:clear
Regenerate with autoconf 2.57.
2004-01-14 11:15:08 +08:00
s/^\([^=]*\)=\(.*[{}].*\)$/test "${\1+set}" = set || &/
t end
We support building tcpdump with versions of libpcap other than the one with which it was released, and DLT_BLUETOOTH_HCI_H4_WITH_PHDR might be defined by pcap-bpf.h without pcap/bluetooth.h being present (as appears to be the case on Fedora 9, for example), so check whether <pcap/bluetooth.h> is usable. Update a comment - F9 appears to have a "/usr/include/pcap.h" if you install the libpcap headers. When adding -I flags when running a compiler-based test, add them to CPPFLAGS, not CFLAGS - the latter doesn't work right with AC_CHECK_HEADERS, as the "gcc -E" run doesn't have the -I flags added.
2008-09-26 05:45:50 +08:00
s/^\([^=]*\)=\(.*\)$/\1=${\1=\2}/
:end' >>confcache
if diff "$cache_file" confcache >/dev/null 2>&1; then :; else
Check for extra networking libraries before checking for IPv6. On some platforms, such as SunOS 5.x, building the "do we have IPv6 support?" test program requires the extra networking libraries, so we need to know what extra networking libraries are required before doing that test.
2013-04-07 04:03:58 +08:00
if test -w "$cache_file"; then
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
if test "x$cache_file" != "x/dev/null"; then
{ $as_echo "$as_me:${as_lineno-$LINENO}: updating cache $cache_file" >&5
$as_echo "$as_me: updating cache $cache_file" >&6;}
if test ! -f "$cache_file" || test -h "$cache_file"; then
cat confcache >"$cache_file"
else
case $cache_file in #(
*/* | ?:*)
mv -f confcache "$cache_file"$$ &&
mv -f "$cache_file"$$ "$cache_file" ;; #(
*)
mv -f confcache "$cache_file" ;;
esac
fi
fi
Initial revision
1999-10-08 07:47:09 +08:00
else
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
{ $as_echo "$as_me:${as_lineno-$LINENO}: not updating unwritable cache $cache_file" >&5
$as_echo "$as_me: not updating unwritable cache $cache_file" >&6;}
Initial revision
1999-10-08 07:47:09 +08:00
fi
fi
rm -f confcache
test "x$prefix" = xNONE && prefix=$ac_default_prefix
# Let make expand exec_prefix.
test "x$exec_prefix" = xNONE && exec_prefix='${prefix}'
Switch to config.h instead of passing defines in DEFS.
1999-11-21 17:36:43 +08:00
DEFS=-DHAVE_CONFIG_H
Initial revision
1999-10-08 07:47:09 +08:00
From Andrew Church <andrew@users.sourceforge.net>: when testing for "pcap_version", "pcap_debug", and "yydebug", don't add our own functions referring to those variables - GCC 3.4.1 optimizes the test code out before the link is done, as it's in a function that's not called.
2004-08-27 15:17:03 +08:00
ac_libobjs=
ac_ltlibobjs=
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
U=
From Andrew Church <andrew@users.sourceforge.net>: when testing for "pcap_version", "pcap_debug", and "yydebug", don't add our own functions referring to those variables - GCC 3.4.1 optimizes the test code out before the link is done, as it's in a function that's not called.
2004-08-27 15:17:03 +08:00
for ac_i in : $LIBOBJS; do test "x$ac_i" = x: && continue
# 1. Remove the extension, and $U if already installed.
We support building tcpdump with versions of libpcap other than the one with which it was released, and DLT_BLUETOOTH_HCI_H4_WITH_PHDR might be defined by pcap-bpf.h without pcap/bluetooth.h being present (as appears to be the case on Fedora 9, for example), so check whether <pcap/bluetooth.h> is usable. Update a comment - F9 appears to have a "/usr/include/pcap.h" if you install the libpcap headers. When adding -I flags when running a compiler-based test, add them to CPPFLAGS, not CFLAGS - the latter doesn't work right with AC_CHECK_HEADERS, as the "gcc -E" run doesn't have the -I flags added.
2008-09-26 05:45:50 +08:00
ac_script='s/\$U\././;s/\.o$//;s/\.obj$//'
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
ac_i=`$as_echo "$ac_i" | sed "$ac_script"`
We support building tcpdump with versions of libpcap other than the one with which it was released, and DLT_BLUETOOTH_HCI_H4_WITH_PHDR might be defined by pcap-bpf.h without pcap/bluetooth.h being present (as appears to be the case on Fedora 9, for example), so check whether <pcap/bluetooth.h> is usable. Update a comment - F9 appears to have a "/usr/include/pcap.h" if you install the libpcap headers. When adding -I flags when running a compiler-based test, add them to CPPFLAGS, not CFLAGS - the latter doesn't work right with AC_CHECK_HEADERS, as the "gcc -E" run doesn't have the -I flags added.
2008-09-26 05:45:50 +08:00
# 2. Prepend LIBOBJDIR. When used with automake>=1.10 LIBOBJDIR
# will be set to the directory where LIBOBJS objects are built.
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
as_fn_append ac_libobjs " \${LIBOBJDIR}$ac_i\$U.$ac_objext"
as_fn_append ac_ltlibobjs " \${LIBOBJDIR}$ac_i"'$U.lo'
From Andrew Church <andrew@users.sourceforge.net>: when testing for "pcap_version", "pcap_debug", and "yydebug", don't add our own functions referring to those variables - GCC 3.4.1 optimizes the test code out before the link is done, as it's in a function that's not called.
2004-08-27 15:17:03 +08:00
done
LIBOBJS=$ac_libobjs
LTLIBOBJS=$ac_ltlibobjs
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
: "${CONFIG_STATUS=./config.status}"
ac_write_fail=0
Regenerate with autoconf 2.57.
2004-01-14 11:15:08 +08:00
ac_clean_files_save=$ac_clean_files
ac_clean_files="$ac_clean_files $CONFIG_STATUS"
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
{ $as_echo "$as_me:${as_lineno-$LINENO}: creating $CONFIG_STATUS" >&5
$as_echo "$as_me: creating $CONFIG_STATUS" >&6;}
as_write_fail=0
cat >$CONFIG_STATUS <<_ASEOF || as_write_fail=1
Regenerate with autoconf 2.57.
2004-01-14 11:15:08 +08:00
#! $SHELL
From Andrew Church <andrew@users.sourceforge.net>: when testing for "pcap_version", "pcap_debug", and "yydebug", don't add our own functions referring to those variables - GCC 3.4.1 optimizes the test code out before the link is done, as it's in a function that's not called.
2004-08-27 15:17:03 +08:00
# Generated by $as_me.
Initial revision
1999-10-08 07:47:09 +08:00
# Run this file to recreate the current configuration.
# Compiler output produced by configure, useful for debugging
Regenerate with autoconf 2.57.
2004-01-14 11:15:08 +08:00
# configure, is in config.log if it exists.
Initial revision
1999-10-08 07:47:09 +08:00
Regenerate with autoconf 2.57.
2004-01-14 11:15:08 +08:00
debug=false
From Andrew Church <andrew@users.sourceforge.net>: when testing for "pcap_version", "pcap_debug", and "yydebug", don't add our own functions referring to those variables - GCC 3.4.1 optimizes the test code out before the link is done, as it's in a function that's not called.
2004-08-27 15:17:03 +08:00
ac_cs_recheck=false
ac_cs_silent=false
Check for extra networking libraries before checking for IPv6. On some platforms, such as SunOS 5.x, building the "do we have IPv6 support?" test program requires the extra networking libraries, so we need to know what extra networking libraries are required before doing that test.
2013-04-07 04:03:58 +08:00
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
SHELL=\${CONFIG_SHELL-$SHELL}
export SHELL
_ASEOF
cat >>$CONFIG_STATUS <<\_ASEOF || as_write_fail=1
## -------------------- ##
## M4sh Initialization. ##
## -------------------- ##
From Andrew Church <andrew@users.sourceforge.net>: when testing for "pcap_version", "pcap_debug", and "yydebug", don't add our own functions referring to those variables - GCC 3.4.1 optimizes the test code out before the link is done, as it's in a function that's not called.
2004-08-27 15:17:03 +08:00
We support building tcpdump with versions of libpcap other than the one with which it was released, and DLT_BLUETOOTH_HCI_H4_WITH_PHDR might be defined by pcap-bpf.h without pcap/bluetooth.h being present (as appears to be the case on Fedora 9, for example), so check whether <pcap/bluetooth.h> is usable. Update a comment - F9 appears to have a "/usr/include/pcap.h" if you install the libpcap headers. When adding -I flags when running a compiler-based test, add them to CPPFLAGS, not CFLAGS - the latter doesn't work right with AC_CHECK_HEADERS, as the "gcc -E" run doesn't have the -I flags added.
2008-09-26 05:45:50 +08:00
# Be more Bourne compatible
DUALCASE=1; export DUALCASE # for MKS sh
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
if test -n "${ZSH_VERSION+set}" && (emulate sh) >/dev/null 2>&1; then :
Regenerate with autoconf 2.57.
2004-01-14 11:15:08 +08:00
emulate sh
NULLCMD=:
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
# Pre-4.2 versions of Zsh do word splitting on ${1+"$@"}, which
From Andrew Church <andrew@users.sourceforge.net>: when testing for "pcap_version", "pcap_debug", and "yydebug", don't add our own functions referring to those variables - GCC 3.4.1 optimizes the test code out before the link is done, as it's in a function that's not called.
2004-08-27 15:17:03 +08:00
# is contrary to our usage. Disable this feature.
alias -g '${1+"$@"}'='"$@"'
We support building tcpdump with versions of libpcap other than the one with which it was released, and DLT_BLUETOOTH_HCI_H4_WITH_PHDR might be defined by pcap-bpf.h without pcap/bluetooth.h being present (as appears to be the case on Fedora 9, for example), so check whether <pcap/bluetooth.h> is usable. Update a comment - F9 appears to have a "/usr/include/pcap.h" if you install the libpcap headers. When adding -I flags when running a compiler-based test, add them to CPPFLAGS, not CFLAGS - the latter doesn't work right with AC_CHECK_HEADERS, as the "gcc -E" run doesn't have the -I flags added.
2008-09-26 05:45:50 +08:00
setopt NO_GLOB_SUBST
else
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
case `(set -o) 2>/dev/null` in #(
*posix*) :
set -o posix ;; #(
*) :
;;
We support building tcpdump with versions of libpcap other than the one with which it was released, and DLT_BLUETOOTH_HCI_H4_WITH_PHDR might be defined by pcap-bpf.h without pcap/bluetooth.h being present (as appears to be the case on Fedora 9, for example), so check whether <pcap/bluetooth.h> is usable. Update a comment - F9 appears to have a "/usr/include/pcap.h" if you install the libpcap headers. When adding -I flags when running a compiler-based test, add them to CPPFLAGS, not CFLAGS - the latter doesn't work right with AC_CHECK_HEADERS, as the "gcc -E" run doesn't have the -I flags added.
2008-09-26 05:45:50 +08:00
esac
fi
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
as_nl='
'
export as_nl
# Printing a long string crashes Solaris 7 /usr/bin/printf.
as_echo='\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\'
as_echo=$as_echo$as_echo$as_echo$as_echo$as_echo
as_echo=$as_echo$as_echo$as_echo$as_echo$as_echo$as_echo
# Prefer a ksh shell builtin over an external printf program on Solaris,
# but without wasting forks for bash or zsh.
if test -z "$BASH_VERSION$ZSH_VERSION" \
&& (test "X`print -r -- $as_echo`" = "X$as_echo") 2>/dev/null; then
as_echo='print -r --'
as_echo_n='print -rn --'
elif (test "X`printf %s $as_echo`" = "X$as_echo") 2>/dev/null; then
as_echo='printf %s\n'
as_echo_n='printf %s'
else
if test "X`(/usr/ucb/echo -n -n $as_echo) 2>/dev/null`" = "X-n $as_echo"; then
as_echo_body='eval /usr/ucb/echo -n "$1$as_nl"'
as_echo_n='/usr/ucb/echo -n'
We support building tcpdump with versions of libpcap other than the one with which it was released, and DLT_BLUETOOTH_HCI_H4_WITH_PHDR might be defined by pcap-bpf.h without pcap/bluetooth.h being present (as appears to be the case on Fedora 9, for example), so check whether <pcap/bluetooth.h> is usable. Update a comment - F9 appears to have a "/usr/include/pcap.h" if you install the libpcap headers. When adding -I flags when running a compiler-based test, add them to CPPFLAGS, not CFLAGS - the latter doesn't work right with AC_CHECK_HEADERS, as the "gcc -E" run doesn't have the -I flags added.
2008-09-26 05:45:50 +08:00
else
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
as_echo_body='eval expr "X$1" : "X\\(.*\\)"'
as_echo_n_body='eval
arg=$1;
case $arg in #(
*"$as_nl"*)
expr "X$arg" : "X\\(.*\\)$as_nl";
arg=`expr "X$arg" : ".*$as_nl\\(.*\\)"`;;
esac;
expr "X$arg" : "X\\(.*\\)" | tr -d "$as_nl"
'
export as_echo_n_body
as_echo_n='sh -c $as_echo_n_body as_echo'
We support building tcpdump with versions of libpcap other than the one with which it was released, and DLT_BLUETOOTH_HCI_H4_WITH_PHDR might be defined by pcap-bpf.h without pcap/bluetooth.h being present (as appears to be the case on Fedora 9, for example), so check whether <pcap/bluetooth.h> is usable. Update a comment - F9 appears to have a "/usr/include/pcap.h" if you install the libpcap headers. When adding -I flags when running a compiler-based test, add them to CPPFLAGS, not CFLAGS - the latter doesn't work right with AC_CHECK_HEADERS, as the "gcc -E" run doesn't have the -I flags added.
2008-09-26 05:45:50 +08:00
fi
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
export as_echo_body
as_echo='sh -c $as_echo_body as_echo'
Regenerate with autoconf 2.57.
2004-01-14 11:15:08 +08:00
fi
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
# The user is always right.
if test "${PATH_SEPARATOR+set}" != set; then
PATH_SEPARATOR=:
(PATH='/bin;/bin'; FPATH=$PATH; sh -c :) >/dev/null 2>&1 && {
(PATH='/bin:/bin'; FPATH=$PATH; sh -c :) >/dev/null 2>&1 ||
PATH_SEPARATOR=';'
}
From Andrew Church <andrew@users.sourceforge.net>: when testing for "pcap_version", "pcap_debug", and "yydebug", don't add our own functions referring to those variables - GCC 3.4.1 optimizes the test code out before the link is done, as it's in a function that's not called.
2004-08-27 15:17:03 +08:00
fi
We support building tcpdump with versions of libpcap other than the one with which it was released, and DLT_BLUETOOTH_HCI_H4_WITH_PHDR might be defined by pcap-bpf.h without pcap/bluetooth.h being present (as appears to be the case on Fedora 9, for example), so check whether <pcap/bluetooth.h> is usable. Update a comment - F9 appears to have a "/usr/include/pcap.h" if you install the libpcap headers. When adding -I flags when running a compiler-based test, add them to CPPFLAGS, not CFLAGS - the latter doesn't work right with AC_CHECK_HEADERS, as the "gcc -E" run doesn't have the -I flags added.
2008-09-26 05:45:50 +08:00
# IFS
# We need space, tab and new line, in precisely that order. Quoting is
# there to prevent editors from complaining about space-tab.
# (If _AS_PATH_WALK were called with IFS unset, it would disable word
# splitting by setting IFS to empty value.)
IFS=" "" $as_nl"
# Find who we are. Look in the path if we contain no directory separator.
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
as_myself=
case $0 in #((
We support building tcpdump with versions of libpcap other than the one with which it was released, and DLT_BLUETOOTH_HCI_H4_WITH_PHDR might be defined by pcap-bpf.h without pcap/bluetooth.h being present (as appears to be the case on Fedora 9, for example), so check whether <pcap/bluetooth.h> is usable. Update a comment - F9 appears to have a "/usr/include/pcap.h" if you install the libpcap headers. When adding -I flags when running a compiler-based test, add them to CPPFLAGS, not CFLAGS - the latter doesn't work right with AC_CHECK_HEADERS, as the "gcc -E" run doesn't have the -I flags added.
2008-09-26 05:45:50 +08:00
*[\\/]* ) as_myself=$0 ;;
*) as_save_IFS=$IFS; IFS=$PATH_SEPARATOR
for as_dir in $PATH
do
IFS=$as_save_IFS
test -z "$as_dir" && as_dir=.
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
test -r "$as_dir/$0" && as_myself=$as_dir/$0 && break
done
We support building tcpdump with versions of libpcap other than the one with which it was released, and DLT_BLUETOOTH_HCI_H4_WITH_PHDR might be defined by pcap-bpf.h without pcap/bluetooth.h being present (as appears to be the case on Fedora 9, for example), so check whether <pcap/bluetooth.h> is usable. Update a comment - F9 appears to have a "/usr/include/pcap.h" if you install the libpcap headers. When adding -I flags when running a compiler-based test, add them to CPPFLAGS, not CFLAGS - the latter doesn't work right with AC_CHECK_HEADERS, as the "gcc -E" run doesn't have the -I flags added.
2008-09-26 05:45:50 +08:00
IFS=$as_save_IFS
;;
esac
# We did not find ourselves, most probably we were run as `sh COMMAND'
# in which case we are not to be found in the path.
if test "x$as_myself" = x; then
as_myself=$0
fi
if test ! -f "$as_myself"; then
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
$as_echo "$as_myself: error: cannot find myself; rerun with an absolute file name" >&2
exit 1
We support building tcpdump with versions of libpcap other than the one with which it was released, and DLT_BLUETOOTH_HCI_H4_WITH_PHDR might be defined by pcap-bpf.h without pcap/bluetooth.h being present (as appears to be the case on Fedora 9, for example), so check whether <pcap/bluetooth.h> is usable. Update a comment - F9 appears to have a "/usr/include/pcap.h" if you install the libpcap headers. When adding -I flags when running a compiler-based test, add them to CPPFLAGS, not CFLAGS - the latter doesn't work right with AC_CHECK_HEADERS, as the "gcc -E" run doesn't have the -I flags added.
2008-09-26 05:45:50 +08:00
fi
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
# Unset variables that we do not need and which cause bugs (e.g. in
# pre-3.0 UWIN ksh). But do not cause bugs in bash 2.01; the "|| exit 1"
# suppresses any "Segmentation fault" message there. '((' could
# trigger a bug in pdksh 5.2.14.
for as_var in BASH_ENV ENV MAIL MAILPATH
do eval test x\${$as_var+set} = xset \
&& ( (unset $as_var) || exit 1) >/dev/null 2>&1 && unset $as_var || :
We support building tcpdump with versions of libpcap other than the one with which it was released, and DLT_BLUETOOTH_HCI_H4_WITH_PHDR might be defined by pcap-bpf.h without pcap/bluetooth.h being present (as appears to be the case on Fedora 9, for example), so check whether <pcap/bluetooth.h> is usable. Update a comment - F9 appears to have a "/usr/include/pcap.h" if you install the libpcap headers. When adding -I flags when running a compiler-based test, add them to CPPFLAGS, not CFLAGS - the latter doesn't work right with AC_CHECK_HEADERS, as the "gcc -E" run doesn't have the -I flags added.
2008-09-26 05:45:50 +08:00
done
From Andrew Church <andrew@users.sourceforge.net>: when testing for "pcap_version", "pcap_debug", and "yydebug", don't add our own functions referring to those variables - GCC 3.4.1 optimizes the test code out before the link is done, as it's in a function that's not called.
2004-08-27 15:17:03 +08:00
PS1='$ '
PS2='> '
PS4='+ '
# NLS nuisances.
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
LC_ALL=C
export LC_ALL
LANGUAGE=C
export LANGUAGE
# CDPATH.
(unset CDPATH) >/dev/null 2>&1 && unset CDPATH
# as_fn_error STATUS ERROR [LINENO LOG_FD]
# ----------------------------------------
# Output "`basename $0`: error: ERROR" to stderr. If LINENO and LOG_FD are
# provided, also output the error to LOG_FD, referencing LINENO. Then exit the
# script with STATUS, using 1 if that was 0.
as_fn_error ()
{
as_status=$1; test $as_status -eq 0 && as_status=1
if test "$4"; then
as_lineno=${as_lineno-"$3"} as_lineno_stack=as_lineno_stack=$as_lineno_stack
$as_echo "$as_me:${as_lineno-$LINENO}: error: $2" >&$4
From Andrew Church <andrew@users.sourceforge.net>: when testing for "pcap_version", "pcap_debug", and "yydebug", don't add our own functions referring to those variables - GCC 3.4.1 optimizes the test code out before the link is done, as it's in a function that's not called.
2004-08-27 15:17:03 +08:00
fi
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
$as_echo "$as_me: error: $2" >&2
as_fn_exit $as_status
} # as_fn_error
# as_fn_set_status STATUS
# -----------------------
# Set $? to STATUS, without forking.
as_fn_set_status ()
{
return $1
} # as_fn_set_status
# as_fn_exit STATUS
# -----------------
# Exit the shell with STATUS, even in a "trap 0" or "set -e" context.
as_fn_exit ()
{
set +e
as_fn_set_status $1
exit $1
} # as_fn_exit
# as_fn_unset VAR
# ---------------
# Portably unset VAR.
as_fn_unset ()
{
{ eval $1=; unset $1;}
}
as_unset=as_fn_unset
# as_fn_append VAR VALUE
# ----------------------
# Append the text in VALUE to the end of the definition contained in VAR. Take
# advantage of any shell optimizations that allow amortized linear growth over
# repeated appends, instead of the typical quadratic growth present in naive
# implementations.
if (eval "as_var=1; as_var+=2; test x\$as_var = x12") 2>/dev/null; then :
eval 'as_fn_append ()
{
eval $1+=\$2
}'
else
as_fn_append ()
{
eval $1=\$$1\$2
}
fi # as_fn_append
# as_fn_arith ARG...
# ------------------
# Perform arithmetic evaluation on the ARGs, and store the result in the
# global $as_val. Take advantage of shells that can avoid forks. The arguments
# must be portable across $(()) and expr.
if (eval "test \$(( 1 + 1 )) = 2") 2>/dev/null; then :
eval 'as_fn_arith ()
{
as_val=$(( $* ))
}'
else
as_fn_arith ()
{
as_val=`expr "$@" || test $? -eq 1`
}
fi # as_fn_arith
From Andrew Church <andrew@users.sourceforge.net>: when testing for "pcap_version", "pcap_debug", and "yydebug", don't add our own functions referring to those variables - GCC 3.4.1 optimizes the test code out before the link is done, as it's in a function that's not called.
2004-08-27 15:17:03 +08:00
We support building tcpdump with versions of libpcap other than the one with which it was released, and DLT_BLUETOOTH_HCI_H4_WITH_PHDR might be defined by pcap-bpf.h without pcap/bluetooth.h being present (as appears to be the case on Fedora 9, for example), so check whether <pcap/bluetooth.h> is usable. Update a comment - F9 appears to have a "/usr/include/pcap.h" if you install the libpcap headers. When adding -I flags when running a compiler-based test, add them to CPPFLAGS, not CFLAGS - the latter doesn't work right with AC_CHECK_HEADERS, as the "gcc -E" run doesn't have the -I flags added.
2008-09-26 05:45:50 +08:00
if expr a : '\(a\)' >/dev/null 2>&1 &&
test "X`expr 00001 : '.*\(...\)'`" = X001; then
From Andrew Church <andrew@users.sourceforge.net>: when testing for "pcap_version", "pcap_debug", and "yydebug", don't add our own functions referring to those variables - GCC 3.4.1 optimizes the test code out before the link is done, as it's in a function that's not called.
2004-08-27 15:17:03 +08:00
as_expr=expr
else
as_expr=false
fi
We support building tcpdump with versions of libpcap other than the one with which it was released, and DLT_BLUETOOTH_HCI_H4_WITH_PHDR might be defined by pcap-bpf.h without pcap/bluetooth.h being present (as appears to be the case on Fedora 9, for example), so check whether <pcap/bluetooth.h> is usable. Update a comment - F9 appears to have a "/usr/include/pcap.h" if you install the libpcap headers. When adding -I flags when running a compiler-based test, add them to CPPFLAGS, not CFLAGS - the latter doesn't work right with AC_CHECK_HEADERS, as the "gcc -E" run doesn't have the -I flags added.
2008-09-26 05:45:50 +08:00
if (basename -- /) >/dev/null 2>&1 && test "X`basename -- / 2>&1`" = "X/"; then
From Andrew Church <andrew@users.sourceforge.net>: when testing for "pcap_version", "pcap_debug", and "yydebug", don't add our own functions referring to those variables - GCC 3.4.1 optimizes the test code out before the link is done, as it's in a function that's not called.
2004-08-27 15:17:03 +08:00
as_basename=basename
else
as_basename=false
fi
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
if (as_dir=`dirname -- /` && test "X$as_dir" = X/) >/dev/null 2>&1; then
as_dirname=dirname
else
as_dirname=false
fi
From Andrew Church <andrew@users.sourceforge.net>: when testing for "pcap_version", "pcap_debug", and "yydebug", don't add our own functions referring to those variables - GCC 3.4.1 optimizes the test code out before the link is done, as it's in a function that's not called.
2004-08-27 15:17:03 +08:00
We support building tcpdump with versions of libpcap other than the one with which it was released, and DLT_BLUETOOTH_HCI_H4_WITH_PHDR might be defined by pcap-bpf.h without pcap/bluetooth.h being present (as appears to be the case on Fedora 9, for example), so check whether <pcap/bluetooth.h> is usable. Update a comment - F9 appears to have a "/usr/include/pcap.h" if you install the libpcap headers. When adding -I flags when running a compiler-based test, add them to CPPFLAGS, not CFLAGS - the latter doesn't work right with AC_CHECK_HEADERS, as the "gcc -E" run doesn't have the -I flags added.
2008-09-26 05:45:50 +08:00
as_me=`$as_basename -- "$0" ||
From Andrew Church <andrew@users.sourceforge.net>: when testing for "pcap_version", "pcap_debug", and "yydebug", don't add our own functions referring to those variables - GCC 3.4.1 optimizes the test code out before the link is done, as it's in a function that's not called.
2004-08-27 15:17:03 +08:00
$as_expr X/"$0" : '.*/\([^/][^/]*\)/*$' \| \
X"$0" : 'X\(//\)$' \| \
We support building tcpdump with versions of libpcap other than the one with which it was released, and DLT_BLUETOOTH_HCI_H4_WITH_PHDR might be defined by pcap-bpf.h without pcap/bluetooth.h being present (as appears to be the case on Fedora 9, for example), so check whether <pcap/bluetooth.h> is usable. Update a comment - F9 appears to have a "/usr/include/pcap.h" if you install the libpcap headers. When adding -I flags when running a compiler-based test, add them to CPPFLAGS, not CFLAGS - the latter doesn't work right with AC_CHECK_HEADERS, as the "gcc -E" run doesn't have the -I flags added.
2008-09-26 05:45:50 +08:00
X"$0" : 'X\(/\)' \| . 2>/dev/null ||
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
$as_echo X/"$0" |
We support building tcpdump with versions of libpcap other than the one with which it was released, and DLT_BLUETOOTH_HCI_H4_WITH_PHDR might be defined by pcap-bpf.h without pcap/bluetooth.h being present (as appears to be the case on Fedora 9, for example), so check whether <pcap/bluetooth.h> is usable. Update a comment - F9 appears to have a "/usr/include/pcap.h" if you install the libpcap headers. When adding -I flags when running a compiler-based test, add them to CPPFLAGS, not CFLAGS - the latter doesn't work right with AC_CHECK_HEADERS, as the "gcc -E" run doesn't have the -I flags added.
2008-09-26 05:45:50 +08:00
sed '/^.*\/\([^/][^/]*\)\/*$/{
s//\1/
q
}
/^X\/\(\/\/\)$/{
s//\1/
q
}
/^X\/\(\/\).*/{
s//\1/
q
}
s/.*/./; q'`
From Andrew Church <andrew@users.sourceforge.net>: when testing for "pcap_version", "pcap_debug", and "yydebug", don't add our own functions referring to those variables - GCC 3.4.1 optimizes the test code out before the link is done, as it's in a function that's not called.
2004-08-27 15:17:03 +08:00
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
# Avoid depending upon Character Ranges.
as_cr_letters='abcdefghijklmnopqrstuvwxyz'
as_cr_LETTERS='ABCDEFGHIJKLMNOPQRSTUVWXYZ'
as_cr_Letters=$as_cr_letters$as_cr_LETTERS
as_cr_digits='0123456789'
as_cr_alnum=$as_cr_Letters$as_cr_digits
We support building tcpdump with versions of libpcap other than the one with which it was released, and DLT_BLUETOOTH_HCI_H4_WITH_PHDR might be defined by pcap-bpf.h without pcap/bluetooth.h being present (as appears to be the case on Fedora 9, for example), so check whether <pcap/bluetooth.h> is usable. Update a comment - F9 appears to have a "/usr/include/pcap.h" if you install the libpcap headers. When adding -I flags when running a compiler-based test, add them to CPPFLAGS, not CFLAGS - the latter doesn't work right with AC_CHECK_HEADERS, as the "gcc -E" run doesn't have the -I flags added.
2008-09-26 05:45:50 +08:00
ECHO_C= ECHO_N= ECHO_T=
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
case `echo -n x` in #(((((
We support building tcpdump with versions of libpcap other than the one with which it was released, and DLT_BLUETOOTH_HCI_H4_WITH_PHDR might be defined by pcap-bpf.h without pcap/bluetooth.h being present (as appears to be the case on Fedora 9, for example), so check whether <pcap/bluetooth.h> is usable. Update a comment - F9 appears to have a "/usr/include/pcap.h" if you install the libpcap headers. When adding -I flags when running a compiler-based test, add them to CPPFLAGS, not CFLAGS - the latter doesn't work right with AC_CHECK_HEADERS, as the "gcc -E" run doesn't have the -I flags added.
2008-09-26 05:45:50 +08:00
-n*)
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
case `echo 'xy\c'` in
We support building tcpdump with versions of libpcap other than the one with which it was released, and DLT_BLUETOOTH_HCI_H4_WITH_PHDR might be defined by pcap-bpf.h without pcap/bluetooth.h being present (as appears to be the case on Fedora 9, for example), so check whether <pcap/bluetooth.h> is usable. Update a comment - F9 appears to have a "/usr/include/pcap.h" if you install the libpcap headers. When adding -I flags when running a compiler-based test, add them to CPPFLAGS, not CFLAGS - the latter doesn't work right with AC_CHECK_HEADERS, as the "gcc -E" run doesn't have the -I flags added.
2008-09-26 05:45:50 +08:00
*c*) ECHO_T=' ';; # ECHO_T is single tab character.
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
xy) ECHO_C='\c';;
*) echo `echo ksh88 bug on AIX 6.1` > /dev/null
ECHO_T=' ';;
We support building tcpdump with versions of libpcap other than the one with which it was released, and DLT_BLUETOOTH_HCI_H4_WITH_PHDR might be defined by pcap-bpf.h without pcap/bluetooth.h being present (as appears to be the case on Fedora 9, for example), so check whether <pcap/bluetooth.h> is usable. Update a comment - F9 appears to have a "/usr/include/pcap.h" if you install the libpcap headers. When adding -I flags when running a compiler-based test, add them to CPPFLAGS, not CFLAGS - the latter doesn't work right with AC_CHECK_HEADERS, as the "gcc -E" run doesn't have the -I flags added.
2008-09-26 05:45:50 +08:00
esac;;
*)
ECHO_N='-n';;
From Andrew Church <andrew@users.sourceforge.net>: when testing for "pcap_version", "pcap_debug", and "yydebug", don't add our own functions referring to those variables - GCC 3.4.1 optimizes the test code out before the link is done, as it's in a function that's not called.
2004-08-27 15:17:03 +08:00
esac
Regenerate with autoconf 2.57.
2004-01-14 11:15:08 +08:00
rm -f conf$$ conf$$.exe conf$$.file
We support building tcpdump with versions of libpcap other than the one with which it was released, and DLT_BLUETOOTH_HCI_H4_WITH_PHDR might be defined by pcap-bpf.h without pcap/bluetooth.h being present (as appears to be the case on Fedora 9, for example), so check whether <pcap/bluetooth.h> is usable. Update a comment - F9 appears to have a "/usr/include/pcap.h" if you install the libpcap headers. When adding -I flags when running a compiler-based test, add them to CPPFLAGS, not CFLAGS - the latter doesn't work right with AC_CHECK_HEADERS, as the "gcc -E" run doesn't have the -I flags added.
2008-09-26 05:45:50 +08:00
if test -d conf$$.dir; then
rm -f conf$$.dir/conf$$.file
else
rm -f conf$$.dir
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
mkdir conf$$.dir 2>/dev/null
fi
if (echo >conf$$.file) 2>/dev/null; then
if ln -s conf$$.file conf$$ 2>/dev/null; then
as_ln_s='ln -s'
# ... but there are two gotchas:
# 1) On MSYS, both `ln -s file dir' and `ln file dir' fail.
# 2) DJGPP < 2.04 has no symlinks; `ln -s' creates a wrapper executable.
# In both cases, we have to default to `cp -pR'.
ln -s conf$$.file conf$$.dir 2>/dev/null && test ! -f conf$$.exe ||
as_ln_s='cp -pR'
elif ln conf$$.file conf$$ 2>/dev/null; then
as_ln_s=ln
else
as_ln_s='cp -pR'
fi
else
as_ln_s='cp -pR'
Regenerate with autoconf 2.57.
2004-01-14 11:15:08 +08:00
fi
We support building tcpdump with versions of libpcap other than the one with which it was released, and DLT_BLUETOOTH_HCI_H4_WITH_PHDR might be defined by pcap-bpf.h without pcap/bluetooth.h being present (as appears to be the case on Fedora 9, for example), so check whether <pcap/bluetooth.h> is usable. Update a comment - F9 appears to have a "/usr/include/pcap.h" if you install the libpcap headers. When adding -I flags when running a compiler-based test, add them to CPPFLAGS, not CFLAGS - the latter doesn't work right with AC_CHECK_HEADERS, as the "gcc -E" run doesn't have the -I flags added.
2008-09-26 05:45:50 +08:00
rm -f conf$$ conf$$.exe conf$$.dir/conf$$.file conf$$.file
rmdir conf$$.dir 2>/dev/null
Regenerate with autoconf 2.57.
2004-01-14 11:15:08 +08:00
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
# as_fn_mkdir_p
# -------------
# Create "$as_dir" as a directory, including parents if necessary.
as_fn_mkdir_p ()
{
case $as_dir in #(
-*) as_dir=./$as_dir;;
esac
test -d "$as_dir" || eval $as_mkdir_p || {
as_dirs=
while :; do
case $as_dir in #(
*\'*) as_qdir=`$as_echo "$as_dir" | sed "s/'/'\\\\\\\\''/g"`;; #'(
*) as_qdir=$as_dir;;
esac
as_dirs="'$as_qdir' $as_dirs"
as_dir=`$as_dirname -- "$as_dir" ||
$as_expr X"$as_dir" : 'X\(.*[^/]\)//*[^/][^/]*/*$' \| \
X"$as_dir" : 'X\(//\)[^/]' \| \
X"$as_dir" : 'X\(//\)$' \| \
X"$as_dir" : 'X\(/\)' \| . 2>/dev/null ||
$as_echo X"$as_dir" |
sed '/^X\(.*[^/]\)\/\/*[^/][^/]*\/*$/{
s//\1/
q
}
/^X\(\/\/\)[^/].*/{
s//\1/
q
}
/^X\(\/\/\)$/{
s//\1/
q
}
/^X\(\/\).*/{
s//\1/
q
}
s/.*/./; q'`
test -d "$as_dir" && break
done
test -z "$as_dirs" || eval "mkdir $as_dirs"
} || test -d "$as_dir" || as_fn_error $? "cannot create directory $as_dir"
} # as_fn_mkdir_p
From Andrew Church <andrew@users.sourceforge.net>: when testing for "pcap_version", "pcap_debug", and "yydebug", don't add our own functions referring to those variables - GCC 3.4.1 optimizes the test code out before the link is done, as it's in a function that's not called.
2004-08-27 15:17:03 +08:00
if mkdir -p . 2>/dev/null; then
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
as_mkdir_p='mkdir -p "$as_dir"'
First stage of adding support for 64-bit integral data types - this causes "int64_t" and "u_int64_t" to be defined by the configure script, and causes "missing/bittypes.h" to attempt to define "u_int64_t" in a fashion that should, with any luck, work on MSVC++ and various flavors of GNU C on Windows.
2004-04-17 12:33:16 +08:00
else
Add -Wpointer-arith to the list of warnings we enable with GCC.
2005-11-08 10:59:40 +08:00
test -d ./-p && rmdir ./-p
From Andrew Church <andrew@users.sourceforge.net>: when testing for "pcap_version", "pcap_debug", and "yydebug", don't add our own functions referring to those variables - GCC 3.4.1 optimizes the test code out before the link is done, as it's in a function that's not called.
2004-08-27 15:17:03 +08:00
as_mkdir_p=false
First stage of adding support for 64-bit integral data types - this causes "int64_t" and "u_int64_t" to be defined by the configure script, and causes "missing/bittypes.h" to attempt to define "u_int64_t" in a fashion that should, with any luck, work on MSVC++ and various flavors of GNU C on Windows.
2004-04-17 12:33:16 +08:00
fi
Regenerate with autoconf 2.57.
2004-01-14 11:15:08 +08:00
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
# as_fn_executable_p FILE
# -----------------------
# Test if FILE is an executable regular file.
as_fn_executable_p ()
{
test -f "$1" && test -x "$1"
} # as_fn_executable_p
as_test_x='test -x'
as_executable_p=as_fn_executable_p
From Andrew Church <andrew@users.sourceforge.net>: when testing for "pcap_version", "pcap_debug", and "yydebug", don't add our own functions referring to those variables - GCC 3.4.1 optimizes the test code out before the link is done, as it's in a function that's not called.
2004-08-27 15:17:03 +08:00
# Sed expression to map a string onto a valid CPP name.
Add -Wpointer-arith to the list of warnings we enable with GCC.
2005-11-08 10:59:40 +08:00
as_tr_cpp="eval sed 'y%*$as_cr_letters%P$as_cr_LETTERS%;s%[^_$as_cr_alnum]%_%g'"
From Andrew Church <andrew@users.sourceforge.net>: when testing for "pcap_version", "pcap_debug", and "yydebug", don't add our own functions referring to those variables - GCC 3.4.1 optimizes the test code out before the link is done, as it's in a function that's not called.
2004-08-27 15:17:03 +08:00
# Sed expression to map a string onto a valid variable name.
Add -Wpointer-arith to the list of warnings we enable with GCC.
2005-11-08 10:59:40 +08:00
as_tr_sh="eval sed 'y%*+%pp%;s%[^_$as_cr_alnum]%_%g'"
From Andrew Church <andrew@users.sourceforge.net>: when testing for "pcap_version", "pcap_debug", and "yydebug", don't add our own functions referring to those variables - GCC 3.4.1 optimizes the test code out before the link is done, as it's in a function that's not called.
2004-08-27 15:17:03 +08:00
Regenerate with autoconf 2.57.
2004-01-14 11:15:08 +08:00
exec 6>&1
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
## ----------------------------------- ##
## Main body of $CONFIG_STATUS script. ##
## ----------------------------------- ##
_ASEOF
test $as_write_fail = 0 && chmod +x $CONFIG_STATUS || ac_write_fail=1
Regenerate with autoconf 2.57.
2004-01-14 11:15:08 +08:00
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
cat >>$CONFIG_STATUS <<\_ACEOF || ac_write_fail=1
# Save the log message, to keep $0 and so on meaningful, and to
From Andrew Church <andrew@users.sourceforge.net>: when testing for "pcap_version", "pcap_debug", and "yydebug", don't add our own functions referring to those variables - GCC 3.4.1 optimizes the test code out before the link is done, as it's in a function that's not called.
2004-08-27 15:17:03 +08:00
# report actual input values of CONFIG_FILES etc. instead of their
We support building tcpdump with versions of libpcap other than the one with which it was released, and DLT_BLUETOOTH_HCI_H4_WITH_PHDR might be defined by pcap-bpf.h without pcap/bluetooth.h being present (as appears to be the case on Fedora 9, for example), so check whether <pcap/bluetooth.h> is usable. Update a comment - F9 appears to have a "/usr/include/pcap.h" if you install the libpcap headers. When adding -I flags when running a compiler-based test, add them to CPPFLAGS, not CFLAGS - the latter doesn't work right with AC_CHECK_HEADERS, as the "gcc -E" run doesn't have the -I flags added.
2008-09-26 05:45:50 +08:00
# values after options handling.
ac_log="
Do the version number the way it's now done for libpcap. Use the two-argument version of AC_INIT() - which requires autoconf 2.64 or later, so require that as a minimum - and get the version string from the VERSION file. Use AC_CONFIG_SRCDIR() to say that the source directory needs tcpdump.c; the two-argument version of AC_INIT() doesn't do that. This means that we no longer have a version.c file.
2017-10-17 05:31:14 +08:00
This file was extended by tcpdump $as_me 4.10.0-PRE-GIT, which was
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
generated by GNU Autoconf 2.69. Invocation command line was
From Andrew Church <andrew@users.sourceforge.net>: when testing for "pcap_version", "pcap_debug", and "yydebug", don't add our own functions referring to those variables - GCC 3.4.1 optimizes the test code out before the link is done, as it's in a function that's not called.
2004-08-27 15:17:03 +08:00
CONFIG_FILES = $CONFIG_FILES
CONFIG_HEADERS = $CONFIG_HEADERS
CONFIG_LINKS = $CONFIG_LINKS
CONFIG_COMMANDS = $CONFIG_COMMANDS
$ $0 $@
We support building tcpdump with versions of libpcap other than the one with which it was released, and DLT_BLUETOOTH_HCI_H4_WITH_PHDR might be defined by pcap-bpf.h without pcap/bluetooth.h being present (as appears to be the case on Fedora 9, for example), so check whether <pcap/bluetooth.h> is usable. Update a comment - F9 appears to have a "/usr/include/pcap.h" if you install the libpcap headers. When adding -I flags when running a compiler-based test, add them to CPPFLAGS, not CFLAGS - the latter doesn't work right with AC_CHECK_HEADERS, as the "gcc -E" run doesn't have the -I flags added.
2008-09-26 05:45:50 +08:00
on `(hostname || uname -n) 2>/dev/null | sed 1q`
"
Regenerate with autoconf 2.57.
2004-01-14 11:15:08 +08:00
_ACEOF
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
case $ac_config_files in *"
"*) set x $ac_config_files; shift; ac_config_files=$*;;
esac
case $ac_config_headers in *"
"*) set x $ac_config_headers; shift; ac_config_headers=$*;;
esac
cat >>$CONFIG_STATUS <<_ACEOF || ac_write_fail=1
Regenerate with autoconf 2.57.
2004-01-14 11:15:08 +08:00
# Files that config.status was made for.
We support building tcpdump with versions of libpcap other than the one with which it was released, and DLT_BLUETOOTH_HCI_H4_WITH_PHDR might be defined by pcap-bpf.h without pcap/bluetooth.h being present (as appears to be the case on Fedora 9, for example), so check whether <pcap/bluetooth.h> is usable. Update a comment - F9 appears to have a "/usr/include/pcap.h" if you install the libpcap headers. When adding -I flags when running a compiler-based test, add them to CPPFLAGS, not CFLAGS - the latter doesn't work right with AC_CHECK_HEADERS, as the "gcc -E" run doesn't have the -I flags added.
2008-09-26 05:45:50 +08:00
config_files="$ac_config_files"
config_headers="$ac_config_headers"
config_commands="$ac_config_commands"
Run ranlib on libnetdissect.a if necessary. Remove it before building it, so we discard any stuff already in the archive.
2008-02-05 04:42:09 +08:00
We support building tcpdump with versions of libpcap other than the one with which it was released, and DLT_BLUETOOTH_HCI_H4_WITH_PHDR might be defined by pcap-bpf.h without pcap/bluetooth.h being present (as appears to be the case on Fedora 9, for example), so check whether <pcap/bluetooth.h> is usable. Update a comment - F9 appears to have a "/usr/include/pcap.h" if you install the libpcap headers. When adding -I flags when running a compiler-based test, add them to CPPFLAGS, not CFLAGS - the latter doesn't work right with AC_CHECK_HEADERS, as the "gcc -E" run doesn't have the -I flags added.
2008-09-26 05:45:50 +08:00
_ACEOF
Regenerate with autoconf 2.57.
2004-01-14 11:15:08 +08:00
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
cat >>$CONFIG_STATUS <<\_ACEOF || ac_write_fail=1
Regenerate with autoconf 2.57.
2004-01-14 11:15:08 +08:00
ac_cs_usage="\
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
\`$as_me' instantiates files and other configuration actions
from templates according to the current configuration. Unless the files
and actions are specified as TAGs, all are instantiated by default.
Regenerate with autoconf 2.57.
2004-01-14 11:15:08 +08:00
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
Usage: $0 [OPTION]... [TAG]...
Regenerate with autoconf 2.57.
2004-01-14 11:15:08 +08:00
-h, --help print this help, then exit
We support building tcpdump with versions of libpcap other than the one with which it was released, and DLT_BLUETOOTH_HCI_H4_WITH_PHDR might be defined by pcap-bpf.h without pcap/bluetooth.h being present (as appears to be the case on Fedora 9, for example), so check whether <pcap/bluetooth.h> is usable. Update a comment - F9 appears to have a "/usr/include/pcap.h" if you install the libpcap headers. When adding -I flags when running a compiler-based test, add them to CPPFLAGS, not CFLAGS - the latter doesn't work right with AC_CHECK_HEADERS, as the "gcc -E" run doesn't have the -I flags added.
2008-09-26 05:45:50 +08:00
-V, --version print version number and configuration settings, then exit
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
--config print configuration, then exit
-q, --quiet, --silent
do not print progress messages
Regenerate with autoconf 2.57.
2004-01-14 11:15:08 +08:00
-d, --debug don't remove temporary files
--recheck update $as_me by reconfiguring in the same conditions
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
--file=FILE[:TEMPLATE]
instantiate the configuration file FILE
--header=FILE[:TEMPLATE]
instantiate the configuration header FILE
Regenerate with autoconf 2.57.
2004-01-14 11:15:08 +08:00
Configuration files:
$config_files
Configuration headers:
$config_headers
Configuration commands:
$config_commands
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
Report bugs to the package provider."
Run ranlib on libnetdissect.a if necessary. Remove it before building it, so we discard any stuff already in the archive.
2008-02-05 04:42:09 +08:00
We support building tcpdump with versions of libpcap other than the one with which it was released, and DLT_BLUETOOTH_HCI_H4_WITH_PHDR might be defined by pcap-bpf.h without pcap/bluetooth.h being present (as appears to be the case on Fedora 9, for example), so check whether <pcap/bluetooth.h> is usable. Update a comment - F9 appears to have a "/usr/include/pcap.h" if you install the libpcap headers. When adding -I flags when running a compiler-based test, add them to CPPFLAGS, not CFLAGS - the latter doesn't work right with AC_CHECK_HEADERS, as the "gcc -E" run doesn't have the -I flags added.
2008-09-26 05:45:50 +08:00
_ACEOF
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
cat >>$CONFIG_STATUS <<_ACEOF || ac_write_fail=1
ac_cs_config="`$as_echo "$ac_configure_args" | sed 's/^ //; s/[\\""\`\$]/\\\\&/g'`"
Regenerate with autoconf 2.57.
2004-01-14 11:15:08 +08:00
ac_cs_version="\\
Do the version number the way it's now done for libpcap. Use the two-argument version of AC_INIT() - which requires autoconf 2.64 or later, so require that as a minimum - and get the version string from the VERSION file. Use AC_CONFIG_SRCDIR() to say that the source directory needs tcpdump.c; the two-argument version of AC_INIT() doesn't do that. This means that we no longer have a version.c file.
2017-10-17 05:31:14 +08:00
tcpdump config.status 4.10.0-PRE-GIT
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
configured by $0, generated by GNU Autoconf 2.69,
with options \\"\$ac_cs_config\\"
Regenerate with autoconf 2.57.
2004-01-14 11:15:08 +08:00
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
Copyright (C) 2012 Free Software Foundation, Inc.
Regenerate with autoconf 2.57.
2004-01-14 11:15:08 +08:00
This config.status script is free software; the Free Software Foundation
gives unlimited permission to copy, distribute and modify it."
We support building tcpdump with versions of libpcap other than the one with which it was released, and DLT_BLUETOOTH_HCI_H4_WITH_PHDR might be defined by pcap-bpf.h without pcap/bluetooth.h being present (as appears to be the case on Fedora 9, for example), so check whether <pcap/bluetooth.h> is usable. Update a comment - F9 appears to have a "/usr/include/pcap.h" if you install the libpcap headers. When adding -I flags when running a compiler-based test, add them to CPPFLAGS, not CFLAGS - the latter doesn't work right with AC_CHECK_HEADERS, as the "gcc -E" run doesn't have the -I flags added.
2008-09-26 05:45:50 +08:00
ac_pwd='$ac_pwd'
srcdir='$srcdir'
INSTALL='$INSTALL'
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
test -n "\$AWK" || AWK=awk
From Andrew Church <andrew@users.sourceforge.net>: when testing for "pcap_version", "pcap_debug", and "yydebug", don't add our own functions referring to those variables - GCC 3.4.1 optimizes the test code out before the link is done, as it's in a function that's not called.
2004-08-27 15:17:03 +08:00
_ACEOF
Regenerate with autoconf 2.57.
2004-01-14 11:15:08 +08:00
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
cat >>$CONFIG_STATUS <<\_ACEOF || ac_write_fail=1
# The default lists apply if the user does not specify any file.
Regenerate with autoconf 2.57.
2004-01-14 11:15:08 +08:00
ac_need_defaults=:
while test $# != 0
do
case $1 in
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
--*=?*)
We support building tcpdump with versions of libpcap other than the one with which it was released, and DLT_BLUETOOTH_HCI_H4_WITH_PHDR might be defined by pcap-bpf.h without pcap/bluetooth.h being present (as appears to be the case on Fedora 9, for example), so check whether <pcap/bluetooth.h> is usable. Update a comment - F9 appears to have a "/usr/include/pcap.h" if you install the libpcap headers. When adding -I flags when running a compiler-based test, add them to CPPFLAGS, not CFLAGS - the latter doesn't work right with AC_CHECK_HEADERS, as the "gcc -E" run doesn't have the -I flags added.
2008-09-26 05:45:50 +08:00
ac_option=`expr "X$1" : 'X\([^=]*\)='`
ac_optarg=`expr "X$1" : 'X[^=]*=\(.*\)'`
From Andrew Church <andrew@users.sourceforge.net>: when testing for "pcap_version", "pcap_debug", and "yydebug", don't add our own functions referring to those variables - GCC 3.4.1 optimizes the test code out before the link is done, as it's in a function that's not called.
2004-08-27 15:17:03 +08:00
ac_shift=:
;;
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
--*=)
ac_option=`expr "X$1" : 'X\([^=]*\)='`
ac_optarg=
ac_shift=:
;;
We support building tcpdump with versions of libpcap other than the one with which it was released, and DLT_BLUETOOTH_HCI_H4_WITH_PHDR might be defined by pcap-bpf.h without pcap/bluetooth.h being present (as appears to be the case on Fedora 9, for example), so check whether <pcap/bluetooth.h> is usable. Update a comment - F9 appears to have a "/usr/include/pcap.h" if you install the libpcap headers. When adding -I flags when running a compiler-based test, add them to CPPFLAGS, not CFLAGS - the latter doesn't work right with AC_CHECK_HEADERS, as the "gcc -E" run doesn't have the -I flags added.
2008-09-26 05:45:50 +08:00
*)
From Andrew Church <andrew@users.sourceforge.net>: when testing for "pcap_version", "pcap_debug", and "yydebug", don't add our own functions referring to those variables - GCC 3.4.1 optimizes the test code out before the link is done, as it's in a function that's not called.
2004-08-27 15:17:03 +08:00
ac_option=$1
ac_optarg=$2
ac_shift=shift
Regenerate with autoconf 2.57.
2004-01-14 11:15:08 +08:00
;;
esac
From Andrew Church <andrew@users.sourceforge.net>: when testing for "pcap_version", "pcap_debug", and "yydebug", don't add our own functions referring to those variables - GCC 3.4.1 optimizes the test code out before the link is done, as it's in a function that's not called.
2004-08-27 15:17:03 +08:00
case $ac_option in
Regenerate with autoconf 2.57.
2004-01-14 11:15:08 +08:00
# Handling of the options.
-recheck | --recheck | --rechec | --reche | --rech | --rec | --re | --r)
From Andrew Church <andrew@users.sourceforge.net>: when testing for "pcap_version", "pcap_debug", and "yydebug", don't add our own functions referring to those variables - GCC 3.4.1 optimizes the test code out before the link is done, as it's in a function that's not called.
2004-08-27 15:17:03 +08:00
ac_cs_recheck=: ;;
We support building tcpdump with versions of libpcap other than the one with which it was released, and DLT_BLUETOOTH_HCI_H4_WITH_PHDR might be defined by pcap-bpf.h without pcap/bluetooth.h being present (as appears to be the case on Fedora 9, for example), so check whether <pcap/bluetooth.h> is usable. Update a comment - F9 appears to have a "/usr/include/pcap.h" if you install the libpcap headers. When adding -I flags when running a compiler-based test, add them to CPPFLAGS, not CFLAGS - the latter doesn't work right with AC_CHECK_HEADERS, as the "gcc -E" run doesn't have the -I flags added.
2008-09-26 05:45:50 +08:00
--version | --versio | --versi | --vers | --ver | --ve | --v | -V )
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
$as_echo "$ac_cs_version"; exit ;;
--config | --confi | --conf | --con | --co | --c )
$as_echo "$ac_cs_config"; exit ;;
We support building tcpdump with versions of libpcap other than the one with which it was released, and DLT_BLUETOOTH_HCI_H4_WITH_PHDR might be defined by pcap-bpf.h without pcap/bluetooth.h being present (as appears to be the case on Fedora 9, for example), so check whether <pcap/bluetooth.h> is usable. Update a comment - F9 appears to have a "/usr/include/pcap.h" if you install the libpcap headers. When adding -I flags when running a compiler-based test, add them to CPPFLAGS, not CFLAGS - the latter doesn't work right with AC_CHECK_HEADERS, as the "gcc -E" run doesn't have the -I flags added.
2008-09-26 05:45:50 +08:00
--debug | --debu | --deb | --de | --d | -d )
Regenerate with autoconf 2.57.
2004-01-14 11:15:08 +08:00
debug=: ;;
--file | --fil | --fi | --f )
From Andrew Church <andrew@users.sourceforge.net>: when testing for "pcap_version", "pcap_debug", and "yydebug", don't add our own functions referring to those variables - GCC 3.4.1 optimizes the test code out before the link is done, as it's in a function that's not called.
2004-08-27 15:17:03 +08:00
$ac_shift
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
case $ac_optarg in
*\'*) ac_optarg=`$as_echo "$ac_optarg" | sed "s/'/'\\\\\\\\''/g"` ;;
'') as_fn_error $? "missing file argument" ;;
esac
as_fn_append CONFIG_FILES " '$ac_optarg'"
Regenerate with autoconf 2.57.
2004-01-14 11:15:08 +08:00
ac_need_defaults=false;;
--header | --heade | --head | --hea )
From Andrew Church <andrew@users.sourceforge.net>: when testing for "pcap_version", "pcap_debug", and "yydebug", don't add our own functions referring to those variables - GCC 3.4.1 optimizes the test code out before the link is done, as it's in a function that's not called.
2004-08-27 15:17:03 +08:00
$ac_shift
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
case $ac_optarg in
*\'*) ac_optarg=`$as_echo "$ac_optarg" | sed "s/'/'\\\\\\\\''/g"` ;;
esac
as_fn_append CONFIG_HEADERS " '$ac_optarg'"
Regenerate with autoconf 2.57.
2004-01-14 11:15:08 +08:00
ac_need_defaults=false;;
We support building tcpdump with versions of libpcap other than the one with which it was released, and DLT_BLUETOOTH_HCI_H4_WITH_PHDR might be defined by pcap-bpf.h without pcap/bluetooth.h being present (as appears to be the case on Fedora 9, for example), so check whether <pcap/bluetooth.h> is usable. Update a comment - F9 appears to have a "/usr/include/pcap.h" if you install the libpcap headers. When adding -I flags when running a compiler-based test, add them to CPPFLAGS, not CFLAGS - the latter doesn't work right with AC_CHECK_HEADERS, as the "gcc -E" run doesn't have the -I flags added.
2008-09-26 05:45:50 +08:00
--he | --h)
# Conflict between --help and --header
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
as_fn_error $? "ambiguous option: \`$1'
Try \`$0 --help' for more information.";;
We support building tcpdump with versions of libpcap other than the one with which it was released, and DLT_BLUETOOTH_HCI_H4_WITH_PHDR might be defined by pcap-bpf.h without pcap/bluetooth.h being present (as appears to be the case on Fedora 9, for example), so check whether <pcap/bluetooth.h> is usable. Update a comment - F9 appears to have a "/usr/include/pcap.h" if you install the libpcap headers. When adding -I flags when running a compiler-based test, add them to CPPFLAGS, not CFLAGS - the latter doesn't work right with AC_CHECK_HEADERS, as the "gcc -E" run doesn't have the -I flags added.
2008-09-26 05:45:50 +08:00
--help | --hel | -h )
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
$as_echo "$ac_cs_usage"; exit ;;
From Andrew Church <andrew@users.sourceforge.net>: when testing for "pcap_version", "pcap_debug", and "yydebug", don't add our own functions referring to those variables - GCC 3.4.1 optimizes the test code out before the link is done, as it's in a function that's not called.
2004-08-27 15:17:03 +08:00
-q | -quiet | --quiet | --quie | --qui | --qu | --q \
| -silent | --silent | --silen | --sile | --sil | --si | --s)
ac_cs_silent=: ;;
Regenerate with autoconf 2.57.
2004-01-14 11:15:08 +08:00
# This is an error.
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
-*) as_fn_error $? "unrecognized option: \`$1'
Try \`$0 --help' for more information." ;;
Regenerate with autoconf 2.57.
2004-01-14 11:15:08 +08:00
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
*) as_fn_append ac_config_targets " $1"
We support building tcpdump with versions of libpcap other than the one with which it was released, and DLT_BLUETOOTH_HCI_H4_WITH_PHDR might be defined by pcap-bpf.h without pcap/bluetooth.h being present (as appears to be the case on Fedora 9, for example), so check whether <pcap/bluetooth.h> is usable. Update a comment - F9 appears to have a "/usr/include/pcap.h" if you install the libpcap headers. When adding -I flags when running a compiler-based test, add them to CPPFLAGS, not CFLAGS - the latter doesn't work right with AC_CHECK_HEADERS, as the "gcc -E" run doesn't have the -I flags added.
2008-09-26 05:45:50 +08:00
ac_need_defaults=false ;;
Regenerate with autoconf 2.57.
2004-01-14 11:15:08 +08:00
esac
shift
Initial revision
1999-10-08 07:47:09 +08:00
done
Regenerate with autoconf 2.57.
2004-01-14 11:15:08 +08:00
From Andrew Church <andrew@users.sourceforge.net>: when testing for "pcap_version", "pcap_debug", and "yydebug", don't add our own functions referring to those variables - GCC 3.4.1 optimizes the test code out before the link is done, as it's in a function that's not called.
2004-08-27 15:17:03 +08:00
ac_configure_extra_args=
Regenerate with autoconf 2.57.
2004-01-14 11:15:08 +08:00
From Andrew Church <andrew@users.sourceforge.net>: when testing for "pcap_version", "pcap_debug", and "yydebug", don't add our own functions referring to those variables - GCC 3.4.1 optimizes the test code out before the link is done, as it's in a function that's not called.
2004-08-27 15:17:03 +08:00
if $ac_cs_silent; then
exec 6>/dev/null
ac_configure_extra_args="$ac_configure_extra_args --silent"
fi
Initial revision
1999-10-08 07:47:09 +08:00
From Andrew Church <andrew@users.sourceforge.net>: when testing for "pcap_version", "pcap_debug", and "yydebug", don't add our own functions referring to those variables - GCC 3.4.1 optimizes the test code out before the link is done, as it's in a function that's not called.
2004-08-27 15:17:03 +08:00
_ACEOF
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
cat >>$CONFIG_STATUS <<_ACEOF || ac_write_fail=1
From Andrew Church <andrew@users.sourceforge.net>: when testing for "pcap_version", "pcap_debug", and "yydebug", don't add our own functions referring to those variables - GCC 3.4.1 optimizes the test code out before the link is done, as it's in a function that's not called.
2004-08-27 15:17:03 +08:00
if \$ac_cs_recheck; then
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
set X $SHELL '$0' $ac_configure_args \$ac_configure_extra_args --no-create --no-recursion
shift
\$as_echo "running CONFIG_SHELL=$SHELL \$*" >&6
CONFIG_SHELL='$SHELL'
We support building tcpdump with versions of libpcap other than the one with which it was released, and DLT_BLUETOOTH_HCI_H4_WITH_PHDR might be defined by pcap-bpf.h without pcap/bluetooth.h being present (as appears to be the case on Fedora 9, for example), so check whether <pcap/bluetooth.h> is usable. Update a comment - F9 appears to have a "/usr/include/pcap.h" if you install the libpcap headers. When adding -I flags when running a compiler-based test, add them to CPPFLAGS, not CFLAGS - the latter doesn't work right with AC_CHECK_HEADERS, as the "gcc -E" run doesn't have the -I flags added.
2008-09-26 05:45:50 +08:00
export CONFIG_SHELL
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
exec "\$@"
From Andrew Church <andrew@users.sourceforge.net>: when testing for "pcap_version", "pcap_debug", and "yydebug", don't add our own functions referring to those variables - GCC 3.4.1 optimizes the test code out before the link is done, as it's in a function that's not called.
2004-08-27 15:17:03 +08:00
fi
Initial revision
1999-10-08 07:47:09 +08:00
Regenerate with autoconf 2.57.
2004-01-14 11:15:08 +08:00
_ACEOF
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
cat >>$CONFIG_STATUS <<\_ACEOF || ac_write_fail=1
We support building tcpdump with versions of libpcap other than the one with which it was released, and DLT_BLUETOOTH_HCI_H4_WITH_PHDR might be defined by pcap-bpf.h without pcap/bluetooth.h being present (as appears to be the case on Fedora 9, for example), so check whether <pcap/bluetooth.h> is usable. Update a comment - F9 appears to have a "/usr/include/pcap.h" if you install the libpcap headers. When adding -I flags when running a compiler-based test, add them to CPPFLAGS, not CFLAGS - the latter doesn't work right with AC_CHECK_HEADERS, as the "gcc -E" run doesn't have the -I flags added.
2008-09-26 05:45:50 +08:00
exec 5>>config.log
{
echo
sed 'h;s/./-/g;s/^.../## /;s/...$/ ##/;p;x;p;x' <<_ASBOX
## Running $as_me. ##
_ASBOX
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
$as_echo "$ac_log"
We support building tcpdump with versions of libpcap other than the one with which it was released, and DLT_BLUETOOTH_HCI_H4_WITH_PHDR might be defined by pcap-bpf.h without pcap/bluetooth.h being present (as appears to be the case on Fedora 9, for example), so check whether <pcap/bluetooth.h> is usable. Update a comment - F9 appears to have a "/usr/include/pcap.h" if you install the libpcap headers. When adding -I flags when running a compiler-based test, add them to CPPFLAGS, not CFLAGS - the latter doesn't work right with AC_CHECK_HEADERS, as the "gcc -E" run doesn't have the -I flags added.
2008-09-26 05:45:50 +08:00
} >&5
Regenerate with autoconf 2.57.
2004-01-14 11:15:08 +08:00
We support building tcpdump with versions of libpcap other than the one with which it was released, and DLT_BLUETOOTH_HCI_H4_WITH_PHDR might be defined by pcap-bpf.h without pcap/bluetooth.h being present (as appears to be the case on Fedora 9, for example), so check whether <pcap/bluetooth.h> is usable. Update a comment - F9 appears to have a "/usr/include/pcap.h" if you install the libpcap headers. When adding -I flags when running a compiler-based test, add them to CPPFLAGS, not CFLAGS - the latter doesn't work right with AC_CHECK_HEADERS, as the "gcc -E" run doesn't have the -I flags added.
2008-09-26 05:45:50 +08:00
_ACEOF
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
cat >>$CONFIG_STATUS <<_ACEOF || ac_write_fail=1
Regenerate with autoconf 2.57.
2004-01-14 11:15:08 +08:00
#
We support building tcpdump with versions of libpcap other than the one with which it was released, and DLT_BLUETOOTH_HCI_H4_WITH_PHDR might be defined by pcap-bpf.h without pcap/bluetooth.h being present (as appears to be the case on Fedora 9, for example), so check whether <pcap/bluetooth.h> is usable. Update a comment - F9 appears to have a "/usr/include/pcap.h" if you install the libpcap headers. When adding -I flags when running a compiler-based test, add them to CPPFLAGS, not CFLAGS - the latter doesn't work right with AC_CHECK_HEADERS, as the "gcc -E" run doesn't have the -I flags added.
2008-09-26 05:45:50 +08:00
# INIT-COMMANDS
Regenerate with autoconf 2.57.
2004-01-14 11:15:08 +08:00
#
From Andrew Church <andrew@users.sourceforge.net>: when testing for "pcap_version", "pcap_debug", and "yydebug", don't add our own functions referring to those variables - GCC 3.4.1 optimizes the test code out before the link is done, as it's in a function that's not called.
2004-08-27 15:17:03 +08:00
_ACEOF
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
cat >>$CONFIG_STATUS <<\_ACEOF || ac_write_fail=1
We support building tcpdump with versions of libpcap other than the one with which it was released, and DLT_BLUETOOTH_HCI_H4_WITH_PHDR might be defined by pcap-bpf.h without pcap/bluetooth.h being present (as appears to be the case on Fedora 9, for example), so check whether <pcap/bluetooth.h> is usable. Update a comment - F9 appears to have a "/usr/include/pcap.h" if you install the libpcap headers. When adding -I flags when running a compiler-based test, add them to CPPFLAGS, not CFLAGS - the latter doesn't work right with AC_CHECK_HEADERS, as the "gcc -E" run doesn't have the -I flags added.
2008-09-26 05:45:50 +08:00
# Handling of arguments.
Regenerate with autoconf 2.57.
2004-01-14 11:15:08 +08:00
for ac_config_target in $ac_config_targets
do
We support building tcpdump with versions of libpcap other than the one with which it was released, and DLT_BLUETOOTH_HCI_H4_WITH_PHDR might be defined by pcap-bpf.h without pcap/bluetooth.h being present (as appears to be the case on Fedora 9, for example), so check whether <pcap/bluetooth.h> is usable. Update a comment - F9 appears to have a "/usr/include/pcap.h" if you install the libpcap headers. When adding -I flags when running a compiler-based test, add them to CPPFLAGS, not CFLAGS - the latter doesn't work right with AC_CHECK_HEADERS, as the "gcc -E" run doesn't have the -I flags added.
2008-09-26 05:45:50 +08:00
case $ac_config_target in
"config.h") CONFIG_HEADERS="$CONFIG_HEADERS config.h" ;;
"default-1") CONFIG_COMMANDS="$CONFIG_COMMANDS default-1" ;;
"Makefile") CONFIG_FILES="$CONFIG_FILES Makefile" ;;
Run the tcpdump man page through config, so that it refers to the right man page sections. Have it refer to the new pcap-savefile man page for a description of the savefile format.
2008-10-28 05:20:16 +08:00
"tcpdump.1") CONFIG_FILES="$CONFIG_FILES tcpdump.1" ;;
We support building tcpdump with versions of libpcap other than the one with which it was released, and DLT_BLUETOOTH_HCI_H4_WITH_PHDR might be defined by pcap-bpf.h without pcap/bluetooth.h being present (as appears to be the case on Fedora 9, for example), so check whether <pcap/bluetooth.h> is usable. Update a comment - F9 appears to have a "/usr/include/pcap.h" if you install the libpcap headers. When adding -I flags when running a compiler-based test, add them to CPPFLAGS, not CFLAGS - the latter doesn't work right with AC_CHECK_HEADERS, as the "gcc -E" run doesn't have the -I flags added.
2008-09-26 05:45:50 +08:00
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
*) as_fn_error $? "invalid argument: \`$ac_config_target'" "$LINENO" 5;;
Initial revision
1999-10-08 07:47:09 +08:00
esac
Regenerate with autoconf 2.57.
2004-01-14 11:15:08 +08:00
done
Initial revision
1999-10-08 07:47:09 +08:00
We support building tcpdump with versions of libpcap other than the one with which it was released, and DLT_BLUETOOTH_HCI_H4_WITH_PHDR might be defined by pcap-bpf.h without pcap/bluetooth.h being present (as appears to be the case on Fedora 9, for example), so check whether <pcap/bluetooth.h> is usable. Update a comment - F9 appears to have a "/usr/include/pcap.h" if you install the libpcap headers. When adding -I flags when running a compiler-based test, add them to CPPFLAGS, not CFLAGS - the latter doesn't work right with AC_CHECK_HEADERS, as the "gcc -E" run doesn't have the -I flags added.
2008-09-26 05:45:50 +08:00
Regenerate with autoconf 2.57.
2004-01-14 11:15:08 +08:00
# If the user did not use the arguments to specify the items to instantiate,
# then the envvar interface is used. Set only those that are not.
# We use the long form for the default assignment because of an extremely
# bizarre bug on SunOS 4.1.3.
if $ac_need_defaults; then
test "${CONFIG_FILES+set}" = set || CONFIG_FILES=$config_files
test "${CONFIG_HEADERS+set}" = set || CONFIG_HEADERS=$config_headers
test "${CONFIG_COMMANDS+set}" = set || CONFIG_COMMANDS=$config_commands
fi
From Andrew Church <andrew@users.sourceforge.net>: when testing for "pcap_version", "pcap_debug", and "yydebug", don't add our own functions referring to those variables - GCC 3.4.1 optimizes the test code out before the link is done, as it's in a function that's not called.
2004-08-27 15:17:03 +08:00
# Have a temporary directory for convenience. Make it in the build tree
We support building tcpdump with versions of libpcap other than the one with which it was released, and DLT_BLUETOOTH_HCI_H4_WITH_PHDR might be defined by pcap-bpf.h without pcap/bluetooth.h being present (as appears to be the case on Fedora 9, for example), so check whether <pcap/bluetooth.h> is usable. Update a comment - F9 appears to have a "/usr/include/pcap.h" if you install the libpcap headers. When adding -I flags when running a compiler-based test, add them to CPPFLAGS, not CFLAGS - the latter doesn't work right with AC_CHECK_HEADERS, as the "gcc -E" run doesn't have the -I flags added.
2008-09-26 05:45:50 +08:00
# simply because there is no reason against having it here, and in addition,
From Andrew Church <andrew@users.sourceforge.net>: when testing for "pcap_version", "pcap_debug", and "yydebug", don't add our own functions referring to those variables - GCC 3.4.1 optimizes the test code out before the link is done, as it's in a function that's not called.
2004-08-27 15:17:03 +08:00
# creating and moving files from /tmp can sometimes cause problems.
We support building tcpdump with versions of libpcap other than the one with which it was released, and DLT_BLUETOOTH_HCI_H4_WITH_PHDR might be defined by pcap-bpf.h without pcap/bluetooth.h being present (as appears to be the case on Fedora 9, for example), so check whether <pcap/bluetooth.h> is usable. Update a comment - F9 appears to have a "/usr/include/pcap.h" if you install the libpcap headers. When adding -I flags when running a compiler-based test, add them to CPPFLAGS, not CFLAGS - the latter doesn't work right with AC_CHECK_HEADERS, as the "gcc -E" run doesn't have the -I flags added.
2008-09-26 05:45:50 +08:00
# Hook for its removal unless debugging.
# Note that there is a small window in which the directory will not be cleaned:
# after its creation but before its name has been assigned to `$tmp'.
Regenerate with autoconf 2.57.
2004-01-14 11:15:08 +08:00
$debug ||
{
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
tmp= ac_tmp=
We support building tcpdump with versions of libpcap other than the one with which it was released, and DLT_BLUETOOTH_HCI_H4_WITH_PHDR might be defined by pcap-bpf.h without pcap/bluetooth.h being present (as appears to be the case on Fedora 9, for example), so check whether <pcap/bluetooth.h> is usable. Update a comment - F9 appears to have a "/usr/include/pcap.h" if you install the libpcap headers. When adding -I flags when running a compiler-based test, add them to CPPFLAGS, not CFLAGS - the latter doesn't work right with AC_CHECK_HEADERS, as the "gcc -E" run doesn't have the -I flags added.
2008-09-26 05:45:50 +08:00
trap 'exit_status=$?
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
: "${ac_tmp:=$tmp}"
{ test ! -d "$ac_tmp" || rm -fr "$ac_tmp"; } && exit $exit_status
We support building tcpdump with versions of libpcap other than the one with which it was released, and DLT_BLUETOOTH_HCI_H4_WITH_PHDR might be defined by pcap-bpf.h without pcap/bluetooth.h being present (as appears to be the case on Fedora 9, for example), so check whether <pcap/bluetooth.h> is usable. Update a comment - F9 appears to have a "/usr/include/pcap.h" if you install the libpcap headers. When adding -I flags when running a compiler-based test, add them to CPPFLAGS, not CFLAGS - the latter doesn't work right with AC_CHECK_HEADERS, as the "gcc -E" run doesn't have the -I flags added.
2008-09-26 05:45:50 +08:00
' 0
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
trap 'as_fn_exit 1' 1 2 13 15
Regenerate with autoconf 2.57.
2004-01-14 11:15:08 +08:00
}
# Create a (secure) tmp directory for tmp files.
From Andrew Church <andrew@users.sourceforge.net>: when testing for "pcap_version", "pcap_debug", and "yydebug", don't add our own functions referring to those variables - GCC 3.4.1 optimizes the test code out before the link is done, as it's in a function that's not called.
2004-08-27 15:17:03 +08:00
Regenerate with autoconf 2.57.
2004-01-14 11:15:08 +08:00
{
We support building tcpdump with versions of libpcap other than the one with which it was released, and DLT_BLUETOOTH_HCI_H4_WITH_PHDR might be defined by pcap-bpf.h without pcap/bluetooth.h being present (as appears to be the case on Fedora 9, for example), so check whether <pcap/bluetooth.h> is usable. Update a comment - F9 appears to have a "/usr/include/pcap.h" if you install the libpcap headers. When adding -I flags when running a compiler-based test, add them to CPPFLAGS, not CFLAGS - the latter doesn't work right with AC_CHECK_HEADERS, as the "gcc -E" run doesn't have the -I flags added.
2008-09-26 05:45:50 +08:00
tmp=`(umask 077 && mktemp -d "./confXXXXXX") 2>/dev/null` &&
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
test -d "$tmp"
Regenerate with autoconf 2.57.
2004-01-14 11:15:08 +08:00
} ||
{
We support building tcpdump with versions of libpcap other than the one with which it was released, and DLT_BLUETOOTH_HCI_H4_WITH_PHDR might be defined by pcap-bpf.h without pcap/bluetooth.h being present (as appears to be the case on Fedora 9, for example), so check whether <pcap/bluetooth.h> is usable. Update a comment - F9 appears to have a "/usr/include/pcap.h" if you install the libpcap headers. When adding -I flags when running a compiler-based test, add them to CPPFLAGS, not CFLAGS - the latter doesn't work right with AC_CHECK_HEADERS, as the "gcc -E" run doesn't have the -I flags added.
2008-09-26 05:45:50 +08:00
tmp=./conf$$-$RANDOM
(umask 077 && mkdir "$tmp")
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
} || as_fn_error $? "cannot create a temporary directory in ." "$LINENO" 5
ac_tmp=$tmp
We support building tcpdump with versions of libpcap other than the one with which it was released, and DLT_BLUETOOTH_HCI_H4_WITH_PHDR might be defined by pcap-bpf.h without pcap/bluetooth.h being present (as appears to be the case on Fedora 9, for example), so check whether <pcap/bluetooth.h> is usable. Update a comment - F9 appears to have a "/usr/include/pcap.h" if you install the libpcap headers. When adding -I flags when running a compiler-based test, add them to CPPFLAGS, not CFLAGS - the latter doesn't work right with AC_CHECK_HEADERS, as the "gcc -E" run doesn't have the -I flags added.
2008-09-26 05:45:50 +08:00
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
# Set up the scripts for CONFIG_FILES section.
# No need to generate them if there are no CONFIG_FILES.
# This happens for instance with `./config.status config.h'.
Check for extra networking libraries before checking for IPv6. On some platforms, such as SunOS 5.x, building the "do we have IPv6 support?" test program requires the extra networking libraries, so we need to know what extra networking libraries are required before doing that test.
2013-04-07 04:03:58 +08:00
if test -n "$CONFIG_FILES"; then
Simplify the detection of OpenSSL libcrypto by using standard autoconf macros rather than a local copy of AC_LBL_SSLEAY. AC_LBL_SSLEAY is old and has not kept pace with some more recent developments in packaging like Debian and Ubuntu's multiarch support. The autoconf macros have been updated to handle multiarch so using them means that tcpdump gains the ability to be built with libcrypto on these new multiarch distros and to work successfully with Travis CI, which uses Ubuntu 12, which is one such multiarch distro (see GH-32). Fixes GH-33
2012-10-14 02:21:45 +08:00
We support building tcpdump with versions of libpcap other than the one with which it was released, and DLT_BLUETOOTH_HCI_H4_WITH_PHDR might be defined by pcap-bpf.h without pcap/bluetooth.h being present (as appears to be the case on Fedora 9, for example), so check whether <pcap/bluetooth.h> is usable. Update a comment - F9 appears to have a "/usr/include/pcap.h" if you install the libpcap headers. When adding -I flags when running a compiler-based test, add them to CPPFLAGS, not CFLAGS - the latter doesn't work right with AC_CHECK_HEADERS, as the "gcc -E" run doesn't have the -I flags added.
2008-09-26 05:45:50 +08:00
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
ac_cr=`echo X | tr X '\015'`
# On cygwin, bash can eat \r inside `` if the user requested igncr.
# But we know of no other shell where ac_cr would be empty at this
# point, so we can use a bashism as a fallback.
if test "x$ac_cr" = x; then
eval ac_cr=\$\'\\r\'
fi
ac_cs_awk_cr=`$AWK 'BEGIN { print "a\rb" }' </dev/null 2>/dev/null`
if test "$ac_cs_awk_cr" = "a${ac_cr}b"; then
ac_cs_awk_cr='\\r'
else
ac_cs_awk_cr=$ac_cr
fi
echo 'BEGIN {' >"$ac_tmp/subs1.awk" &&
_ACEOF
We support building tcpdump with versions of libpcap other than the one with which it was released, and DLT_BLUETOOTH_HCI_H4_WITH_PHDR might be defined by pcap-bpf.h without pcap/bluetooth.h being present (as appears to be the case on Fedora 9, for example), so check whether <pcap/bluetooth.h> is usable. Update a comment - F9 appears to have a "/usr/include/pcap.h" if you install the libpcap headers. When adding -I flags when running a compiler-based test, add them to CPPFLAGS, not CFLAGS - the latter doesn't work right with AC_CHECK_HEADERS, as the "gcc -E" run doesn't have the -I flags added.
2008-09-26 05:45:50 +08:00
Check for extra networking libraries before checking for IPv6. On some platforms, such as SunOS 5.x, building the "do we have IPv6 support?" test program requires the extra networking libraries, so we need to know what extra networking libraries are required before doing that test.
2013-04-07 04:03:58 +08:00
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
{
echo "cat >conf$$subs.awk <<_ACEOF" &&
echo "$ac_subst_vars" | sed 's/.*/&!$&$ac_delim/' &&
echo "_ACEOF"
} >conf$$subs.sh ||
as_fn_error $? "could not make $CONFIG_STATUS" "$LINENO" 5
ac_delim_num=`echo "$ac_subst_vars" | grep -c '^'`
We support building tcpdump with versions of libpcap other than the one with which it was released, and DLT_BLUETOOTH_HCI_H4_WITH_PHDR might be defined by pcap-bpf.h without pcap/bluetooth.h being present (as appears to be the case on Fedora 9, for example), so check whether <pcap/bluetooth.h> is usable. Update a comment - F9 appears to have a "/usr/include/pcap.h" if you install the libpcap headers. When adding -I flags when running a compiler-based test, add them to CPPFLAGS, not CFLAGS - the latter doesn't work right with AC_CHECK_HEADERS, as the "gcc -E" run doesn't have the -I flags added.
2008-09-26 05:45:50 +08:00
ac_delim='%!_!# '
for ac_last_try in false false false false false :; do
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
. ./conf$$subs.sh ||
as_fn_error $? "could not make $CONFIG_STATUS" "$LINENO" 5
ac_delim_n=`sed -n "s/.*$ac_delim\$/X/p" conf$$subs.awk | grep -c X`
if test $ac_delim_n = $ac_delim_num; then
We support building tcpdump with versions of libpcap other than the one with which it was released, and DLT_BLUETOOTH_HCI_H4_WITH_PHDR might be defined by pcap-bpf.h without pcap/bluetooth.h being present (as appears to be the case on Fedora 9, for example), so check whether <pcap/bluetooth.h> is usable. Update a comment - F9 appears to have a "/usr/include/pcap.h" if you install the libpcap headers. When adding -I flags when running a compiler-based test, add them to CPPFLAGS, not CFLAGS - the latter doesn't work right with AC_CHECK_HEADERS, as the "gcc -E" run doesn't have the -I flags added.
2008-09-26 05:45:50 +08:00
break
elif $ac_last_try; then
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
as_fn_error $? "could not make $CONFIG_STATUS" "$LINENO" 5
We support building tcpdump with versions of libpcap other than the one with which it was released, and DLT_BLUETOOTH_HCI_H4_WITH_PHDR might be defined by pcap-bpf.h without pcap/bluetooth.h being present (as appears to be the case on Fedora 9, for example), so check whether <pcap/bluetooth.h> is usable. Update a comment - F9 appears to have a "/usr/include/pcap.h" if you install the libpcap headers. When adding -I flags when running a compiler-based test, add them to CPPFLAGS, not CFLAGS - the latter doesn't work right with AC_CHECK_HEADERS, as the "gcc -E" run doesn't have the -I flags added.
2008-09-26 05:45:50 +08:00
else
ac_delim="$ac_delim!$ac_delim _$ac_delim!! "
Initial revision
1999-10-08 07:47:09 +08:00
fi
We support building tcpdump with versions of libpcap other than the one with which it was released, and DLT_BLUETOOTH_HCI_H4_WITH_PHDR might be defined by pcap-bpf.h without pcap/bluetooth.h being present (as appears to be the case on Fedora 9, for example), so check whether <pcap/bluetooth.h> is usable. Update a comment - F9 appears to have a "/usr/include/pcap.h" if you install the libpcap headers. When adding -I flags when running a compiler-based test, add them to CPPFLAGS, not CFLAGS - the latter doesn't work right with AC_CHECK_HEADERS, as the "gcc -E" run doesn't have the -I flags added.
2008-09-26 05:45:50 +08:00
done
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
rm -f conf$$subs.sh
cat >>$CONFIG_STATUS <<_ACEOF || ac_write_fail=1
cat >>"\$ac_tmp/subs1.awk" <<\\_ACAWK &&
_ACEOF
sed -n '
h
s/^/S["/; s/!.*/"]=/
p
g
s/^[^!]*!//
:repl
t repl
s/'"$ac_delim"'$//
t delim
:nl
h
s/\(.\{148\}\)..*/\1/
t more1
s/["\\]/\\&/g; s/^/"/; s/$/\\n"\\/
p
n
b repl
:more1
s/["\\]/\\&/g; s/^/"/; s/$/"\\/
p
g
s/.\{148\}//
t nl
:delim
h
s/\(.\{148\}\)..*/\1/
t more2
s/["\\]/\\&/g; s/^/"/; s/$/"/
p
b
:more2
s/["\\]/\\&/g; s/^/"/; s/$/"\\/
p
g
s/.\{148\}//
t delim
' <conf$$subs.awk | sed '
/^[^""]/{
N
s/\n//
}
' >>$CONFIG_STATUS || ac_write_fail=1
rm -f conf$$subs.awk
cat >>$CONFIG_STATUS <<_ACEOF || ac_write_fail=1
_ACAWK
cat >>"\$ac_tmp/subs1.awk" <<_ACAWK &&
for (key in S) S_is_set[key] = 1
FS = ""
We support building tcpdump with versions of libpcap other than the one with which it was released, and DLT_BLUETOOTH_HCI_H4_WITH_PHDR might be defined by pcap-bpf.h without pcap/bluetooth.h being present (as appears to be the case on Fedora 9, for example), so check whether <pcap/bluetooth.h> is usable. Update a comment - F9 appears to have a "/usr/include/pcap.h" if you install the libpcap headers. When adding -I flags when running a compiler-based test, add them to CPPFLAGS, not CFLAGS - the latter doesn't work right with AC_CHECK_HEADERS, as the "gcc -E" run doesn't have the -I flags added.
2008-09-26 05:45:50 +08:00
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
}
{
line = $ 0
nfields = split(line, field, "@")
substed = 0
len = length(field[1])
for (i = 2; i < nfields; i++) {
key = field[i]
keylen = length(key)
if (S_is_set[key]) {
value = S[key]
line = substr(line, 1, len) "" value "" substr(line, len + keylen + 3)
len += length(value) + length(field[++i])
substed = 1
} else
len += 1 + keylen
}
Simplify the detection of OpenSSL libcrypto by using standard autoconf macros rather than a local copy of AC_LBL_SSLEAY. AC_LBL_SSLEAY is old and has not kept pace with some more recent developments in packaging like Debian and Ubuntu's multiarch support. The autoconf macros have been updated to handle multiarch so using them means that tcpdump gains the ability to be built with libcrypto on these new multiarch distros and to work successfully with Travis CI, which uses Ubuntu 12, which is one such multiarch distro (see GH-32). Fixes GH-33
2012-10-14 02:21:45 +08:00
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
print line
}
_ACAWK
We support building tcpdump with versions of libpcap other than the one with which it was released, and DLT_BLUETOOTH_HCI_H4_WITH_PHDR might be defined by pcap-bpf.h without pcap/bluetooth.h being present (as appears to be the case on Fedora 9, for example), so check whether <pcap/bluetooth.h> is usable. Update a comment - F9 appears to have a "/usr/include/pcap.h" if you install the libpcap headers. When adding -I flags when running a compiler-based test, add them to CPPFLAGS, not CFLAGS - the latter doesn't work right with AC_CHECK_HEADERS, as the "gcc -E" run doesn't have the -I flags added.
2008-09-26 05:45:50 +08:00
_ACEOF
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
cat >>$CONFIG_STATUS <<\_ACEOF || ac_write_fail=1
if sed "s/$ac_cr//" < /dev/null > /dev/null 2>&1; then
sed "s/$ac_cr\$//; s/$ac_cr/$ac_cs_awk_cr/g"
else
cat
fi < "$ac_tmp/subs1.awk" > "$ac_tmp/subs.awk" \
|| as_fn_error $? "could not setup config files machinery" "$LINENO" 5
From Andrew Church <andrew@users.sourceforge.net>: when testing for "pcap_version", "pcap_debug", and "yydebug", don't add our own functions referring to those variables - GCC 3.4.1 optimizes the test code out before the link is done, as it's in a function that's not called.
2004-08-27 15:17:03 +08:00
_ACEOF
We support building tcpdump with versions of libpcap other than the one with which it was released, and DLT_BLUETOOTH_HCI_H4_WITH_PHDR might be defined by pcap-bpf.h without pcap/bluetooth.h being present (as appears to be the case on Fedora 9, for example), so check whether <pcap/bluetooth.h> is usable. Update a comment - F9 appears to have a "/usr/include/pcap.h" if you install the libpcap headers. When adding -I flags when running a compiler-based test, add them to CPPFLAGS, not CFLAGS - the latter doesn't work right with AC_CHECK_HEADERS, as the "gcc -E" run doesn't have the -I flags added.
2008-09-26 05:45:50 +08:00
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
# VPATH may cause trouble with some makes, so we remove sole $(srcdir),
# ${srcdir} and @srcdir@ entries from VPATH if srcdir is ".", strip leading and
We support building tcpdump with versions of libpcap other than the one with which it was released, and DLT_BLUETOOTH_HCI_H4_WITH_PHDR might be defined by pcap-bpf.h without pcap/bluetooth.h being present (as appears to be the case on Fedora 9, for example), so check whether <pcap/bluetooth.h> is usable. Update a comment - F9 appears to have a "/usr/include/pcap.h" if you install the libpcap headers. When adding -I flags when running a compiler-based test, add them to CPPFLAGS, not CFLAGS - the latter doesn't work right with AC_CHECK_HEADERS, as the "gcc -E" run doesn't have the -I flags added.
2008-09-26 05:45:50 +08:00
# trailing colons and then remove the whole line if VPATH becomes empty
# (actually we leave an empty line to preserve line numbers).
if test "x$srcdir" = x.; then
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
ac_vpsub='/^[ ]*VPATH[ ]*=[ ]*/{
h
s///
s/^/:/
s/[ ]*$/:/
s/:\$(srcdir):/:/g
s/:\${srcdir}:/:/g
s/:@srcdir@:/:/g
s/^:*//
We support building tcpdump with versions of libpcap other than the one with which it was released, and DLT_BLUETOOTH_HCI_H4_WITH_PHDR might be defined by pcap-bpf.h without pcap/bluetooth.h being present (as appears to be the case on Fedora 9, for example), so check whether <pcap/bluetooth.h> is usable. Update a comment - F9 appears to have a "/usr/include/pcap.h" if you install the libpcap headers. When adding -I flags when running a compiler-based test, add them to CPPFLAGS, not CFLAGS - the latter doesn't work right with AC_CHECK_HEADERS, as the "gcc -E" run doesn't have the -I flags added.
2008-09-26 05:45:50 +08:00
s/:*$//
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
x
s/\(=[ ]*\).*/\1/
G
s/\n//
We support building tcpdump with versions of libpcap other than the one with which it was released, and DLT_BLUETOOTH_HCI_H4_WITH_PHDR might be defined by pcap-bpf.h without pcap/bluetooth.h being present (as appears to be the case on Fedora 9, for example), so check whether <pcap/bluetooth.h> is usable. Update a comment - F9 appears to have a "/usr/include/pcap.h" if you install the libpcap headers. When adding -I flags when running a compiler-based test, add them to CPPFLAGS, not CFLAGS - the latter doesn't work right with AC_CHECK_HEADERS, as the "gcc -E" run doesn't have the -I flags added.
2008-09-26 05:45:50 +08:00
s/^[^=]*=[ ]*$//
}'
fi
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
cat >>$CONFIG_STATUS <<\_ACEOF || ac_write_fail=1
We support building tcpdump with versions of libpcap other than the one with which it was released, and DLT_BLUETOOTH_HCI_H4_WITH_PHDR might be defined by pcap-bpf.h without pcap/bluetooth.h being present (as appears to be the case on Fedora 9, for example), so check whether <pcap/bluetooth.h> is usable. Update a comment - F9 appears to have a "/usr/include/pcap.h" if you install the libpcap headers. When adding -I flags when running a compiler-based test, add them to CPPFLAGS, not CFLAGS - the latter doesn't work right with AC_CHECK_HEADERS, as the "gcc -E" run doesn't have the -I flags added.
2008-09-26 05:45:50 +08:00
fi # test -n "$CONFIG_FILES"
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
# Set up the scripts for CONFIG_HEADERS section.
# No need to generate them if there are no CONFIG_HEADERS.
# This happens for instance with `./config.status Makefile'.
if test -n "$CONFIG_HEADERS"; then
cat >"$ac_tmp/defines.awk" <<\_ACAWK ||
BEGIN {
_ACEOF
# Transform confdefs.h into an awk script `defines.awk', embedded as
# here-document in config.status, that substitutes the proper values into
# config.h.in to produce config.h.
# Create a delimiter string that does not exist in confdefs.h, to ease
# handling of long lines.
ac_delim='%!_!# '
for ac_last_try in false false :; do
ac_tt=`sed -n "/$ac_delim/p" confdefs.h`
if test -z "$ac_tt"; then
break
elif $ac_last_try; then
as_fn_error $? "could not make $CONFIG_HEADERS" "$LINENO" 5
else
ac_delim="$ac_delim!$ac_delim _$ac_delim!! "
fi
done
# For the awk script, D is an array of macro values keyed by name,
# likewise P contains macro parameters if any. Preserve backslash
# newline sequences.
ac_word_re=[_$as_cr_Letters][_$as_cr_alnum]*
sed -n '
s/.\{148\}/&'"$ac_delim"'/g
t rset
:rset
s/^[ ]*#[ ]*define[ ][ ]*/ /
t def
d
:def
s/\\$//
t bsnl
s/["\\]/\\&/g
s/^ \('"$ac_word_re"'\)\(([^()]*)\)[ ]*\(.*\)/P["\1"]="\2"\
D["\1"]=" \3"/p
s/^ \('"$ac_word_re"'\)[ ]*\(.*\)/D["\1"]=" \2"/p
d
:bsnl
s/["\\]/\\&/g
s/^ \('"$ac_word_re"'\)\(([^()]*)\)[ ]*\(.*\)/P["\1"]="\2"\
D["\1"]=" \3\\\\\\n"\\/p
t cont
s/^ \('"$ac_word_re"'\)[ ]*\(.*\)/D["\1"]=" \2\\\\\\n"\\/p
t cont
d
:cont
n
s/.\{148\}/&'"$ac_delim"'/g
t clear
:clear
s/\\$//
t bsnlc
s/["\\]/\\&/g; s/^/"/; s/$/"/p
d
:bsnlc
s/["\\]/\\&/g; s/^/"/; s/$/\\\\\\n"\\/p
b cont
' <confdefs.h | sed '
s/'"$ac_delim"'/"\\\
"/g' >>$CONFIG_STATUS || ac_write_fail=1
cat >>$CONFIG_STATUS <<_ACEOF || ac_write_fail=1
for (key in D) D_is_set[key] = 1
FS = ""
}
/^[\t ]*#[\t ]*(define|undef)[\t ]+$ac_word_re([\t (]|\$)/ {
line = \$ 0
split(line, arg, " ")
if (arg[1] == "#") {
defundef = arg[2]
mac1 = arg[3]
} else {
defundef = substr(arg[1], 2)
mac1 = arg[2]
}
split(mac1, mac2, "(") #)
macro = mac2[1]
prefix = substr(line, 1, index(line, defundef) - 1)
if (D_is_set[macro]) {
# Preserve the white space surrounding the "#".
print prefix "define", macro P[macro] D[macro]
next
} else {
# Replace #undef with comments. This is necessary, for example,
# in the case of _POSIX_SOURCE, which is predefined and required
# on some systems where configure will not decide to define it.
if (defundef == "undef") {
print "/*", prefix defundef, macro, "*/"
next
}
}
}
{ print }
_ACAWK
_ACEOF
cat >>$CONFIG_STATUS <<\_ACEOF || ac_write_fail=1
as_fn_error $? "could not setup config headers machinery" "$LINENO" 5
fi # test -n "$CONFIG_HEADERS"
We support building tcpdump with versions of libpcap other than the one with which it was released, and DLT_BLUETOOTH_HCI_H4_WITH_PHDR might be defined by pcap-bpf.h without pcap/bluetooth.h being present (as appears to be the case on Fedora 9, for example), so check whether <pcap/bluetooth.h> is usable. Update a comment - F9 appears to have a "/usr/include/pcap.h" if you install the libpcap headers. When adding -I flags when running a compiler-based test, add them to CPPFLAGS, not CFLAGS - the latter doesn't work right with AC_CHECK_HEADERS, as the "gcc -E" run doesn't have the -I flags added.
2008-09-26 05:45:50 +08:00
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
eval set X " :F $CONFIG_FILES :H $CONFIG_HEADERS :C $CONFIG_COMMANDS"
shift
for ac_tag
We support building tcpdump with versions of libpcap other than the one with which it was released, and DLT_BLUETOOTH_HCI_H4_WITH_PHDR might be defined by pcap-bpf.h without pcap/bluetooth.h being present (as appears to be the case on Fedora 9, for example), so check whether <pcap/bluetooth.h> is usable. Update a comment - F9 appears to have a "/usr/include/pcap.h" if you install the libpcap headers. When adding -I flags when running a compiler-based test, add them to CPPFLAGS, not CFLAGS - the latter doesn't work right with AC_CHECK_HEADERS, as the "gcc -E" run doesn't have the -I flags added.
2008-09-26 05:45:50 +08:00
do
case $ac_tag in
:[FHLC]) ac_mode=$ac_tag; continue;;
esac
case $ac_mode$ac_tag in
:[FHL]*:*);;
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
:L* | :C*:*) as_fn_error $? "invalid tag \`$ac_tag'" "$LINENO" 5;;
We support building tcpdump with versions of libpcap other than the one with which it was released, and DLT_BLUETOOTH_HCI_H4_WITH_PHDR might be defined by pcap-bpf.h without pcap/bluetooth.h being present (as appears to be the case on Fedora 9, for example), so check whether <pcap/bluetooth.h> is usable. Update a comment - F9 appears to have a "/usr/include/pcap.h" if you install the libpcap headers. When adding -I flags when running a compiler-based test, add them to CPPFLAGS, not CFLAGS - the latter doesn't work right with AC_CHECK_HEADERS, as the "gcc -E" run doesn't have the -I flags added.
2008-09-26 05:45:50 +08:00
:[FH]-) ac_tag=-:-;;
:[FH]*) ac_tag=$ac_tag:$ac_tag.in;;
From Max Laier: check whether the system has <net/pfvar.h> and: if it does, use that for the pf definitions; if it doesn't, don't compile in pf support; as both OpenBSD and FreeBSD have changed the pf definitions and header format without changing the DLT value, so you can't reliably read pflog-format libpcap files on a machine running an OS version other than the one on which the file was generated.
2007-09-13 03:36:18 +08:00
esac
We support building tcpdump with versions of libpcap other than the one with which it was released, and DLT_BLUETOOTH_HCI_H4_WITH_PHDR might be defined by pcap-bpf.h without pcap/bluetooth.h being present (as appears to be the case on Fedora 9, for example), so check whether <pcap/bluetooth.h> is usable. Update a comment - F9 appears to have a "/usr/include/pcap.h" if you install the libpcap headers. When adding -I flags when running a compiler-based test, add them to CPPFLAGS, not CFLAGS - the latter doesn't work right with AC_CHECK_HEADERS, as the "gcc -E" run doesn't have the -I flags added.
2008-09-26 05:45:50 +08:00
ac_save_IFS=$IFS
IFS=:
set x $ac_tag
IFS=$ac_save_IFS
shift
ac_file=$1
shift
From Max Laier: check whether the system has <net/pfvar.h> and: if it does, use that for the pf definitions; if it doesn't, don't compile in pf support; as both OpenBSD and FreeBSD have changed the pf definitions and header format without changing the DLT value, so you can't reliably read pflog-format libpcap files on a machine running an OS version other than the one on which the file was generated.
2007-09-13 03:36:18 +08:00
We support building tcpdump with versions of libpcap other than the one with which it was released, and DLT_BLUETOOTH_HCI_H4_WITH_PHDR might be defined by pcap-bpf.h without pcap/bluetooth.h being present (as appears to be the case on Fedora 9, for example), so check whether <pcap/bluetooth.h> is usable. Update a comment - F9 appears to have a "/usr/include/pcap.h" if you install the libpcap headers. When adding -I flags when running a compiler-based test, add them to CPPFLAGS, not CFLAGS - the latter doesn't work right with AC_CHECK_HEADERS, as the "gcc -E" run doesn't have the -I flags added.
2008-09-26 05:45:50 +08:00
case $ac_mode in
:L) ac_source=$1;;
:[FH])
ac_file_inputs=
for ac_f
do
case $ac_f in
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
-) ac_f="$ac_tmp/stdin";;
We support building tcpdump with versions of libpcap other than the one with which it was released, and DLT_BLUETOOTH_HCI_H4_WITH_PHDR might be defined by pcap-bpf.h without pcap/bluetooth.h being present (as appears to be the case on Fedora 9, for example), so check whether <pcap/bluetooth.h> is usable. Update a comment - F9 appears to have a "/usr/include/pcap.h" if you install the libpcap headers. When adding -I flags when running a compiler-based test, add them to CPPFLAGS, not CFLAGS - the latter doesn't work right with AC_CHECK_HEADERS, as the "gcc -E" run doesn't have the -I flags added.
2008-09-26 05:45:50 +08:00
*) # Look for the file first in the build tree, then in the source tree
# (if the path is not absolute). The absolute path cannot be DOS-style,
# because $ac_f cannot contain `:'.
test -f "$ac_f" ||
case $ac_f in
[\\/$]*) false;;
*) test -f "$srcdir/$ac_f" && ac_f="$srcdir/$ac_f";;
esac ||
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
as_fn_error 1 "cannot find input file: \`$ac_f'" "$LINENO" 5;;
We support building tcpdump with versions of libpcap other than the one with which it was released, and DLT_BLUETOOTH_HCI_H4_WITH_PHDR might be defined by pcap-bpf.h without pcap/bluetooth.h being present (as appears to be the case on Fedora 9, for example), so check whether <pcap/bluetooth.h> is usable. Update a comment - F9 appears to have a "/usr/include/pcap.h" if you install the libpcap headers. When adding -I flags when running a compiler-based test, add them to CPPFLAGS, not CFLAGS - the latter doesn't work right with AC_CHECK_HEADERS, as the "gcc -E" run doesn't have the -I flags added.
2008-09-26 05:45:50 +08:00
esac
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
case $ac_f in *\'*) ac_f=`$as_echo "$ac_f" | sed "s/'/'\\\\\\\\''/g"`;; esac
as_fn_append ac_file_inputs " '$ac_f'"
We support building tcpdump with versions of libpcap other than the one with which it was released, and DLT_BLUETOOTH_HCI_H4_WITH_PHDR might be defined by pcap-bpf.h without pcap/bluetooth.h being present (as appears to be the case on Fedora 9, for example), so check whether <pcap/bluetooth.h> is usable. Update a comment - F9 appears to have a "/usr/include/pcap.h" if you install the libpcap headers. When adding -I flags when running a compiler-based test, add them to CPPFLAGS, not CFLAGS - the latter doesn't work right with AC_CHECK_HEADERS, as the "gcc -E" run doesn't have the -I flags added.
2008-09-26 05:45:50 +08:00
done
# Let's still pretend it is `configure' which instantiates (i.e., don't
# use $as_me), people would be surprised to read:
# /* config.h. Generated by config.status. */
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
configure_input='Generated from '`
$as_echo "$*" | sed 's|^[^:]*/||;s|:[^:]*/|, |g'
`' by configure.'
We support building tcpdump with versions of libpcap other than the one with which it was released, and DLT_BLUETOOTH_HCI_H4_WITH_PHDR might be defined by pcap-bpf.h without pcap/bluetooth.h being present (as appears to be the case on Fedora 9, for example), so check whether <pcap/bluetooth.h> is usable. Update a comment - F9 appears to have a "/usr/include/pcap.h" if you install the libpcap headers. When adding -I flags when running a compiler-based test, add them to CPPFLAGS, not CFLAGS - the latter doesn't work right with AC_CHECK_HEADERS, as the "gcc -E" run doesn't have the -I flags added.
2008-09-26 05:45:50 +08:00
if test x"$ac_file" != x-; then
configure_input="$ac_file. $configure_input"
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
{ $as_echo "$as_me:${as_lineno-$LINENO}: creating $ac_file" >&5
$as_echo "$as_me: creating $ac_file" >&6;}
We support building tcpdump with versions of libpcap other than the one with which it was released, and DLT_BLUETOOTH_HCI_H4_WITH_PHDR might be defined by pcap-bpf.h without pcap/bluetooth.h being present (as appears to be the case on Fedora 9, for example), so check whether <pcap/bluetooth.h> is usable. Update a comment - F9 appears to have a "/usr/include/pcap.h" if you install the libpcap headers. When adding -I flags when running a compiler-based test, add them to CPPFLAGS, not CFLAGS - the latter doesn't work right with AC_CHECK_HEADERS, as the "gcc -E" run doesn't have the -I flags added.
2008-09-26 05:45:50 +08:00
fi
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
# Neutralize special characters interpreted by sed in replacement strings.
case $configure_input in #(
*\&* | *\|* | *\\* )
ac_sed_conf_input=`$as_echo "$configure_input" |
sed 's/[\\\\&|]/\\\\&/g'`;; #(
*) ac_sed_conf_input=$configure_input;;
esac
We support building tcpdump with versions of libpcap other than the one with which it was released, and DLT_BLUETOOTH_HCI_H4_WITH_PHDR might be defined by pcap-bpf.h without pcap/bluetooth.h being present (as appears to be the case on Fedora 9, for example), so check whether <pcap/bluetooth.h> is usable. Update a comment - F9 appears to have a "/usr/include/pcap.h" if you install the libpcap headers. When adding -I flags when running a compiler-based test, add them to CPPFLAGS, not CFLAGS - the latter doesn't work right with AC_CHECK_HEADERS, as the "gcc -E" run doesn't have the -I flags added.
2008-09-26 05:45:50 +08:00
case $ac_tag in
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
*:-:* | *:-) cat >"$ac_tmp/stdin" \
|| as_fn_error $? "could not create $ac_file" "$LINENO" 5 ;;
We support building tcpdump with versions of libpcap other than the one with which it was released, and DLT_BLUETOOTH_HCI_H4_WITH_PHDR might be defined by pcap-bpf.h without pcap/bluetooth.h being present (as appears to be the case on Fedora 9, for example), so check whether <pcap/bluetooth.h> is usable. Update a comment - F9 appears to have a "/usr/include/pcap.h" if you install the libpcap headers. When adding -I flags when running a compiler-based test, add them to CPPFLAGS, not CFLAGS - the latter doesn't work right with AC_CHECK_HEADERS, as the "gcc -E" run doesn't have the -I flags added.
2008-09-26 05:45:50 +08:00
esac
;;
esac
ac_dir=`$as_dirname -- "$ac_file" ||
From Andrew Church <andrew@users.sourceforge.net>: when testing for "pcap_version", "pcap_debug", and "yydebug", don't add our own functions referring to those variables - GCC 3.4.1 optimizes the test code out before the link is done, as it's in a function that's not called.
2004-08-27 15:17:03 +08:00
$as_expr X"$ac_file" : 'X\(.*[^/]\)//*[^/][^/]*/*$' \| \
Add -Wpointer-arith to the list of warnings we enable with GCC.
2005-11-08 10:59:40 +08:00
X"$ac_file" : 'X\(//\)[^/]' \| \
X"$ac_file" : 'X\(//\)$' \| \
We support building tcpdump with versions of libpcap other than the one with which it was released, and DLT_BLUETOOTH_HCI_H4_WITH_PHDR might be defined by pcap-bpf.h without pcap/bluetooth.h being present (as appears to be the case on Fedora 9, for example), so check whether <pcap/bluetooth.h> is usable. Update a comment - F9 appears to have a "/usr/include/pcap.h" if you install the libpcap headers. When adding -I flags when running a compiler-based test, add them to CPPFLAGS, not CFLAGS - the latter doesn't work right with AC_CHECK_HEADERS, as the "gcc -E" run doesn't have the -I flags added.
2008-09-26 05:45:50 +08:00
X"$ac_file" : 'X\(/\)' \| . 2>/dev/null ||
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
$as_echo X"$ac_file" |
We support building tcpdump with versions of libpcap other than the one with which it was released, and DLT_BLUETOOTH_HCI_H4_WITH_PHDR might be defined by pcap-bpf.h without pcap/bluetooth.h being present (as appears to be the case on Fedora 9, for example), so check whether <pcap/bluetooth.h> is usable. Update a comment - F9 appears to have a "/usr/include/pcap.h" if you install the libpcap headers. When adding -I flags when running a compiler-based test, add them to CPPFLAGS, not CFLAGS - the latter doesn't work right with AC_CHECK_HEADERS, as the "gcc -E" run doesn't have the -I flags added.
2008-09-26 05:45:50 +08:00
sed '/^X\(.*[^/]\)\/\/*[^/][^/]*\/*$/{
s//\1/
q
}
/^X\(\/\/\)[^/].*/{
s//\1/
q
}
/^X\(\/\/\)$/{
s//\1/
q
}
/^X\(\/\).*/{
s//\1/
q
}
s/.*/./; q'`
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
as_dir="$ac_dir"; as_fn_mkdir_p
From Andrew Church <andrew@users.sourceforge.net>: when testing for "pcap_version", "pcap_debug", and "yydebug", don't add our own functions referring to those variables - GCC 3.4.1 optimizes the test code out before the link is done, as it's in a function that's not called.
2004-08-27 15:17:03 +08:00
ac_builddir=.
We support building tcpdump with versions of libpcap other than the one with which it was released, and DLT_BLUETOOTH_HCI_H4_WITH_PHDR might be defined by pcap-bpf.h without pcap/bluetooth.h being present (as appears to be the case on Fedora 9, for example), so check whether <pcap/bluetooth.h> is usable. Update a comment - F9 appears to have a "/usr/include/pcap.h" if you install the libpcap headers. When adding -I flags when running a compiler-based test, add them to CPPFLAGS, not CFLAGS - the latter doesn't work right with AC_CHECK_HEADERS, as the "gcc -E" run doesn't have the -I flags added.
2008-09-26 05:45:50 +08:00
case "$ac_dir" in
.) ac_dir_suffix= ac_top_builddir_sub=. ac_top_build_prefix= ;;
*)
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
ac_dir_suffix=/`$as_echo "$ac_dir" | sed 's|^\.[\\/]||'`
We support building tcpdump with versions of libpcap other than the one with which it was released, and DLT_BLUETOOTH_HCI_H4_WITH_PHDR might be defined by pcap-bpf.h without pcap/bluetooth.h being present (as appears to be the case on Fedora 9, for example), so check whether <pcap/bluetooth.h> is usable. Update a comment - F9 appears to have a "/usr/include/pcap.h" if you install the libpcap headers. When adding -I flags when running a compiler-based test, add them to CPPFLAGS, not CFLAGS - the latter doesn't work right with AC_CHECK_HEADERS, as the "gcc -E" run doesn't have the -I flags added.
2008-09-26 05:45:50 +08:00
# A ".." for each directory in $ac_dir_suffix.
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
ac_top_builddir_sub=`$as_echo "$ac_dir_suffix" | sed 's|/[^\\/]*|/..|g;s|/||'`
We support building tcpdump with versions of libpcap other than the one with which it was released, and DLT_BLUETOOTH_HCI_H4_WITH_PHDR might be defined by pcap-bpf.h without pcap/bluetooth.h being present (as appears to be the case on Fedora 9, for example), so check whether <pcap/bluetooth.h> is usable. Update a comment - F9 appears to have a "/usr/include/pcap.h" if you install the libpcap headers. When adding -I flags when running a compiler-based test, add them to CPPFLAGS, not CFLAGS - the latter doesn't work right with AC_CHECK_HEADERS, as the "gcc -E" run doesn't have the -I flags added.
2008-09-26 05:45:50 +08:00
case $ac_top_builddir_sub in
"") ac_top_builddir_sub=. ac_top_build_prefix= ;;
*) ac_top_build_prefix=$ac_top_builddir_sub/ ;;
esac ;;
esac
ac_abs_top_builddir=$ac_pwd
ac_abs_builddir=$ac_pwd$ac_dir_suffix
# for backward compatibility:
ac_top_builddir=$ac_top_build_prefix
From Andrew Church <andrew@users.sourceforge.net>: when testing for "pcap_version", "pcap_debug", and "yydebug", don't add our own functions referring to those variables - GCC 3.4.1 optimizes the test code out before the link is done, as it's in a function that's not called.
2004-08-27 15:17:03 +08:00
case $srcdir in
We support building tcpdump with versions of libpcap other than the one with which it was released, and DLT_BLUETOOTH_HCI_H4_WITH_PHDR might be defined by pcap-bpf.h without pcap/bluetooth.h being present (as appears to be the case on Fedora 9, for example), so check whether <pcap/bluetooth.h> is usable. Update a comment - F9 appears to have a "/usr/include/pcap.h" if you install the libpcap headers. When adding -I flags when running a compiler-based test, add them to CPPFLAGS, not CFLAGS - the latter doesn't work right with AC_CHECK_HEADERS, as the "gcc -E" run doesn't have the -I flags added.
2008-09-26 05:45:50 +08:00
.) # We are building in place.
From Andrew Church <andrew@users.sourceforge.net>: when testing for "pcap_version", "pcap_debug", and "yydebug", don't add our own functions referring to those variables - GCC 3.4.1 optimizes the test code out before the link is done, as it's in a function that's not called.
2004-08-27 15:17:03 +08:00
ac_srcdir=.
We support building tcpdump with versions of libpcap other than the one with which it was released, and DLT_BLUETOOTH_HCI_H4_WITH_PHDR might be defined by pcap-bpf.h without pcap/bluetooth.h being present (as appears to be the case on Fedora 9, for example), so check whether <pcap/bluetooth.h> is usable. Update a comment - F9 appears to have a "/usr/include/pcap.h" if you install the libpcap headers. When adding -I flags when running a compiler-based test, add them to CPPFLAGS, not CFLAGS - the latter doesn't work right with AC_CHECK_HEADERS, as the "gcc -E" run doesn't have the -I flags added.
2008-09-26 05:45:50 +08:00
ac_top_srcdir=$ac_top_builddir_sub
ac_abs_top_srcdir=$ac_pwd ;;
[\\/]* | ?:[\\/]* ) # Absolute name.
From Andrew Church <andrew@users.sourceforge.net>: when testing for "pcap_version", "pcap_debug", and "yydebug", don't add our own functions referring to those variables - GCC 3.4.1 optimizes the test code out before the link is done, as it's in a function that's not called.
2004-08-27 15:17:03 +08:00
ac_srcdir=$srcdir$ac_dir_suffix;
We support building tcpdump with versions of libpcap other than the one with which it was released, and DLT_BLUETOOTH_HCI_H4_WITH_PHDR might be defined by pcap-bpf.h without pcap/bluetooth.h being present (as appears to be the case on Fedora 9, for example), so check whether <pcap/bluetooth.h> is usable. Update a comment - F9 appears to have a "/usr/include/pcap.h" if you install the libpcap headers. When adding -I flags when running a compiler-based test, add them to CPPFLAGS, not CFLAGS - the latter doesn't work right with AC_CHECK_HEADERS, as the "gcc -E" run doesn't have the -I flags added.
2008-09-26 05:45:50 +08:00
ac_top_srcdir=$srcdir
ac_abs_top_srcdir=$srcdir ;;
*) # Relative name.
ac_srcdir=$ac_top_build_prefix$srcdir$ac_dir_suffix
ac_top_srcdir=$ac_top_build_prefix$srcdir
ac_abs_top_srcdir=$ac_pwd/$srcdir ;;
From Andrew Church <andrew@users.sourceforge.net>: when testing for "pcap_version", "pcap_debug", and "yydebug", don't add our own functions referring to those variables - GCC 3.4.1 optimizes the test code out before the link is done, as it's in a function that's not called.
2004-08-27 15:17:03 +08:00
esac
We support building tcpdump with versions of libpcap other than the one with which it was released, and DLT_BLUETOOTH_HCI_H4_WITH_PHDR might be defined by pcap-bpf.h without pcap/bluetooth.h being present (as appears to be the case on Fedora 9, for example), so check whether <pcap/bluetooth.h> is usable. Update a comment - F9 appears to have a "/usr/include/pcap.h" if you install the libpcap headers. When adding -I flags when running a compiler-based test, add them to CPPFLAGS, not CFLAGS - the latter doesn't work right with AC_CHECK_HEADERS, as the "gcc -E" run doesn't have the -I flags added.
2008-09-26 05:45:50 +08:00
ac_abs_srcdir=$ac_abs_top_srcdir$ac_dir_suffix
Add -Wpointer-arith to the list of warnings we enable with GCC.
2005-11-08 10:59:40 +08:00
From Andrew Church <andrew@users.sourceforge.net>: when testing for "pcap_version", "pcap_debug", and "yydebug", don't add our own functions referring to those variables - GCC 3.4.1 optimizes the test code out before the link is done, as it's in a function that's not called.
2004-08-27 15:17:03 +08:00
We support building tcpdump with versions of libpcap other than the one with which it was released, and DLT_BLUETOOTH_HCI_H4_WITH_PHDR might be defined by pcap-bpf.h without pcap/bluetooth.h being present (as appears to be the case on Fedora 9, for example), so check whether <pcap/bluetooth.h> is usable. Update a comment - F9 appears to have a "/usr/include/pcap.h" if you install the libpcap headers. When adding -I flags when running a compiler-based test, add them to CPPFLAGS, not CFLAGS - the latter doesn't work right with AC_CHECK_HEADERS, as the "gcc -E" run doesn't have the -I flags added.
2008-09-26 05:45:50 +08:00
case $ac_mode in
:F)
#
# CONFIG_FILE
#
Regenerate with autoconf 2.57.
2004-01-14 11:15:08 +08:00
case $INSTALL in
[\\/$]* | ?:[\\/]* ) ac_INSTALL=$INSTALL ;;
We support building tcpdump with versions of libpcap other than the one with which it was released, and DLT_BLUETOOTH_HCI_H4_WITH_PHDR might be defined by pcap-bpf.h without pcap/bluetooth.h being present (as appears to be the case on Fedora 9, for example), so check whether <pcap/bluetooth.h> is usable. Update a comment - F9 appears to have a "/usr/include/pcap.h" if you install the libpcap headers. When adding -I flags when running a compiler-based test, add them to CPPFLAGS, not CFLAGS - the latter doesn't work right with AC_CHECK_HEADERS, as the "gcc -E" run doesn't have the -I flags added.
2008-09-26 05:45:50 +08:00
*) ac_INSTALL=$ac_top_build_prefix$INSTALL ;;
Initial revision
1999-10-08 07:47:09 +08:00
esac
We support building tcpdump with versions of libpcap other than the one with which it was released, and DLT_BLUETOOTH_HCI_H4_WITH_PHDR might be defined by pcap-bpf.h without pcap/bluetooth.h being present (as appears to be the case on Fedora 9, for example), so check whether <pcap/bluetooth.h> is usable. Update a comment - F9 appears to have a "/usr/include/pcap.h" if you install the libpcap headers. When adding -I flags when running a compiler-based test, add them to CPPFLAGS, not CFLAGS - the latter doesn't work right with AC_CHECK_HEADERS, as the "gcc -E" run doesn't have the -I flags added.
2008-09-26 05:45:50 +08:00
_ACEOF
Initial revision
1999-10-08 07:47:09 +08:00
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
cat >>$CONFIG_STATUS <<\_ACEOF || ac_write_fail=1
We support building tcpdump with versions of libpcap other than the one with which it was released, and DLT_BLUETOOTH_HCI_H4_WITH_PHDR might be defined by pcap-bpf.h without pcap/bluetooth.h being present (as appears to be the case on Fedora 9, for example), so check whether <pcap/bluetooth.h> is usable. Update a comment - F9 appears to have a "/usr/include/pcap.h" if you install the libpcap headers. When adding -I flags when running a compiler-based test, add them to CPPFLAGS, not CFLAGS - the latter doesn't work right with AC_CHECK_HEADERS, as the "gcc -E" run doesn't have the -I flags added.
2008-09-26 05:45:50 +08:00
# If the template does not know about datarootdir, expand it.
# FIXME: This hack should be removed a few years after 2.60.
ac_datarootdir_hack=; ac_datarootdir_seen=
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
ac_sed_dataroot='
/datarootdir/ {
We support building tcpdump with versions of libpcap other than the one with which it was released, and DLT_BLUETOOTH_HCI_H4_WITH_PHDR might be defined by pcap-bpf.h without pcap/bluetooth.h being present (as appears to be the case on Fedora 9, for example), so check whether <pcap/bluetooth.h> is usable. Update a comment - F9 appears to have a "/usr/include/pcap.h" if you install the libpcap headers. When adding -I flags when running a compiler-based test, add them to CPPFLAGS, not CFLAGS - the latter doesn't work right with AC_CHECK_HEADERS, as the "gcc -E" run doesn't have the -I flags added.
2008-09-26 05:45:50 +08:00
p
q
}
/@datadir@/p
/@docdir@/p
/@infodir@/p
/@localedir@/p
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
/@mandir@/p'
case `eval "sed -n \"\$ac_sed_dataroot\" $ac_file_inputs"` in
We support building tcpdump with versions of libpcap other than the one with which it was released, and DLT_BLUETOOTH_HCI_H4_WITH_PHDR might be defined by pcap-bpf.h without pcap/bluetooth.h being present (as appears to be the case on Fedora 9, for example), so check whether <pcap/bluetooth.h> is usable. Update a comment - F9 appears to have a "/usr/include/pcap.h" if you install the libpcap headers. When adding -I flags when running a compiler-based test, add them to CPPFLAGS, not CFLAGS - the latter doesn't work right with AC_CHECK_HEADERS, as the "gcc -E" run doesn't have the -I flags added.
2008-09-26 05:45:50 +08:00
*datarootdir*) ac_datarootdir_seen=yes;;
*@datadir@*|*@docdir@*|*@infodir@*|*@localedir@*|*@mandir@*)
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
{ $as_echo "$as_me:${as_lineno-$LINENO}: WARNING: $ac_file_inputs seems to ignore the --datarootdir setting" >&5
$as_echo "$as_me: WARNING: $ac_file_inputs seems to ignore the --datarootdir setting" >&2;}
From Andrew Church <andrew@users.sourceforge.net>: when testing for "pcap_version", "pcap_debug", and "yydebug", don't add our own functions referring to those variables - GCC 3.4.1 optimizes the test code out before the link is done, as it's in a function that's not called.
2004-08-27 15:17:03 +08:00
_ACEOF
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
cat >>$CONFIG_STATUS <<_ACEOF || ac_write_fail=1
We support building tcpdump with versions of libpcap other than the one with which it was released, and DLT_BLUETOOTH_HCI_H4_WITH_PHDR might be defined by pcap-bpf.h without pcap/bluetooth.h being present (as appears to be the case on Fedora 9, for example), so check whether <pcap/bluetooth.h> is usable. Update a comment - F9 appears to have a "/usr/include/pcap.h" if you install the libpcap headers. When adding -I flags when running a compiler-based test, add them to CPPFLAGS, not CFLAGS - the latter doesn't work right with AC_CHECK_HEADERS, as the "gcc -E" run doesn't have the -I flags added.
2008-09-26 05:45:50 +08:00
ac_datarootdir_hack='
s&@datadir@&$datadir&g
s&@docdir@&$docdir&g
s&@infodir@&$infodir&g
s&@localedir@&$localedir&g
s&@mandir@&$mandir&g
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
s&\\\${datarootdir}&$datarootdir&g' ;;
We support building tcpdump with versions of libpcap other than the one with which it was released, and DLT_BLUETOOTH_HCI_H4_WITH_PHDR might be defined by pcap-bpf.h without pcap/bluetooth.h being present (as appears to be the case on Fedora 9, for example), so check whether <pcap/bluetooth.h> is usable. Update a comment - F9 appears to have a "/usr/include/pcap.h" if you install the libpcap headers. When adding -I flags when running a compiler-based test, add them to CPPFLAGS, not CFLAGS - the latter doesn't work right with AC_CHECK_HEADERS, as the "gcc -E" run doesn't have the -I flags added.
2008-09-26 05:45:50 +08:00
esac
_ACEOF
# Neutralize VPATH when `$srcdir' = `.'.
# Shell code in configure.ac might set extrasub.
# FIXME: do we really want to maintain this feature?
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
cat >>$CONFIG_STATUS <<_ACEOF || ac_write_fail=1
ac_sed_extra="$ac_vpsub
Regenerate with autoconf 2.57.
2004-01-14 11:15:08 +08:00
$extrasub
From Andrew Church <andrew@users.sourceforge.net>: when testing for "pcap_version", "pcap_debug", and "yydebug", don't add our own functions referring to those variables - GCC 3.4.1 optimizes the test code out before the link is done, as it's in a function that's not called.
2004-08-27 15:17:03 +08:00
_ACEOF
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
cat >>$CONFIG_STATUS <<\_ACEOF || ac_write_fail=1
Regenerate with autoconf 2.57.
2004-01-14 11:15:08 +08:00
:t
/@[a-zA-Z_][a-zA-Z_0-9]*@/!b
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
s|@configure_input@|$ac_sed_conf_input|;t t
We support building tcpdump with versions of libpcap other than the one with which it was released, and DLT_BLUETOOTH_HCI_H4_WITH_PHDR might be defined by pcap-bpf.h without pcap/bluetooth.h being present (as appears to be the case on Fedora 9, for example), so check whether <pcap/bluetooth.h> is usable. Update a comment - F9 appears to have a "/usr/include/pcap.h" if you install the libpcap headers. When adding -I flags when running a compiler-based test, add them to CPPFLAGS, not CFLAGS - the latter doesn't work right with AC_CHECK_HEADERS, as the "gcc -E" run doesn't have the -I flags added.
2008-09-26 05:45:50 +08:00
s&@top_builddir@&$ac_top_builddir_sub&;t t
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
s&@top_build_prefix@&$ac_top_build_prefix&;t t
We support building tcpdump with versions of libpcap other than the one with which it was released, and DLT_BLUETOOTH_HCI_H4_WITH_PHDR might be defined by pcap-bpf.h without pcap/bluetooth.h being present (as appears to be the case on Fedora 9, for example), so check whether <pcap/bluetooth.h> is usable. Update a comment - F9 appears to have a "/usr/include/pcap.h" if you install the libpcap headers. When adding -I flags when running a compiler-based test, add them to CPPFLAGS, not CFLAGS - the latter doesn't work right with AC_CHECK_HEADERS, as the "gcc -E" run doesn't have the -I flags added.
2008-09-26 05:45:50 +08:00
s&@srcdir@&$ac_srcdir&;t t
s&@abs_srcdir@&$ac_abs_srcdir&;t t
s&@top_srcdir@&$ac_top_srcdir&;t t
s&@abs_top_srcdir@&$ac_abs_top_srcdir&;t t
s&@builddir@&$ac_builddir&;t t
s&@abs_builddir@&$ac_abs_builddir&;t t
s&@abs_top_builddir@&$ac_abs_top_builddir&;t t
s&@INSTALL@&$ac_INSTALL&;t t
$ac_datarootdir_hack
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
"
eval sed \"\$ac_sed_extra\" "$ac_file_inputs" | $AWK -f "$ac_tmp/subs.awk" \
>$ac_tmp/out || as_fn_error $? "could not create $ac_file" "$LINENO" 5
We support building tcpdump with versions of libpcap other than the one with which it was released, and DLT_BLUETOOTH_HCI_H4_WITH_PHDR might be defined by pcap-bpf.h without pcap/bluetooth.h being present (as appears to be the case on Fedora 9, for example), so check whether <pcap/bluetooth.h> is usable. Update a comment - F9 appears to have a "/usr/include/pcap.h" if you install the libpcap headers. When adding -I flags when running a compiler-based test, add them to CPPFLAGS, not CFLAGS - the latter doesn't work right with AC_CHECK_HEADERS, as the "gcc -E" run doesn't have the -I flags added.
2008-09-26 05:45:50 +08:00
test -z "$ac_datarootdir_hack$ac_datarootdir_seen" &&
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
{ ac_out=`sed -n '/\${datarootdir}/p' "$ac_tmp/out"`; test -n "$ac_out"; } &&
{ ac_out=`sed -n '/^[ ]*datarootdir[ ]*:*=/p' \
"$ac_tmp/out"`; test -z "$ac_out"; } &&
{ $as_echo "$as_me:${as_lineno-$LINENO}: WARNING: $ac_file contains a reference to the variable \`datarootdir'
which seems to be undefined. Please make sure it is defined" >&5
$as_echo "$as_me: WARNING: $ac_file contains a reference to the variable \`datarootdir'
which seems to be undefined. Please make sure it is defined" >&2;}
rm -f "$ac_tmp/stdin"
Regenerate with autoconf 2.57.
2004-01-14 11:15:08 +08:00
case $ac_file in
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
-) cat "$ac_tmp/out" && rm -f "$ac_tmp/out";;
*) rm -f "$ac_file" && mv "$ac_tmp/out" "$ac_file";;
esac \
|| as_fn_error $? "could not create $ac_file" "$LINENO" 5
We support building tcpdump with versions of libpcap other than the one with which it was released, and DLT_BLUETOOTH_HCI_H4_WITH_PHDR might be defined by pcap-bpf.h without pcap/bluetooth.h being present (as appears to be the case on Fedora 9, for example), so check whether <pcap/bluetooth.h> is usable. Update a comment - F9 appears to have a "/usr/include/pcap.h" if you install the libpcap headers. When adding -I flags when running a compiler-based test, add them to CPPFLAGS, not CFLAGS - the latter doesn't work right with AC_CHECK_HEADERS, as the "gcc -E" run doesn't have the -I flags added.
2008-09-26 05:45:50 +08:00
;;
:H)
#
# CONFIG_HEADER
#
Regenerate with autoconf 2.57.
2004-01-14 11:15:08 +08:00
if test x"$ac_file" != x-; then
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
{
$as_echo "/* $configure_input */" \
&& eval '$AWK -f "$ac_tmp/defines.awk"' "$ac_file_inputs"
} >"$ac_tmp/config.h" \
|| as_fn_error $? "could not create $ac_file" "$LINENO" 5
if diff "$ac_file" "$ac_tmp/config.h" >/dev/null 2>&1; then
{ $as_echo "$as_me:${as_lineno-$LINENO}: $ac_file is unchanged" >&5
$as_echo "$as_me: $ac_file is unchanged" >&6;}
Regenerate with autoconf 2.57.
2004-01-14 11:15:08 +08:00
else
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
rm -f "$ac_file"
mv "$ac_tmp/config.h" "$ac_file" \
|| as_fn_error $? "could not create $ac_file" "$LINENO" 5
Regenerate with autoconf 2.57.
2004-01-14 11:15:08 +08:00
fi
else
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
$as_echo "/* $configure_input */" \
&& eval '$AWK -f "$ac_tmp/defines.awk"' "$ac_file_inputs" \
|| as_fn_error $? "could not create -" "$LINENO" 5
Regenerate with autoconf 2.57.
2004-01-14 11:15:08 +08:00
fi
We support building tcpdump with versions of libpcap other than the one with which it was released, and DLT_BLUETOOTH_HCI_H4_WITH_PHDR might be defined by pcap-bpf.h without pcap/bluetooth.h being present (as appears to be the case on Fedora 9, for example), so check whether <pcap/bluetooth.h> is usable. Update a comment - F9 appears to have a "/usr/include/pcap.h" if you install the libpcap headers. When adding -I flags when running a compiler-based test, add them to CPPFLAGS, not CFLAGS - the latter doesn't work right with AC_CHECK_HEADERS, as the "gcc -E" run doesn't have the -I flags added.
2008-09-26 05:45:50 +08:00
;;
Run ranlib on libnetdissect.a if necessary. Remove it before building it, so we discard any stuff already in the archive.
2008-02-05 04:42:09 +08:00
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
:C) { $as_echo "$as_me:${as_lineno-$LINENO}: executing $ac_file commands" >&5
$as_echo "$as_me: executing $ac_file commands" >&6;}
We support building tcpdump with versions of libpcap other than the one with which it was released, and DLT_BLUETOOTH_HCI_H4_WITH_PHDR might be defined by pcap-bpf.h without pcap/bluetooth.h being present (as appears to be the case on Fedora 9, for example), so check whether <pcap/bluetooth.h> is usable. Update a comment - F9 appears to have a "/usr/include/pcap.h" if you install the libpcap headers. When adding -I flags when running a compiler-based test, add them to CPPFLAGS, not CFLAGS - the latter doesn't work right with AC_CHECK_HEADERS, as the "gcc -E" run doesn't have the -I flags added.
2008-09-26 05:45:50 +08:00
;;
esac
From Andrew Church <andrew@users.sourceforge.net>: when testing for "pcap_version", "pcap_debug", and "yydebug", don't add our own functions referring to those variables - GCC 3.4.1 optimizes the test code out before the link is done, as it's in a function that's not called.
2004-08-27 15:17:03 +08:00
Regenerate with autoconf 2.57.
2004-01-14 11:15:08 +08:00
We support building tcpdump with versions of libpcap other than the one with which it was released, and DLT_BLUETOOTH_HCI_H4_WITH_PHDR might be defined by pcap-bpf.h without pcap/bluetooth.h being present (as appears to be the case on Fedora 9, for example), so check whether <pcap/bluetooth.h> is usable. Update a comment - F9 appears to have a "/usr/include/pcap.h" if you install the libpcap headers. When adding -I flags when running a compiler-based test, add them to CPPFLAGS, not CFLAGS - the latter doesn't work right with AC_CHECK_HEADERS, as the "gcc -E" run doesn't have the -I flags added.
2008-09-26 05:45:50 +08:00
case $ac_file$ac_mode in
"default-1":C) if test -f .devel; then
Regenerate
2000-01-18 11:47:39 +08:00
echo timestamp > stamp-h
cat Makefile-devel-adds >> Makefile
make depend
Regenerate with autoconf 2.57.
2004-01-14 11:15:08 +08:00
fi ;;
We support building tcpdump with versions of libpcap other than the one with which it was released, and DLT_BLUETOOTH_HCI_H4_WITH_PHDR might be defined by pcap-bpf.h without pcap/bluetooth.h being present (as appears to be the case on Fedora 9, for example), so check whether <pcap/bluetooth.h> is usable. Update a comment - F9 appears to have a "/usr/include/pcap.h" if you install the libpcap headers. When adding -I flags when running a compiler-based test, add them to CPPFLAGS, not CFLAGS - the latter doesn't work right with AC_CHECK_HEADERS, as the "gcc -E" run doesn't have the -I flags added.
2008-09-26 05:45:50 +08:00
Regenerate with autoconf 2.57.
2004-01-14 11:15:08 +08:00
esac
We support building tcpdump with versions of libpcap other than the one with which it was released, and DLT_BLUETOOTH_HCI_H4_WITH_PHDR might be defined by pcap-bpf.h without pcap/bluetooth.h being present (as appears to be the case on Fedora 9, for example), so check whether <pcap/bluetooth.h> is usable. Update a comment - F9 appears to have a "/usr/include/pcap.h" if you install the libpcap headers. When adding -I flags when running a compiler-based test, add them to CPPFLAGS, not CFLAGS - the latter doesn't work right with AC_CHECK_HEADERS, as the "gcc -E" run doesn't have the -I flags added.
2008-09-26 05:45:50 +08:00
done # for ac_tag
Initial revision
1999-10-08 07:47:09 +08:00
Regenerate with autoconf 2.57.
2004-01-14 11:15:08 +08:00
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
as_fn_exit 0
From Andrew Church <andrew@users.sourceforge.net>: when testing for "pcap_version", "pcap_debug", and "yydebug", don't add our own functions referring to those variables - GCC 3.4.1 optimizes the test code out before the link is done, as it's in a function that's not called.
2004-08-27 15:17:03 +08:00
_ACEOF
Regenerate with autoconf 2.57.
2004-01-14 11:15:08 +08:00
ac_clean_files=$ac_clean_files_save
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
test $ac_write_fail = 0 ||
as_fn_error $? "write failure creating $CONFIG_STATUS" "$LINENO" 5
From Andrew Church <andrew@users.sourceforge.net>: when testing for "pcap_version", "pcap_debug", and "yydebug", don't add our own functions referring to those variables - GCC 3.4.1 optimizes the test code out before the link is done, as it's in a function that's not called.
2004-08-27 15:17:03 +08:00
Regenerate with autoconf 2.57.
2004-01-14 11:15:08 +08:00
# configure is writing to config.log, and then calls config.status.
# config.status does its own redirection, appending to config.log.
# Unfortunately, on DOS this fails, as config.log is still kept open
# by configure, so config.status won't be able to write to it; its
# output is simply discarded. So we exec the FD to /dev/null,
# effectively closing config.log, so it can be properly (re)opened and
# appended to by config.status. When coming back to configure, we
# need to make the FD available again.
if test "$no_create" != yes; then
ac_cs_success=:
From Andrew Church <andrew@users.sourceforge.net>: when testing for "pcap_version", "pcap_debug", and "yydebug", don't add our own functions referring to those variables - GCC 3.4.1 optimizes the test code out before the link is done, as it's in a function that's not called.
2004-08-27 15:17:03 +08:00
ac_config_status_args=
test "$silent" = yes &&
ac_config_status_args="$ac_config_status_args --quiet"
Regenerate with autoconf 2.57.
2004-01-14 11:15:08 +08:00
exec 5>/dev/null
From Andrew Church <andrew@users.sourceforge.net>: when testing for "pcap_version", "pcap_debug", and "yydebug", don't add our own functions referring to those variables - GCC 3.4.1 optimizes the test code out before the link is done, as it's in a function that's not called.
2004-08-27 15:17:03 +08:00
$SHELL $CONFIG_STATUS $ac_config_status_args || ac_cs_success=false
Regenerate with autoconf 2.57.
2004-01-14 11:15:08 +08:00
exec 5>>config.log
# Use ||, not &&, to avoid exiting from the if with $? = 1, which
# would make configure fail if this is the last instruction.
Clean up handling of -g and -O flags. AC_PROG_CC adds -g and -O2 to CFLAGS if you're using GCC; don't bother adding either of them, or -O, ourselves if we're using GCC. Add -O for all non-GCC compilers.
2013-10-18 07:50:43 +08:00
$ac_cs_success || as_fn_exit 1
fi
if test -n "$ac_unrecognized_opts" && test "$enable_option_checking" != no; then
{ $as_echo "$as_me:${as_lineno-$LINENO}: WARNING: unrecognized options: $ac_unrecognized_opts" >&5
$as_echo "$as_me: WARNING: unrecognized options: $ac_unrecognized_opts" >&2;}
Regenerate with autoconf 2.57.
2004-01-14 11:15:08 +08:00
fi
Initial revision
1999-10-08 07:47:09 +08:00
Regenerate
2000-01-18 11:47:39 +08:00
exit 0
Reference in New Issue Copy Permalink