1998-11-17 02:17:27 +00:00
dnl Macros that test for specific features.
2006-05-22 08:14:01 +00:00
dnl This file is part of the Autoconf packaging for Wireshark.
1999-11-30 22:45:09 +00:00
dnl Copyright (C) 1998-2000 by Gerald Combs.
dnl
2004-07-18 00:24:25 +00:00
dnl $Id$
1998-11-17 02:17:27 +00:00
dnl
dnl This program is free software; you can redistribute it and/or modify
dnl it under the terms of the GNU General Public License as published by
dnl the Free Software Foundation; either version 2, or (at your option)
dnl any later version.
dnl
dnl This program is distributed in the hope that it will be useful,
dnl but WITHOUT ANY WARRANTY; without even the implied warranty of
dnl MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
dnl GNU General Public License for more details.
dnl
dnl You should have received a copy of the GNU General Public License
dnl along with this program; if not, write to the Free Software
dnl Foundation, Inc., 59 Temple Place - Suite 330, Boston, MA
dnl 02111-1307, USA.
dnl
dnl As a special exception, the Free Software Foundation gives unlimited
dnl permission to copy, distribute and modify the configure scripts that
dnl are the output of Autoconf. You need not follow the terms of the GNU
dnl General Public License when using or distributing such scripts, even
dnl though portions of the text of Autoconf appear in them. The GNU
dnl General Public License (GPL) does govern all other use of the material
dnl that constitutes the Autoconf program.
dnl
dnl Certain portions of the Autoconf source text are designed to be copied
dnl (in certain cases, depending on the input) into the output of
dnl Autoconf. We call these the "data" portions. The rest of the Autoconf
dnl source text consists of comments plus executable code that decides which
dnl of the data portions to output in any given case. We call these
dnl comments and executable code the "non-data" portions. Autoconf never
dnl copies any of the non-data portions into its output.
dnl
dnl This special exception to the GPL applies to versions of Autoconf
dnl released by the Free Software Foundation. When you make and
dnl distribute a modified version of Autoconf, you may extend this special
dnl exception to the GPL to apply to your modified version as well, *unless*
dnl your modified version has the potential to copy into its output some
dnl of the text that was the non-data portion of the version that you started
dnl with. (In other words, unless your change moves or copies text from
dnl the non-data portions to the data portions.) If your modification has
dnl such potential, you must delete any notice of this special exception
dnl to the GPL from your modified version.
dnl
dnl Written by David MacKenzie, with help from
dnl Franc,ois Pinard, Karl Berry, Richard Pixley, Ian Lance Taylor,
dnl Roland McGrath, Noah Friedman, david d zuhn, and many others.
2000-01-15 09:46:28 +00:00
#
2006-05-31 19:12:15 +00:00
# AC_WIRESHARK_ADD_DASH_L
2000-01-15 09:46:28 +00:00
#
# Add to the variable specified as the first argument a "-L" flag for the
# directory specified as the second argument, and, on Solaris, add a
# "-R" flag for it as well.
#
# XXX - IRIX, and other OSes, may require some flag equivalent to
# "-R" here.
#
2006-05-31 19:12:15 +00:00
AC_DEFUN([AC_WIRESHARK_ADD_DASH_L],
2000-01-15 09:46:28 +00:00
[$1="$$1 -L$2"
case "$host_os" in
solaris*)
$1="$$1 -R$2"
;;
esac
])
2009-12-11 03:39:17 +00:00
#
# AC_WIRESHARK_TIMEZONE_ABBREV
#
AC_DEFUN([AC_WIRESHARK_TIMEZONE_ABBREV],
[
AC_CACHE_CHECK([for tm_zone in struct tm],
ac_cv_wireshark_have_tm_zone,
[
AC_TRY_COMPILE(
[#include <time.h>],
[struct tm t; t.tm_zone;],
ac_cv_wireshark_have_tm_zone=yes,
ac_cv_wireshark_have_tm_zone=no)
])
if test $ac_cv_wireshark_have_tm_zone = yes; then
AC_DEFINE(HAVE_TM_ZONE, 1, [Define if tm_zone field exists in struct tm])
else
AC_CACHE_CHECK([for tzname],
ac_cv_wireshark_have_tzname,
[
AC_TRY_LINK(
[#include <time.h>
#include <stdio.h>],
2009-12-11 09:11:42 +00:00
[printf("%s", tzname[0]);],
2009-12-11 03:39:17 +00:00
ac_cv_wireshark_have_tzname=yes,
ac_cv_wireshark_have_tzname=no)
])
if test $ac_cv_wireshark_have_tzname = yes; then
AC_DEFINE(HAVE_TZNAME, 1, [Define if tzname array exists])
fi
fi
])
2000-01-15 09:46:28 +00:00
1999-03-28 18:32:03 +00:00
#
2006-05-31 19:12:15 +00:00
# AC_WIRESHARK_STRUCT_SA_LEN
1999-03-28 18:32:03 +00:00
#
2000-01-15 08:08:20 +00:00
dnl AC_STRUCT_ST_BLKSIZE extracted from the file in question,
1998-11-17 02:17:27 +00:00
dnl "acspecific.m4" in GNU Autoconf 2.12, and turned into
2006-05-31 19:12:15 +00:00
dnl AC_WIRESHARK_STRUCT_SA_LEN, which checks if "struct sockaddr"
1998-11-17 02:17:27 +00:00
dnl has the 4.4BSD "sa_len" member, and defines HAVE_SA_LEN; that's
dnl what's in this file.
2008-10-24 18:08:32 +00:00
dnl Done by Guy Harris <guy@alum.mit.edu> on 1998-11-14.
1998-11-17 02:17:27 +00:00
dnl ### Checks for structure members
2006-05-31 19:12:15 +00:00
AC_DEFUN([AC_WIRESHARK_STRUCT_SA_LEN],
[AC_CACHE_CHECK([for sa_len in struct sockaddr], ac_cv_wireshark_struct_sa_len,
1998-11-17 02:17:27 +00:00
[AC_TRY_COMPILE([#include <sys/types.h>
#include <sys/socket.h>], [struct sockaddr s; s.sa_len;],
2006-05-31 19:12:15 +00:00
ac_cv_wireshark_struct_sa_len=yes, ac_cv_wireshark_struct_sa_len=no)])
if test $ac_cv_wireshark_struct_sa_len = yes; then
2003-02-26 20:08:33 +00:00
AC_DEFINE(HAVE_SA_LEN, 1, [Define if sa_len field exists in struct sockaddr])
1998-11-17 02:17:27 +00:00
fi
])
1999-03-28 18:32:03 +00:00
2004-06-19 00:07:23 +00:00
1999-03-28 18:32:03 +00:00
#
2006-05-31 19:12:15 +00:00
# AC_WIRESHARK_IPV6_STACK
1999-03-28 18:32:03 +00:00
#
# By Jun-ichiro "itojun" Hagino, <itojun@iijlab.net>
2000-01-15 08:08:20 +00:00
#
2006-05-31 19:12:15 +00:00
AC_DEFUN([AC_WIRESHARK_IPV6_STACK],
1999-03-28 18:32:03 +00:00
[
v6type=unknown
v6lib=none
AC_MSG_CHECKING([ipv6 stack type])
2002-01-30 08:46:29 +00:00
for i in v6d toshiba kame inria zeta linux linux-glibc solaris8; do
1999-03-28 18:32:03 +00:00
case $i in
v6d)
2001-05-11 01:09:59 +00:00
AC_EGREP_CPP(yes, [
1999-03-28 18:32:03 +00:00
#include </usr/local/v6/include/sys/types.h>
#ifdef __V6D__
yes
#endif],
[v6type=$i; v6lib=v6;
v6libdir=/usr/local/v6/lib;
Put -D and -I flags into CPPFLAGS rather than into CFLAGS; that should
make them apply to C++ as well as C. That seems to be what the autoconf
documentation suggests:
- Variable: CFLAGS
Debugging and optimization options for the C compiler. If it is not set
in the environment when configure runs, the default value is set when
you call AC_PROG_CC (or empty if you don't). configure uses this
variable when compiling or linking programs to test for C features.
If a compiler option affects only the behavior of the preprocessor
(e.g., -Dname), it should be put into CPPFLAGS instead. If it affects
only the linker (e.g., -Ldirectory), it should be put into LDFLAGS
instead. If it affects only the compiler proper, CFLAGS is the natural
home for it. If an option affects multiple phases of the compiler,
though, matters get tricky. One approach to put such options directly
into CC, e.g., CC='gcc -m64'. Another is to put them into both CPPFLAGS
and LDFLAGS, but not into CFLAGS.
...
- Variable: CPPFLAGS
Preprocessor options for the C, C++, Objective C, and Objective C++
preprocessors and compilers. If it is not set in the environment when
configure runs, the default value is empty. configure uses this variable
when preprocessing or compiling programs to test for C, C++, Objective
C, and Objective C++ features.
This variable's contents should contain options like -I, -D, and -U that
affect only the behavior of the preprocessor. Please see the explanation
of CFLAGS for what you can do if an option affects other phases of the
compiler as well.
svn path=/trunk/; revision=41593
2012-03-16 03:27:45 +00:00
CPPFLAGS="-I/usr/local/v6/include $CPPFLAGS"])
1999-03-28 18:32:03 +00:00
;;
toshiba)
2001-05-11 01:09:59 +00:00
AC_EGREP_CPP(yes, [
1999-03-28 18:32:03 +00:00
#include <sys/param.h>
#ifdef _TOSHIBA_INET6
yes
#endif],
[v6type=$i; v6lib=inet6;
v6libdir=/usr/local/v6/lib;
Put -D and -I flags into CPPFLAGS rather than into CFLAGS; that should
make them apply to C++ as well as C. That seems to be what the autoconf
documentation suggests:
- Variable: CFLAGS
Debugging and optimization options for the C compiler. If it is not set
in the environment when configure runs, the default value is set when
you call AC_PROG_CC (or empty if you don't). configure uses this
variable when compiling or linking programs to test for C features.
If a compiler option affects only the behavior of the preprocessor
(e.g., -Dname), it should be put into CPPFLAGS instead. If it affects
only the linker (e.g., -Ldirectory), it should be put into LDFLAGS
instead. If it affects only the compiler proper, CFLAGS is the natural
home for it. If an option affects multiple phases of the compiler,
though, matters get tricky. One approach to put such options directly
into CC, e.g., CC='gcc -m64'. Another is to put them into both CPPFLAGS
and LDFLAGS, but not into CFLAGS.
...
- Variable: CPPFLAGS
Preprocessor options for the C, C++, Objective C, and Objective C++
preprocessors and compilers. If it is not set in the environment when
configure runs, the default value is empty. configure uses this variable
when preprocessing or compiling programs to test for C, C++, Objective
C, and Objective C++ features.
This variable's contents should contain options like -I, -D, and -U that
affect only the behavior of the preprocessor. Please see the explanation
of CFLAGS for what you can do if an option affects other phases of the
compiler as well.
svn path=/trunk/; revision=41593
2012-03-16 03:27:45 +00:00
CPPFLAGS="-DINET6 $CPPFLAGS"])
1999-03-28 18:32:03 +00:00
;;
kame)
2001-05-11 01:09:59 +00:00
AC_EGREP_CPP(yes, [
1999-03-28 18:32:03 +00:00
#include <netinet/in.h>
#ifdef __KAME__
yes
#endif],
[v6type=$i; v6lib=inet6;
v6libdir=/usr/local/v6/lib;
Put -D and -I flags into CPPFLAGS rather than into CFLAGS; that should
make them apply to C++ as well as C. That seems to be what the autoconf
documentation suggests:
- Variable: CFLAGS
Debugging and optimization options for the C compiler. If it is not set
in the environment when configure runs, the default value is set when
you call AC_PROG_CC (or empty if you don't). configure uses this
variable when compiling or linking programs to test for C features.
If a compiler option affects only the behavior of the preprocessor
(e.g., -Dname), it should be put into CPPFLAGS instead. If it affects
only the linker (e.g., -Ldirectory), it should be put into LDFLAGS
instead. If it affects only the compiler proper, CFLAGS is the natural
home for it. If an option affects multiple phases of the compiler,
though, matters get tricky. One approach to put such options directly
into CC, e.g., CC='gcc -m64'. Another is to put them into both CPPFLAGS
and LDFLAGS, but not into CFLAGS.
...
- Variable: CPPFLAGS
Preprocessor options for the C, C++, Objective C, and Objective C++
preprocessors and compilers. If it is not set in the environment when
configure runs, the default value is empty. configure uses this variable
when preprocessing or compiling programs to test for C, C++, Objective
C, and Objective C++ features.
This variable's contents should contain options like -I, -D, and -U that
affect only the behavior of the preprocessor. Please see the explanation
of CFLAGS for what you can do if an option affects other phases of the
compiler as well.
svn path=/trunk/; revision=41593
2012-03-16 03:27:45 +00:00
CPPFLAGS="-DINET6 $CPPFLAGS"])
1999-03-28 18:32:03 +00:00
;;
inria)
2001-05-11 01:09:59 +00:00
AC_EGREP_CPP(yes, [
1999-03-28 18:32:03 +00:00
#include <netinet/in.h>
#ifdef IPV6_INRIA_VERSION
yes
#endif],
Put -D and -I flags into CPPFLAGS rather than into CFLAGS; that should
make them apply to C++ as well as C. That seems to be what the autoconf
documentation suggests:
- Variable: CFLAGS
Debugging and optimization options for the C compiler. If it is not set
in the environment when configure runs, the default value is set when
you call AC_PROG_CC (or empty if you don't). configure uses this
variable when compiling or linking programs to test for C features.
If a compiler option affects only the behavior of the preprocessor
(e.g., -Dname), it should be put into CPPFLAGS instead. If it affects
only the linker (e.g., -Ldirectory), it should be put into LDFLAGS
instead. If it affects only the compiler proper, CFLAGS is the natural
home for it. If an option affects multiple phases of the compiler,
though, matters get tricky. One approach to put such options directly
into CC, e.g., CC='gcc -m64'. Another is to put them into both CPPFLAGS
and LDFLAGS, but not into CFLAGS.
...
- Variable: CPPFLAGS
Preprocessor options for the C, C++, Objective C, and Objective C++
preprocessors and compilers. If it is not set in the environment when
configure runs, the default value is empty. configure uses this variable
when preprocessing or compiling programs to test for C, C++, Objective
C, and Objective C++ features.
This variable's contents should contain options like -I, -D, and -U that
affect only the behavior of the preprocessor. Please see the explanation
of CFLAGS for what you can do if an option affects other phases of the
compiler as well.
svn path=/trunk/; revision=41593
2012-03-16 03:27:45 +00:00
[v6type=$i; CPPFLAGS="-DINET6 $CPPFLAGS"])
1999-03-28 18:32:03 +00:00
;;
zeta)
2001-05-11 01:09:59 +00:00
AC_EGREP_CPP(yes, [
1999-03-28 18:32:03 +00:00
#include <sys/param.h>
#ifdef _ZETA_MINAMI_INET6
yes
#endif],
[v6type=$i; v6lib=inet6;
v6libdir=/usr/local/v6/lib;
Put -D and -I flags into CPPFLAGS rather than into CFLAGS; that should
make them apply to C++ as well as C. That seems to be what the autoconf
documentation suggests:
- Variable: CFLAGS
Debugging and optimization options for the C compiler. If it is not set
in the environment when configure runs, the default value is set when
you call AC_PROG_CC (or empty if you don't). configure uses this
variable when compiling or linking programs to test for C features.
If a compiler option affects only the behavior of the preprocessor
(e.g., -Dname), it should be put into CPPFLAGS instead. If it affects
only the linker (e.g., -Ldirectory), it should be put into LDFLAGS
instead. If it affects only the compiler proper, CFLAGS is the natural
home for it. If an option affects multiple phases of the compiler,
though, matters get tricky. One approach to put such options directly
into CC, e.g., CC='gcc -m64'. Another is to put them into both CPPFLAGS
and LDFLAGS, but not into CFLAGS.
...
- Variable: CPPFLAGS
Preprocessor options for the C, C++, Objective C, and Objective C++
preprocessors and compilers. If it is not set in the environment when
configure runs, the default value is empty. configure uses this variable
when preprocessing or compiling programs to test for C, C++, Objective
C, and Objective C++ features.
This variable's contents should contain options like -I, -D, and -U that
affect only the behavior of the preprocessor. Please see the explanation
of CFLAGS for what you can do if an option affects other phases of the
compiler as well.
svn path=/trunk/; revision=41593
2012-03-16 03:27:45 +00:00
CPPFLAGS="-DINET6 $CPPFLAGS"])
1999-03-28 18:32:03 +00:00
;;
linux)
if test -d /usr/inet6; then
v6type=$i
v6lib=inet6
v6libdir=/usr/inet6
Put -D and -I flags into CPPFLAGS rather than into CFLAGS; that should
make them apply to C++ as well as C. That seems to be what the autoconf
documentation suggests:
- Variable: CFLAGS
Debugging and optimization options for the C compiler. If it is not set
in the environment when configure runs, the default value is set when
you call AC_PROG_CC (or empty if you don't). configure uses this
variable when compiling or linking programs to test for C features.
If a compiler option affects only the behavior of the preprocessor
(e.g., -Dname), it should be put into CPPFLAGS instead. If it affects
only the linker (e.g., -Ldirectory), it should be put into LDFLAGS
instead. If it affects only the compiler proper, CFLAGS is the natural
home for it. If an option affects multiple phases of the compiler,
though, matters get tricky. One approach to put such options directly
into CC, e.g., CC='gcc -m64'. Another is to put them into both CPPFLAGS
and LDFLAGS, but not into CFLAGS.
...
- Variable: CPPFLAGS
Preprocessor options for the C, C++, Objective C, and Objective C++
preprocessors and compilers. If it is not set in the environment when
configure runs, the default value is empty. configure uses this variable
when preprocessing or compiling programs to test for C, C++, Objective
C, and Objective C++ features.
This variable's contents should contain options like -I, -D, and -U that
affect only the behavior of the preprocessor. Please see the explanation
of CFLAGS for what you can do if an option affects other phases of the
compiler as well.
svn path=/trunk/; revision=41593
2012-03-16 03:27:45 +00:00
CPPFLAGS="-DINET6 $CPPFLAGS"
1999-03-28 18:32:03 +00:00
fi
;;
2001-07-09 23:42:39 +00:00
linux-glibc)
AC_EGREP_CPP(yes, [
#include <features.h>
#if defined(__GLIBC__) && defined(__GLIBC_MINOR__)
#if (__GLIBC__ == 2 && __GLIBC_MINOR__ >= 1) || __GLIBC__ > 2
yes
#endif
#endif],
Put -D and -I flags into CPPFLAGS rather than into CFLAGS; that should
make them apply to C++ as well as C. That seems to be what the autoconf
documentation suggests:
- Variable: CFLAGS
Debugging and optimization options for the C compiler. If it is not set
in the environment when configure runs, the default value is set when
you call AC_PROG_CC (or empty if you don't). configure uses this
variable when compiling or linking programs to test for C features.
If a compiler option affects only the behavior of the preprocessor
(e.g., -Dname), it should be put into CPPFLAGS instead. If it affects
only the linker (e.g., -Ldirectory), it should be put into LDFLAGS
instead. If it affects only the compiler proper, CFLAGS is the natural
home for it. If an option affects multiple phases of the compiler,
though, matters get tricky. One approach to put such options directly
into CC, e.g., CC='gcc -m64'. Another is to put them into both CPPFLAGS
and LDFLAGS, but not into CFLAGS.
...
- Variable: CPPFLAGS
Preprocessor options for the C, C++, Objective C, and Objective C++
preprocessors and compilers. If it is not set in the environment when
configure runs, the default value is empty. configure uses this variable
when preprocessing or compiling programs to test for C, C++, Objective
C, and Objective C++ features.
This variable's contents should contain options like -I, -D, and -U that
affect only the behavior of the preprocessor. Please see the explanation
of CFLAGS for what you can do if an option affects other phases of the
compiler as well.
svn path=/trunk/; revision=41593
2012-03-16 03:27:45 +00:00
[v6type=$i; v6lib=inet6; CPPFLAGS="-DINET6 $CPPFLAGS"])
2001-07-09 23:42:39 +00:00
;;
2002-01-30 08:46:29 +00:00
solaris8)
if test "`uname -s`" = "SunOS" && test "`uname -r`" = "5.8"; then
v6type=$i
v6lib=inet6
Put -D and -I flags into CPPFLAGS rather than into CFLAGS; that should
make them apply to C++ as well as C. That seems to be what the autoconf
documentation suggests:
- Variable: CFLAGS
Debugging and optimization options for the C compiler. If it is not set
in the environment when configure runs, the default value is set when
you call AC_PROG_CC (or empty if you don't). configure uses this
variable when compiling or linking programs to test for C features.
If a compiler option affects only the behavior of the preprocessor
(e.g., -Dname), it should be put into CPPFLAGS instead. If it affects
only the linker (e.g., -Ldirectory), it should be put into LDFLAGS
instead. If it affects only the compiler proper, CFLAGS is the natural
home for it. If an option affects multiple phases of the compiler,
though, matters get tricky. One approach to put such options directly
into CC, e.g., CC='gcc -m64'. Another is to put them into both CPPFLAGS
and LDFLAGS, but not into CFLAGS.
...
- Variable: CPPFLAGS
Preprocessor options for the C, C++, Objective C, and Objective C++
preprocessors and compilers. If it is not set in the environment when
configure runs, the default value is empty. configure uses this variable
when preprocessing or compiling programs to test for C, C++, Objective
C, and Objective C++ features.
This variable's contents should contain options like -I, -D, and -U that
affect only the behavior of the preprocessor. Please see the explanation
of CFLAGS for what you can do if an option affects other phases of the
compiler as well.
svn path=/trunk/; revision=41593
2012-03-16 03:27:45 +00:00
[CPPFLAGS="-DINET6 -DSOLARIS8_INET6 $CPPFLAGS"]
2002-01-30 08:46:29 +00:00
fi
2008-10-24 18:08:32 +00:00
;;
1999-03-28 18:32:03 +00:00
esac
if test "$v6type" != "unknown"; then
break
fi
done
if test "$v6lib" != "none"; then
for dir in $v6libdir /usr/local/v6/lib /usr/local/lib; do
if test -d $dir -a -f $dir/lib$v6lib.a; then
1999-10-12 23:12:06 +00:00
LIBS="-L$dir $LIBS -l$v6lib"
1999-03-28 18:32:03 +00:00
break
fi
done
enable_ipv6="yes"
else
enable_ipv6="no"
fi
AC_MSG_RESULT(["$v6type, $v6lib"])
])
1999-07-13 02:53:26 +00:00
2000-01-15 08:08:20 +00:00
#
2006-05-31 19:12:15 +00:00
# AC_WIRESHARK_GETHOSTBY_LIB_CHECK
2000-01-15 08:08:20 +00:00
#
# Checks whether we need "-lnsl" to get "gethostby*()", which we use
# in "resolv.c".
#
# Adapted from stuff in the AC_PATH_XTRA macro in "acspecific.m4" in
# GNU Autoconf 2.13; the comment came from there.
2008-10-24 18:08:32 +00:00
# Done by Guy Harris <guy@alum.mit.edu> on 2000-01-14.
2000-01-15 08:08:20 +00:00
#
2006-05-31 19:12:15 +00:00
AC_DEFUN([AC_WIRESHARK_GETHOSTBY_LIB_CHECK],
2000-01-15 08:08:20 +00:00
[
# msh@cis.ufl.edu says -lnsl (and -lsocket) are needed for his 386/AT,
# to get the SysV transport functions.
# chad@anasazi.com says the Pyramid MIS-ES running DC/OSx (SVR4)
# needs -lnsl.
# The nsl library prevents programs from opening the X display
# on Irix 5.2, according to dickey@clark.net.
2002-01-03 20:09:55 +00:00
AC_CHECK_FUNC(gethostbyname, ,
AC_CHECK_LIB(nsl, gethostbyname, NSL_LIBS="-lnsl"))
2000-01-15 08:08:20 +00:00
AC_SUBST(NSL_LIBS)
])
#
2006-05-31 19:12:15 +00:00
# AC_WIRESHARK_SOCKET_LIB_CHECK
2000-01-15 08:08:20 +00:00
#
# Checks whether we need "-lsocket" to get "socket()", which is used
# by libpcap on some platforms - and, in effect, "gethostby*()" on
# most if not all platforms (so that it can use NIS or DNS or...
# to look up host names).
#
# Adapted from stuff in the AC_PATH_XTRA macro in "acspecific.m4" in
# GNU Autoconf 2.13; the comment came from there.
2008-10-24 18:08:32 +00:00
# Done by Guy Harris <guy@alum.mit.edu> on 2000-01-14.
2000-01-15 08:08:20 +00:00
#
# We use "connect" because that's what AC_PATH_XTRA did.
#
2006-05-31 19:12:15 +00:00
AC_DEFUN([AC_WIRESHARK_SOCKET_LIB_CHECK],
2000-01-15 08:08:20 +00:00
[
# lieder@skyler.mavd.honeywell.com says without -lsocket,
# socket/setsockopt and other routines are undefined under SCO ODT
# 2.0. But -lsocket is broken on IRIX 5.2 (and is not necessary
# on later versions), says simon@lia.di.epfl.ch: it contains
# gethostby* variants that don't use the nameserver (or something).
# -lsocket must be given before -lnsl if both are needed.
# We assume that if connect needs -lnsl, so does gethostbyname.
2002-01-03 20:09:55 +00:00
AC_CHECK_FUNC(connect, ,
2000-01-15 08:08:20 +00:00
AC_CHECK_LIB(socket, connect, SOCKET_LIBS="-lsocket",
2002-01-03 20:09:55 +00:00
AC_MSG_ERROR(Function 'socket' not found.), $NSL_LIBS))
2000-01-15 08:08:20 +00:00
AC_SUBST(SOCKET_LIBS)
])
2007-04-22 13:38:50 +00:00
#
# AC_WIRESHARK_BREAKLOOP_TRY_LINK
#
AC_DEFUN([AC_WIRESHARK_PCAP_BREAKLOOP_TRY_LINK],
[
AC_LINK_IFELSE(
[
AC_LANG_SOURCE(
[[
# include <pcap.h>
int main(void)
{
pcap_t *pct = NULL;
pcap_breakloop(pct);
return 0;
}
]])
],
[
ws_breakloop_compiled=yes
],
[
ws_breakloop_compiled=no
])
])
1999-07-13 02:53:26 +00:00
#
2006-05-31 19:12:15 +00:00
# AC_WIRESHARK_PCAP_CHECK
1999-07-13 02:53:26 +00:00
#
2006-05-31 19:12:15 +00:00
AC_DEFUN([AC_WIRESHARK_PCAP_CHECK],
1999-07-13 02:53:26 +00:00
[
2001-06-27 07:47:50 +00:00
if test -z "$pcap_dir"
then
2003-01-21 20:38:32 +00:00
# Pcap header checks
# XXX need to set a var AC_CHECK_HEADER(pcap.h,,)
2001-06-27 07:47:50 +00:00
#
2009-06-08 02:12:23 +00:00
# The user didn't specify a directory in which libpcap resides.
# First, look for a pcap-config script.
2001-06-27 07:47:50 +00:00
#
2009-06-08 02:12:23 +00:00
AC_PATH_PROG(PCAP_CONFIG, pcap-config)
2009-06-08 17:23:00 +00:00
if test -n "$PCAP_CONFIG" ; then
2010-02-19 00:15:29 +00:00
#
# Found it.
#
# Now check whether it's the libpcap 1.0 version, which
# put a space after "-L" - on some platforms, that doesn't
# work.
#
AC_MSG_CHECKING(for broken pcap-config)
2009-06-08 17:23:00 +00:00
case "`\"$PCAP_CONFIG\" --libs`" in
"-L "*)
#
# Space after -L. Pretend pcap-config doesn't exist.
#
AC_MSG_RESULT(yes)
PCAP_CONFIG=""
;;
*)
#
# No space after -L.
#
AC_MSG_RESULT(no)
;;
esac
fi
2009-06-08 02:12:23 +00:00
if test -n "$PCAP_CONFIG" ; then
#
2010-02-19 00:15:29 +00:00
# Found it, and it's usable; use it to get the include flags
# for libpcap.
2009-06-08 02:12:23 +00:00
#
CPPFLAGS="$CPPFLAGS `\"$PCAP_CONFIG\" --cflags`"
2011-04-28 02:24:46 +00:00
else
2009-06-08 02:12:23 +00:00
#
# Didn't find it; we have to look for libpcap ourselves.
# We assume that the current library search path will work,
# but we may have to look for the header in a "pcap"
# subdirectory of "/usr/include" or "/usr/local/include",
# as some systems apparently put "pcap.h" in a "pcap"
# subdirectory, and we also check "$prefix/include" - and
# "$prefix/include/pcap", in case $prefix is set to
# "/usr/include" or "/usr/local/include".
#
# XXX - should we just add "$prefix/include" to the include
# search path and "$prefix/lib" to the library search path?
#
AC_MSG_CHECKING(for extraneous pcap header directories)
found_pcap_dir=""
pcap_dir_list="/usr/include/pcap $prefix/include/pcap $prefix/include"
if test "x$ac_cv_enable_usr_local" = "xyes" ; then
pcap_dir_list="$pcap_dir_list /usr/local/include/pcap"
fi
for pcap_dir in $pcap_dir_list
do
if test -d $pcap_dir ; then
2003-01-21 20:38:32 +00:00
if test x$pcap_dir != x/usr/include -a x$pcap_dir != x/usr/local/include ; then
2002-07-06 20:40:50 +00:00
CPPFLAGS="$CPPFLAGS -I$pcap_dir"
fi
2001-06-27 07:47:50 +00:00
found_pcap_dir=" $found_pcap_dir -I$pcap_dir"
2003-01-21 20:38:32 +00:00
break
2009-06-08 02:12:23 +00:00
fi
done
1999-07-13 02:53:26 +00:00
2009-06-08 02:12:23 +00:00
if test "$found_pcap_dir" != "" ; then
AC_MSG_RESULT(found --$found_pcap_dir added to CFLAGS)
else
AC_MSG_RESULT(not found)
fi
2001-06-27 07:47:50 +00:00
fi
1999-07-13 02:53:26 +00:00
else
2001-06-27 07:47:50 +00:00
#
# The user specified a directory in which libpcap resides,
2001-07-27 07:10:13 +00:00
# so add the "include" subdirectory of that directory to
# the include file search path and the "lib" subdirectory
# of that directory to the library search path.
2001-06-27 07:47:50 +00:00
#
# XXX - if there's also a libpcap in a directory that's
Put -D and -I flags into CPPFLAGS rather than into CFLAGS; that should
make them apply to C++ as well as C. That seems to be what the autoconf
documentation suggests:
- Variable: CFLAGS
Debugging and optimization options for the C compiler. If it is not set
in the environment when configure runs, the default value is set when
you call AC_PROG_CC (or empty if you don't). configure uses this
variable when compiling or linking programs to test for C features.
If a compiler option affects only the behavior of the preprocessor
(e.g., -Dname), it should be put into CPPFLAGS instead. If it affects
only the linker (e.g., -Ldirectory), it should be put into LDFLAGS
instead. If it affects only the compiler proper, CFLAGS is the natural
home for it. If an option affects multiple phases of the compiler,
though, matters get tricky. One approach to put such options directly
into CC, e.g., CC='gcc -m64'. Another is to put them into both CPPFLAGS
and LDFLAGS, but not into CFLAGS.
...
- Variable: CPPFLAGS
Preprocessor options for the C, C++, Objective C, and Objective C++
preprocessors and compilers. If it is not set in the environment when
configure runs, the default value is empty. configure uses this variable
when preprocessing or compiling programs to test for C, C++, Objective
C, and Objective C++ features.
This variable's contents should contain options like -I, -D, and -U that
affect only the behavior of the preprocessor. Please see the explanation
of CFLAGS for what you can do if an option affects other phases of the
compiler as well.
svn path=/trunk/; revision=41593
2012-03-16 03:27:45 +00:00
# already in CPPFLAGS or LDFLAGS, this won't make us find
# the version in the specified directory, as the compiler
# and/or linker will search that other directory before it
# searches the specified directory.
2001-06-27 07:47:50 +00:00
#
2001-07-27 07:10:13 +00:00
CPPFLAGS="$CPPFLAGS -I$pcap_dir/include"
2006-05-31 19:12:15 +00:00
AC_WIRESHARK_ADD_DASH_L(LDFLAGS, $pcap_dir/lib)
1999-07-13 02:53:26 +00:00
fi
2003-02-11 02:31:22 +00:00
# Pcap header check
2008-10-24 18:08:32 +00:00
AC_CHECK_HEADER(pcap.h,,
2003-02-11 02:31:22 +00:00
AC_MSG_ERROR([[Header file pcap.h not found; if you installed libpcap
2002-12-28 23:15:52 +00:00
from source, did you also do \"make install-incl\", and if you installed a
binary package of libpcap, is there also a developer's package of libpcap,
and did you also install that package?]]))
2000-01-15 09:46:28 +00:00
2009-06-08 02:12:23 +00:00
if test -n "$PCAP_CONFIG" ; then
#
# We have pcap-config; we assume that means we have libpcap
# installed and that pcap-config will tell us whatever
# libraries libpcap needs.
#
if test x$enable_static = xyes; then
PCAP_LIBS="`\"$PCAP_CONFIG\" --libs --static`"
else
PCAP_LIBS="`\"$PCAP_CONFIG\" --libs`"
fi
AC_DEFINE(HAVE_LIBPCAP, 1, [Define to use libpcap library])
else
#
# Check to see if we find "pcap_open_live" in "-lpcap".
# Also check for various additional libraries that libpcap might
# require.
#
AC_CHECK_LIB(pcap, pcap_open_live,
[
PCAP_LIBS=-lpcap
AC_DEFINE(HAVE_LIBPCAP, 1, [Define to use libpcap library])
], [
ac_wireshark_extras_found=no
ac_save_LIBS="$LIBS"
for extras in "-lcfg -lodm" "-lpfring"
do
2006-04-25 18:01:43 +00:00
AC_MSG_CHECKING([for pcap_open_live in -lpcap with $extras])
LIBS="-lpcap $extras"
#
# XXX - can't we use AC_CHECK_LIB here?
#
AC_TRY_LINK(
[
2004-02-26 09:39:43 +00:00
# include <pcap.h>
2006-04-25 18:01:43 +00:00
],
[
2004-02-26 09:39:43 +00:00
pcap_open_live(NULL, 0, 0, 0, NULL);
2006-04-25 18:01:43 +00:00
],
[
2006-05-31 19:12:15 +00:00
ac_wireshark_extras_found=yes
2006-04-25 18:01:43 +00:00
AC_MSG_RESULT([yes])
PCAP_LIBS="-lpcap $extras"
AC_DEFINE(HAVE_LIBPCAP, 1, [Define to use libpcap library])
],
[
AC_MSG_RESULT([no])
])
2006-05-31 19:12:15 +00:00
if test x$ac_wireshark_extras_found = xyes
2006-04-25 18:01:43 +00:00
then
break
fi
2009-06-08 02:12:23 +00:00
done
if test x$ac_wireshark_extras_found = xno
then
2006-04-25 18:01:43 +00:00
AC_MSG_ERROR([Can't link with library libpcap.])
2009-06-08 02:12:23 +00:00
fi
LIBS=$ac_save_LIBS
], $SOCKET_LIBS $NSL_LIBS)
fi
2000-01-15 09:46:28 +00:00
AC_SUBST(PCAP_LIBS)
1999-07-13 02:53:26 +00:00
2003-10-10 03:04:38 +00:00
#
# Check whether various variables and functions are defined by
# libpcap.
#
2001-07-27 07:10:13 +00:00
ac_save_LIBS="$LIBS"
2001-07-27 19:14:59 +00:00
LIBS="$PCAP_LIBS $SOCKET_LIBS $NSL_LIBS $LIBS"
2007-04-22 13:38:50 +00:00
AC_CHECK_FUNCS(pcap_open_dead pcap_freecode)
#
2008-02-07 18:19:08 +00:00
# pcap_breakloop may be present in the library but not declared
# in the pcap.h header file. If it's not declared in the header
# file, attempts to use it will get warnings, and, if we're
# building with warnings treated as errors, that warning will
# cause compilation to fail.
#
# We are therefore first testing whether the function is present
# and then, if we're compiling with warnings as errors, testing
# whether it is usable. It is usable if it compiles without
# a -Wimplicit warning (the "compile with warnings as errors"
# option requires GCC). If it is not usable, we fail and tell
# the user that the pcap.h header needs to be updated.
2008-10-24 18:08:32 +00:00
#
2008-02-07 18:19:08 +00:00
# Ceteris paribus, this should only happen with Mac OS X 10.3[.x] which
2007-04-22 13:38:50 +00:00
# can have an up-to-date pcap library without the corresponding pcap
# header.
#
# However, it might also happen on some others OSes with some erroneous
2008-10-24 18:08:32 +00:00
# system manipulations where multiple versions of libcap might co-exist
2007-04-22 13:38:50 +00:00
# e.g. hand made symbolic link from libpcap.so -> libpcap.so.0.8 but
# having the pcap header version 0.7.
#
2008-02-07 18:19:08 +00:00
AC_MSG_CHECKING([whether pcap_breakloop is present])
2007-04-22 13:38:50 +00:00
ac_CFLAGS_saved="$CFLAGS"
AC_WIRESHARK_PCAP_BREAKLOOP_TRY_LINK
if test "x$ws_breakloop_compiled" = "xyes"; then
2008-02-07 18:19:08 +00:00
AC_MSG_RESULT(yes)
AC_DEFINE(HAVE_PCAP_BREAKLOOP, 1, [Define if pcap_breakloop is known])
if test "x$with_warnings_as_errors" = "xyes"; then
AC_MSG_CHECKING([whether pcap_breakloop is usable])
CFLAGS="$CFLAGS -Werror -Wimplicit"
AC_WIRESHARK_PCAP_BREAKLOOP_TRY_LINK
if test "x$ws_breakloop_compiled" = "xyes"; then
AC_MSG_RESULT(yes)
else
AC_MSG_RESULT(no)
AC_MSG_ERROR(
[Your pcap library is more recent than your pcap header.
As you are building with compiler warnings treated as errors, Wireshark
won't be able to use functions not declared in that header.
If you wish to build with compiler warnings treated as errors, You should
install a newer version of the header file.])
fi
CFLAGS="$ac_CFLAGS_saved"
2007-04-22 13:38:50 +00:00
fi
else
2008-02-07 18:19:08 +00:00
AC_MSG_RESULT(no)
2007-04-22 13:38:50 +00:00
fi
For "pcap_findalldevs()", don't assume that just because it's in -lpcap
it's usable - one of the updates to OS X 10.3 updated libpcap to
0.8[.x], so that it had "pcap_findalldevs()", but didn't update
"pcap.h", so it didn't declare "pcap_if_t", so you couldn't actually
*use* it. You can work around that by installing the pcap.h (and
pcap-bpf.h) from the matching tcpdump.org release, but, as even when
that version of OS X is pre-installed rather than being the result of a
Software Update, you still don't get the new "pcap.h" (at least I didn't
get it on my PowerBook with 10.3.4). Therefore, we check whether a
program that calls "pcap_findalldevs()" *and* declares a "pcap_if_t *"
to pass to it can be compiled and linked with -lpcap, and only declare
HAVE_PCAP_FINDALLDEVS if we can.
Also, don't check for the functions added to libpcap after
"pcap_findalldevs()" was added unless we have a usable
"pcap_findalldevs()", as, if not, those functions won't be declared in
"pcap.h" either, so we'll get compiler warnings.
svn path=/trunk/; revision=11745
2004-08-16 01:11:23 +00:00
#
# Later versions of Mac OS X 10.3[.x] ship a pcap.h that
# doesn't define pcap_if_t but ship an 0.8[.x] libpcap,
# so the library has "pcap_findalldevs()", but pcap.h
# doesn't define "pcap_if_t" so you can't actually *use*
# "pcap_findalldevs()".
#
# That even appears to be true of systems shipped with
# 10.3.4, so it doesn't appear only to be a case of
# Software Update not updating header files.
#
# (You can work around this by installing the 0.8 header
# files.)
#
AC_CACHE_CHECK([whether pcap_findalldevs is present and usable],
[ac_cv_func_pcap_findalldevs],
[
AC_LINK_IFELSE(
[
AC_LANG_SOURCE(
[[
#include <pcap.h>
main()
{
pcap_if_t *devpointer;
char errbuf[1];
pcap_findalldevs(&devpointer, errbuf);
}
]])
],
[
ac_cv_func_pcap_findalldevs=yes
],
[
ac_cv_func_pcap_findalldevs=no
])
])
#
# Don't check for other new routines that showed up after
# "pcap_findalldevs()" if we don't have a usable
# "pcap_findalldevs()", so we don't end up using them if the
# "pcap.h" is crufty and old and doesn't declare them.
#
if test $ac_cv_func_pcap_findalldevs = "yes" ; then
AC_DEFINE(HAVE_PCAP_FINDALLDEVS, 1,
2004-08-16 02:23:41 +00:00
[Define to 1 if you have the `pcap_findalldevs' function and a pcap.h that declares pcap_if_t.])
For "pcap_findalldevs()", don't assume that just because it's in -lpcap
it's usable - one of the updates to OS X 10.3 updated libpcap to
0.8[.x], so that it had "pcap_findalldevs()", but didn't update
"pcap.h", so it didn't declare "pcap_if_t", so you couldn't actually
*use* it. You can work around that by installing the pcap.h (and
pcap-bpf.h) from the matching tcpdump.org release, but, as even when
that version of OS X is pre-installed rather than being the result of a
Software Update, you still don't get the new "pcap.h" (at least I didn't
get it on my PowerBook with 10.3.4). Therefore, we check whether a
program that calls "pcap_findalldevs()" *and* declares a "pcap_if_t *"
to pass to it can be compiled and linked with -lpcap, and only declare
HAVE_PCAP_FINDALLDEVS if we can.
Also, don't check for the functions added to libpcap after
"pcap_findalldevs()" was added unless we have a usable
"pcap_findalldevs()", as, if not, those functions won't be declared in
"pcap.h" either, so we'll get compiler warnings.
svn path=/trunk/; revision=11745
2004-08-16 01:11:23 +00:00
AC_CHECK_FUNCS(pcap_datalink_val_to_name pcap_datalink_name_to_val)
2008-12-21 23:22:12 +00:00
AC_CHECK_FUNCS(pcap_datalink_val_to_description)
For "pcap_findalldevs()", don't assume that just because it's in -lpcap
it's usable - one of the updates to OS X 10.3 updated libpcap to
0.8[.x], so that it had "pcap_findalldevs()", but didn't update
"pcap.h", so it didn't declare "pcap_if_t", so you couldn't actually
*use* it. You can work around that by installing the pcap.h (and
pcap-bpf.h) from the matching tcpdump.org release, but, as even when
that version of OS X is pre-installed rather than being the result of a
Software Update, you still don't get the new "pcap.h" (at least I didn't
get it on my PowerBook with 10.3.4). Therefore, we check whether a
program that calls "pcap_findalldevs()" *and* declares a "pcap_if_t *"
to pass to it can be compiled and linked with -lpcap, and only declare
HAVE_PCAP_FINDALLDEVS if we can.
Also, don't check for the functions added to libpcap after
"pcap_findalldevs()" was added unless we have a usable
"pcap_findalldevs()", as, if not, those functions won't be declared in
"pcap.h" either, so we'll get compiler warnings.
svn path=/trunk/; revision=11745
2004-08-16 01:11:23 +00:00
AC_CHECK_FUNCS(pcap_list_datalinks pcap_set_datalink pcap_lib_version)
2008-07-04 03:33:00 +00:00
AC_CHECK_FUNCS(pcap_get_selectable_fd pcap_free_datalinks)
2010-07-13 23:26:07 +00:00
AC_CHECK_FUNCS(pcap_create bpf_image)
For "pcap_findalldevs()", don't assume that just because it's in -lpcap
it's usable - one of the updates to OS X 10.3 updated libpcap to
0.8[.x], so that it had "pcap_findalldevs()", but didn't update
"pcap.h", so it didn't declare "pcap_if_t", so you couldn't actually
*use* it. You can work around that by installing the pcap.h (and
pcap-bpf.h) from the matching tcpdump.org release, but, as even when
that version of OS X is pre-installed rather than being the result of a
Software Update, you still don't get the new "pcap.h" (at least I didn't
get it on my PowerBook with 10.3.4). Therefore, we check whether a
program that calls "pcap_findalldevs()" *and* declares a "pcap_if_t *"
to pass to it can be compiled and linked with -lpcap, and only declare
HAVE_PCAP_FINDALLDEVS if we can.
Also, don't check for the functions added to libpcap after
"pcap_findalldevs()" was added unless we have a usable
"pcap_findalldevs()", as, if not, those functions won't be declared in
"pcap.h" either, so we'll get compiler warnings.
svn path=/trunk/; revision=11745
2004-08-16 01:11:23 +00:00
fi
2003-10-10 03:04:38 +00:00
LIBS="$ac_save_LIBS"
2001-07-27 07:10:13 +00:00
])
2007-12-04 11:19:29 +00:00
AC_DEFUN([AC_WIRESHARK_PCAP_REMOTE_CHECK],
[
ac_save_LIBS="$LIBS"
LIBS="$PCAP_LIBS $SOCKET_LIBS $NSL_LIBS $LIBS"
AC_DEFINE(HAVE_REMOTE, 1, [Define to 1 to enable remote
capturing feature in WinPcap library])
AC_CHECK_FUNCS(pcap_open pcap_findalldevs_ex pcap_createsrcstr)
if test $ac_cv_func_pcap_open = "yes" -a \
$ac_cv_func_pcap_findalldevs_ex = "yes" -a \
$ac_cv_func_pcap_createsrcstr = "yes" ; then
AC_DEFINE(HAVE_PCAP_REMOTE, 1,
[Define to 1 if you have WinPcap remote capturing support and prefer to use these new API features.])
fi
AC_CHECK_FUNCS(pcap_setsampling)
LIBS="$ac_save_LIBS"
])
1999-09-22 01:26:50 +00:00
#
2006-05-31 19:12:15 +00:00
# AC_WIRESHARK_ZLIB_CHECK
1999-09-22 01:26:50 +00:00
#
2006-05-31 19:12:15 +00:00
AC_DEFUN([AC_WIRESHARK_ZLIB_CHECK],
1999-09-22 01:26:50 +00:00
[
2002-04-08 01:34:39 +00:00
if test "x$zlib_dir" != "x"
then
#
# The user specified a directory in which zlib resides,
# so add the "include" subdirectory of that directory to
# the include file search path and the "lib" subdirectory
# of that directory to the library search path.
#
# XXX - if there's also a zlib in a directory that's
Put -D and -I flags into CPPFLAGS rather than into CFLAGS; that should
make them apply to C++ as well as C. That seems to be what the autoconf
documentation suggests:
- Variable: CFLAGS
Debugging and optimization options for the C compiler. If it is not set
in the environment when configure runs, the default value is set when
you call AC_PROG_CC (or empty if you don't). configure uses this
variable when compiling or linking programs to test for C features.
If a compiler option affects only the behavior of the preprocessor
(e.g., -Dname), it should be put into CPPFLAGS instead. If it affects
only the linker (e.g., -Ldirectory), it should be put into LDFLAGS
instead. If it affects only the compiler proper, CFLAGS is the natural
home for it. If an option affects multiple phases of the compiler,
though, matters get tricky. One approach to put such options directly
into CC, e.g., CC='gcc -m64'. Another is to put them into both CPPFLAGS
and LDFLAGS, but not into CFLAGS.
...
- Variable: CPPFLAGS
Preprocessor options for the C, C++, Objective C, and Objective C++
preprocessors and compilers. If it is not set in the environment when
configure runs, the default value is empty. configure uses this variable
when preprocessing or compiling programs to test for C, C++, Objective
C, and Objective C++ features.
This variable's contents should contain options like -I, -D, and -U that
affect only the behavior of the preprocessor. Please see the explanation
of CFLAGS for what you can do if an option affects other phases of the
compiler as well.
svn path=/trunk/; revision=41593
2012-03-16 03:27:45 +00:00
# already in CPPFLAGS or LDFLAGS, this won't make us find
# the version in the specified directory, as the compiler
# and/or linker will search that other directory before it
# searches the specified directory.
2002-04-08 01:34:39 +00:00
#
2006-05-31 19:12:15 +00:00
wireshark_save_CPPFLAGS="$CPPFLAGS"
2002-04-08 01:34:39 +00:00
CPPFLAGS="$CPPFLAGS -I$zlib_dir/include"
2006-05-31 19:12:15 +00:00
wireshark_save_LIBS="$LIBS"
AC_WIRESHARK_ADD_DASH_L(LIBS, $zlib_dir/lib)
2002-04-08 01:34:39 +00:00
fi
2001-08-21 06:52:25 +00:00
#
# Make sure we have "zlib.h". If we don't, it means we probably
# don't have zlib, so don't use it.
#
2002-04-08 01:34:39 +00:00
AC_CHECK_HEADER(zlib.h,,
[
if test "x$zlib_dir" != "x"
then
#
# The user used "--with-zlib=" to specify a directory
# containing zlib, but we didn't find the header file
# there; that either means they didn't specify the
# right directory or are confused about whether zlib
# is, in fact, installed. Report the error and give up.
#
AC_MSG_ERROR([zlib header not found in directory specified in --with-zlib])
else
if test "x$want_zlib" = "xyes"
then
#
# The user tried to force us to use the library, but we
# couldn't find the header file; report an error.
#
AC_MSG_ERROR(Header file zlib.h not found.)
else
#
# We couldn't find the header file; don't use the
# library, as it's probably not present.
#
want_zlib=no
fi
fi
])
1999-11-29 05:10:18 +00:00
2002-04-08 01:34:39 +00:00
if test "x$want_zlib" != "xno"
If there's no "zlib.h" header, we won't be using zlib, so don't bother
checking for "gzgets()" in zlib.
If there is a "zlib.h" header, and there is a "gzgets()" in zlib, check
whether we find "gzgets()" in zlib when we link with the GTK+ link
flags, and, if not, fail. People often grab XFree86 source and build
and install it on their systems, and they appear sometimes to
misconfigure XFree86 so that, even on systems with zlib, it assumes
there is no zlib, so the XFree86 build process builds and installs its
own "mini-zlib" in the X11 library directory. The "mini-zlib" lacks
"gzgets()", and that's the zlib with which Ethereal gets linked, so the
build of Ethereal fails.
svn path=/trunk/; revision=3849
2001-08-18 20:09:44 +00:00
then
#
# Well, we at least have the zlib header file.
2011-05-03 04:48:02 +00:00
# We link with zlib to support uncompression of
# gzipped network traffic, e.g. in an HTTP request
# or response body.
If there's no "zlib.h" header, we won't be using zlib, so don't bother
checking for "gzgets()" in zlib.
If there is a "zlib.h" header, and there is a "gzgets()" in zlib, check
whether we find "gzgets()" in zlib when we link with the GTK+ link
flags, and, if not, fail. People often grab XFree86 source and build
and install it on their systems, and they appear sometimes to
misconfigure XFree86 so that, even on systems with zlib, it assumes
there is no zlib, so the XFree86 build process builds and installs its
own "mini-zlib" in the X11 library directory. The "mini-zlib" lacks
"gzgets()", and that's the zlib with which Ethereal gets linked, so the
build of Ethereal fails.
svn path=/trunk/; revision=3849
2001-08-18 20:09:44 +00:00
#
2011-05-03 04:48:02 +00:00
if test "x$zlib_dir" != "x"
then
#
Put -D and -I flags into CPPFLAGS rather than into CFLAGS; that should
make them apply to C++ as well as C. That seems to be what the autoconf
documentation suggests:
- Variable: CFLAGS
Debugging and optimization options for the C compiler. If it is not set
in the environment when configure runs, the default value is set when
you call AC_PROG_CC (or empty if you don't). configure uses this
variable when compiling or linking programs to test for C features.
If a compiler option affects only the behavior of the preprocessor
(e.g., -Dname), it should be put into CPPFLAGS instead. If it affects
only the linker (e.g., -Ldirectory), it should be put into LDFLAGS
instead. If it affects only the compiler proper, CFLAGS is the natural
home for it. If an option affects multiple phases of the compiler,
though, matters get tricky. One approach to put such options directly
into CC, e.g., CC='gcc -m64'. Another is to put them into both CPPFLAGS
and LDFLAGS, but not into CFLAGS.
...
- Variable: CPPFLAGS
Preprocessor options for the C, C++, Objective C, and Objective C++
preprocessors and compilers. If it is not set in the environment when
configure runs, the default value is empty. configure uses this variable
when preprocessing or compiling programs to test for C, C++, Objective
C, and Objective C++ features.
This variable's contents should contain options like -I, -D, and -U that
affect only the behavior of the preprocessor. Please see the explanation
of CFLAGS for what you can do if an option affects other phases of the
compiler as well.
svn path=/trunk/; revision=41593
2012-03-16 03:27:45 +00:00
# Put the "-L" flags for zlib at the beginning
# of LIBS.
2011-05-03 04:48:02 +00:00
#
LIBS=""
AC_WIRESHARK_ADD_DASH_L(LIBS, $zlib_dir/lib)
LIBS="$LIBS -lz $wireshark_save_LIBS"
else
LIBS="-lz $LIBS"
fi
AC_DEFINE(HAVE_LIBZ, 1, [Define to use libz library])
2002-01-18 08:28:22 +00:00
#
2011-05-03 04:48:02 +00:00
# Check for "inflatePrime()" in zlib, which we need
# in order to read compressed capture files.
2002-01-18 08:28:22 +00:00
#
2011-05-03 04:48:02 +00:00
AC_CHECK_FUNCS(inflatePrime)
if test "x$ac_cv_func_inflatePrime" = "xyes" ; then
#
# Now check for "inflatePrime()" in zlib when
# linking with the linker flags for GTK+
# applications; people often grab XFree86 source
# and build and install it on their systems,
# and they appear sometimes to misconfigure
# XFree86 so that, even on systems with zlib,
# it assumes there is no zlib, so the XFree86
# build process builds and installs its
# own zlib in the X11 library directory.
#
# The zlib in at least some versions of XFree86
# is an older version that may lack "inflatePrime()",
# and that's the zlib with which Wireshark gets
# linked, so the build of Wireshark fails.
#
AC_MSG_CHECKING([for inflatePrime missing when linking with X11])
AC_TRY_LINK_FUNC(inflatePrime, AC_MSG_RESULT(no),
[
AC_MSG_RESULT(yes)
AC_MSG_ERROR(old zlib found when linking with X11 - get rid of old zlib.)
])
fi
else
2002-01-18 08:28:22 +00:00
#
Put -D and -I flags into CPPFLAGS rather than into CFLAGS; that should
make them apply to C++ as well as C. That seems to be what the autoconf
documentation suggests:
- Variable: CFLAGS
Debugging and optimization options for the C compiler. If it is not set
in the environment when configure runs, the default value is set when
you call AC_PROG_CC (or empty if you don't). configure uses this
variable when compiling or linking programs to test for C features.
If a compiler option affects only the behavior of the preprocessor
(e.g., -Dname), it should be put into CPPFLAGS instead. If it affects
only the linker (e.g., -Ldirectory), it should be put into LDFLAGS
instead. If it affects only the compiler proper, CFLAGS is the natural
home for it. If an option affects multiple phases of the compiler,
though, matters get tricky. One approach to put such options directly
into CC, e.g., CC='gcc -m64'. Another is to put them into both CPPFLAGS
and LDFLAGS, but not into CFLAGS.
...
- Variable: CPPFLAGS
Preprocessor options for the C, C++, Objective C, and Objective C++
preprocessors and compilers. If it is not set in the environment when
configure runs, the default value is empty. configure uses this variable
when preprocessing or compiling programs to test for C, C++, Objective
C, and Objective C++ features.
This variable's contents should contain options like -I, -D, and -U that
affect only the behavior of the preprocessor. Please see the explanation
of CFLAGS for what you can do if an option affects other phases of the
compiler as well.
svn path=/trunk/; revision=41593
2012-03-16 03:27:45 +00:00
# Restore the versions of CPPFLAGS and LIBS before
# we added the "-with-zlib=" directory, as we didn't
# actually find zlib there.
2002-01-18 08:28:22 +00:00
#
2011-05-03 04:48:02 +00:00
CPPFLAGS="$wireshark_save_CPPFLAGS"
LIBS="$wireshark_save_LIBS"
want_zlib=no
2002-01-18 08:28:22 +00:00
fi
1999-09-22 01:26:50 +00:00
])
2006-01-31 22:22:05 +00:00
#
2006-05-31 19:12:15 +00:00
# AC_WIRESHARK_LIBLUA_CHECK
2006-01-31 22:22:05 +00:00
#
2006-05-31 19:12:15 +00:00
AC_DEFUN([AC_WIRESHARK_LIBLUA_CHECK],[
2006-01-31 22:22:05 +00:00
if test "x$lua_dir" != "x"
then
#
# The user specified a directory in which liblua resides,
# so add the "include" subdirectory of that directory to
# the include file search path and the "lib" subdirectory
# of that directory to the library search path.
#
# XXX - if there's also a liblua in a directory that's
Put -D and -I flags into CPPFLAGS rather than into CFLAGS; that should
make them apply to C++ as well as C. That seems to be what the autoconf
documentation suggests:
- Variable: CFLAGS
Debugging and optimization options for the C compiler. If it is not set
in the environment when configure runs, the default value is set when
you call AC_PROG_CC (or empty if you don't). configure uses this
variable when compiling or linking programs to test for C features.
If a compiler option affects only the behavior of the preprocessor
(e.g., -Dname), it should be put into CPPFLAGS instead. If it affects
only the linker (e.g., -Ldirectory), it should be put into LDFLAGS
instead. If it affects only the compiler proper, CFLAGS is the natural
home for it. If an option affects multiple phases of the compiler,
though, matters get tricky. One approach to put such options directly
into CC, e.g., CC='gcc -m64'. Another is to put them into both CPPFLAGS
and LDFLAGS, but not into CFLAGS.
...
- Variable: CPPFLAGS
Preprocessor options for the C, C++, Objective C, and Objective C++
preprocessors and compilers. If it is not set in the environment when
configure runs, the default value is empty. configure uses this variable
when preprocessing or compiling programs to test for C, C++, Objective
C, and Objective C++ features.
This variable's contents should contain options like -I, -D, and -U that
affect only the behavior of the preprocessor. Please see the explanation
of CFLAGS for what you can do if an option affects other phases of the
compiler as well.
svn path=/trunk/; revision=41593
2012-03-16 03:27:45 +00:00
# already in CPPFLAGS or LDFLAGS, this won't make us find
# the version in the specified directory, as the compiler
# and/or linker will search that other directory before it
# searches the specified directory.
2006-01-31 22:22:05 +00:00
#
2006-05-31 19:12:15 +00:00
wireshark_save_CPPFLAGS="$CPPFLAGS"
2006-01-31 22:22:05 +00:00
CPPFLAGS="$CPPFLAGS -I$lua_dir/include"
2006-05-31 19:12:15 +00:00
wireshark_save_LIBS="$LIBS"
2007-01-04 22:45:43 +00:00
LIBS="$LIBS -L$lua_dir/lib -llua -lm"
2006-05-31 19:12:15 +00:00
wireshark_save_LDFLAGS="$LDFLAGS"
2006-01-31 22:22:05 +00:00
LDFLAGS="$LDFLAGS -L$lua_dir/lib"
2008-10-24 18:08:32 +00:00
else
2006-01-31 22:22:05 +00:00
#
# The user specified no directory in which liblua resides,
# so just add "-llua -lliblua" to the used libs.
#
2006-05-31 19:12:15 +00:00
wireshark_save_CPPFLAGS="$CPPFLAGS"
wireshark_save_LDFLAGS="$LDFLAGS"
wireshark_save_LIBS="$LIBS"
2007-01-04 22:45:43 +00:00
LIBS="$LIBS -llua -lm"
2006-01-31 22:22:05 +00:00
fi
#
# Make sure we have "lua.h", "lualib.h" and "lauxlib.h". If we don't, it means we probably
# don't have liblua, so don't use it.
#
AC_CHECK_HEADERS(lua.h lualib.h lauxlib.h,,
[
2006-07-19 19:20:58 +00:00
AC_CHECK_HEADERS(lua5.1/lua.h lua5.1/lualib.h lua5.1/lauxlib.h,
[
if test "x$lua_dir" != "x"
2006-01-31 22:22:05 +00:00
then
2006-07-19 19:20:58 +00:00
LUA_INCLUDES="-I$lua_dir/include/lua5.1"
2006-01-31 22:22:05 +00:00
else
2009-06-03 13:21:48 +00:00
#
# The user didn't specify a directory in which liblua resides;
# we must look for the headers in a "lua5.1" subdirectory of
# "/usr/include", "/usr/local/include", or "$prefix/include"
# as some systems apparently put the headers in a "lua5.1"
# subdirectory.
AC_MSG_CHECKING(for extraneous lua header directories)
found_lua_dir=""
lua_dir_list="/usr/include/lua5.1 $prefix/include/lua5.1"
2009-06-03 13:45:48 +00:00
if test "x$ac_cv_enable_usr_local" = "xyes"
then
2009-06-03 13:21:48 +00:00
lua_dir_list="$lua_dir_list /usr/local/include/lua5.1"
fi
2009-06-03 15:40:12 +00:00
for lua_dir_ent in $lua_dir_list
2009-06-03 13:21:48 +00:00
do
2009-06-03 15:40:12 +00:00
if test -d $lua_dir_ent
2009-06-03 13:45:48 +00:00
then
2009-06-03 15:40:12 +00:00
LUA_INCLUDES="-I$lua_dir_ent"
found_lua_dir="$lua_dir_ent"
2009-06-03 15:28:30 +00:00
break
2009-06-03 13:21:48 +00:00
fi
done
2009-06-03 13:45:48 +00:00
if test "x$found_lua_dir" != "x"
then
2009-06-03 13:21:48 +00:00
AC_MSG_RESULT(found -- $found_lua_dir)
else
AC_MSG_RESULT(not found)
2009-06-03 15:28:30 +00:00
#
Put -D and -I flags into CPPFLAGS rather than into CFLAGS; that should
make them apply to C++ as well as C. That seems to be what the autoconf
documentation suggests:
- Variable: CFLAGS
Debugging and optimization options for the C compiler. If it is not set
in the environment when configure runs, the default value is set when
you call AC_PROG_CC (or empty if you don't). configure uses this
variable when compiling or linking programs to test for C features.
If a compiler option affects only the behavior of the preprocessor
(e.g., -Dname), it should be put into CPPFLAGS instead. If it affects
only the linker (e.g., -Ldirectory), it should be put into LDFLAGS
instead. If it affects only the compiler proper, CFLAGS is the natural
home for it. If an option affects multiple phases of the compiler,
though, matters get tricky. One approach to put such options directly
into CC, e.g., CC='gcc -m64'. Another is to put them into both CPPFLAGS
and LDFLAGS, but not into CFLAGS.
...
- Variable: CPPFLAGS
Preprocessor options for the C, C++, Objective C, and Objective C++
preprocessors and compilers. If it is not set in the environment when
configure runs, the default value is empty. configure uses this variable
when preprocessing or compiling programs to test for C, C++, Objective
C, and Objective C++ features.
This variable's contents should contain options like -I, -D, and -U that
affect only the behavior of the preprocessor. Please see the explanation
of CFLAGS for what you can do if an option affects other phases of the
compiler as well.
svn path=/trunk/; revision=41593
2012-03-16 03:27:45 +00:00
# Restore the versions of CPPFLAGS,
2009-06-03 15:28:30 +00:00
# LDFLAGS, and LIBS before we added the
# "--with-lua=" directory, as we didn't
# actually find lua there.
#
CPPFLAGS="$wireshark_save_CPPFLAGS"
LDFLAGS="$wireshark_save_LDFLAGS"
LIBS="$wireshark_save_LIBS"
LUA_LIBS=""
2009-06-03 13:45:48 +00:00
if test "x$want_lua" = "xyes"
then
# we found lua5.1/lua.h, but we don't know which include dir contains it
AC_MSG_ERROR(Header file lua.h was found as lua5.1/lua.h but we can't locate the include directory. Please set the DIR for the --with-lua configure parameter.)
else
#
# We couldn't find the header file; don't use the
# library, as it's probably not present.
#
want_lua=no
fi
2009-06-03 13:21:48 +00:00
fi
2006-07-19 19:20:58 +00:00
fi
],
[
2009-06-03 15:28:30 +00:00
#
Put -D and -I flags into CPPFLAGS rather than into CFLAGS; that should
make them apply to C++ as well as C. That seems to be what the autoconf
documentation suggests:
- Variable: CFLAGS
Debugging and optimization options for the C compiler. If it is not set
in the environment when configure runs, the default value is set when
you call AC_PROG_CC (or empty if you don't). configure uses this
variable when compiling or linking programs to test for C features.
If a compiler option affects only the behavior of the preprocessor
(e.g., -Dname), it should be put into CPPFLAGS instead. If it affects
only the linker (e.g., -Ldirectory), it should be put into LDFLAGS
instead. If it affects only the compiler proper, CFLAGS is the natural
home for it. If an option affects multiple phases of the compiler,
though, matters get tricky. One approach to put such options directly
into CC, e.g., CC='gcc -m64'. Another is to put them into both CPPFLAGS
and LDFLAGS, but not into CFLAGS.
...
- Variable: CPPFLAGS
Preprocessor options for the C, C++, Objective C, and Objective C++
preprocessors and compilers. If it is not set in the environment when
configure runs, the default value is empty. configure uses this variable
when preprocessing or compiling programs to test for C, C++, Objective
C, and Objective C++ features.
This variable's contents should contain options like -I, -D, and -U that
affect only the behavior of the preprocessor. Please see the explanation
of CFLAGS for what you can do if an option affects other phases of the
compiler as well.
svn path=/trunk/; revision=41593
2012-03-16 03:27:45 +00:00
# Restore the versions of CPPFLAGS, LDFLAGS,
# and LIBS before we added the "--with-lua="
# directory, as we didn't actually find lua
# there.
2009-06-03 15:28:30 +00:00
#
CPPFLAGS="$wireshark_save_CPPFLAGS"
LDFLAGS="$wireshark_save_LDFLAGS"
LIBS="$wireshark_save_LIBS"
LUA_LIBS=""
2006-07-19 19:20:58 +00:00
if test "x$lua_dir" != "x"
then
2006-01-31 22:22:05 +00:00
#
2006-07-19 19:20:58 +00:00
# The user used "--with-lua=" to specify a directory
# containing liblua, but we didn't find the header file
# there; that either means they didn't specify the
# right directory or are confused about whether liblua
# is, in fact, installed. Report the error and give up.
2006-01-31 22:22:05 +00:00
#
2006-07-19 19:20:58 +00:00
AC_MSG_ERROR([liblua header not found in directory specified in --with-lua])
else
if test "x$want_lua" = "xyes"
then
#
# The user tried to force us to use the library, but we
# couldn't find the header file; report an error.
#
AC_MSG_ERROR(Header file lua.h not found.)
else
#
# We couldn't find the header file; don't use the
# library, as it's probably not present.
#
want_lua=no
fi
2006-01-31 22:22:05 +00:00
fi
2006-07-19 19:20:58 +00:00
])
2006-01-31 22:22:05 +00:00
])
if test "x$want_lua" != "xno"
then
#
# Well, we at least have the lua header file.
#
# let's check if the libs are there
#
2006-02-19 11:02:20 +00:00
# At least on Suse 9.3 systems, liblualib needs linking
# against libm.
LIBS="$LIBS $LUA_LIBS -lm"
2008-11-18 14:55:01 +00:00
AC_CHECK_LIB(lua, luaL_register,
2006-01-31 22:22:05 +00:00
[
2012-03-16 08:02:35 +00:00
#
# Lua 5.1 found
#
2006-01-31 22:22:05 +00:00
if test "x$lua_dir" != "x"
then
#
2012-03-16 08:02:35 +00:00
# Put the "-I" and "-L" flags for lua into
# LUA_INCLUDES and LUA_LIBS, respectively.
2006-01-31 22:22:05 +00:00
#
2007-01-04 22:45:43 +00:00
LUA_LIBS="-L$lua_dir/lib -llua -lm"
2006-02-18 04:03:24 +00:00
LUA_INCLUDES="-I$lua_dir/include"
2006-01-31 22:22:05 +00:00
else
2007-01-04 22:45:43 +00:00
LUA_LIBS="-llua -lm"
2006-02-18 04:03:24 +00:00
LUA_INCLUDES=""
2006-01-31 22:22:05 +00:00
fi
2008-11-18 14:55:01 +00:00
AC_DEFINE(HAVE_LUA_5_1, 1, [Define to use Lua 5.1])
2009-06-03 12:13:07 +00:00
want_lua=yes
2006-01-31 22:22:05 +00:00
2008-10-24 18:08:32 +00:00
],[
2006-01-31 22:22:05 +00:00
#
2006-07-19 19:20:58 +00:00
# We could not find the libs, maybe we have version number in the lib name
2006-01-31 22:22:05 +00:00
#
2006-07-19 19:20:58 +00:00
LIBS="$wireshark_save_LIBS -llua5.1 -lm"
AC_CHECK_LIB(lua5.1, luaL_register,
[
#
# Lua 5.1 found
#
LUA_LIBS=" -llua5.1 -lm"
2009-06-03 12:13:07 +00:00
AC_DEFINE(HAVE_LUA_5_1, 1, [Define to use Lua 5.1])
want_lua=yes
2006-07-19 19:20:58 +00:00
],[
#
Put -D and -I flags into CPPFLAGS rather than into CFLAGS; that should
make them apply to C++ as well as C. That seems to be what the autoconf
documentation suggests:
- Variable: CFLAGS
Debugging and optimization options for the C compiler. If it is not set
in the environment when configure runs, the default value is set when
you call AC_PROG_CC (or empty if you don't). configure uses this
variable when compiling or linking programs to test for C features.
If a compiler option affects only the behavior of the preprocessor
(e.g., -Dname), it should be put into CPPFLAGS instead. If it affects
only the linker (e.g., -Ldirectory), it should be put into LDFLAGS
instead. If it affects only the compiler proper, CFLAGS is the natural
home for it. If an option affects multiple phases of the compiler,
though, matters get tricky. One approach to put such options directly
into CC, e.g., CC='gcc -m64'. Another is to put them into both CPPFLAGS
and LDFLAGS, but not into CFLAGS.
...
- Variable: CPPFLAGS
Preprocessor options for the C, C++, Objective C, and Objective C++
preprocessors and compilers. If it is not set in the environment when
configure runs, the default value is empty. configure uses this variable
when preprocessing or compiling programs to test for C, C++, Objective
C, and Objective C++ features.
This variable's contents should contain options like -I, -D, and -U that
affect only the behavior of the preprocessor. Please see the explanation
of CFLAGS for what you can do if an option affects other phases of the
compiler as well.
svn path=/trunk/; revision=41593
2012-03-16 03:27:45 +00:00
# Restore the versions of CPPFLAGS, LDFLAGS,
# and LIBS before we added the "--with-lua="
# directory, as we didn't actually find lua
# there.
2006-07-19 19:20:58 +00:00
#
CPPFLAGS="$wireshark_save_CPPFLAGS"
LDFLAGS="$wireshark_save_LDFLAGS"
LIBS="$wireshark_save_LIBS"
LUA_LIBS=""
# User requested --with-lua but it isn't available
if test "x$want_lua" = "xyes"
then
AC_MSG_ERROR(Linking with liblua failed.)
fi
want_lua=no
])
2006-01-31 22:22:05 +00:00
])
2006-02-18 04:03:24 +00:00
2006-05-31 19:12:15 +00:00
CPPFLAGS="$wireshark_save_CPPFLAGS"
LDFLAGS="$wireshark_save_LDFLAGS"
LIBS="$wireshark_save_LIBS"
2006-01-31 22:22:05 +00:00
AC_SUBST(LUA_LIBS)
2006-02-18 04:03:24 +00:00
AC_SUBST(LUA_INCLUDES)
2006-01-31 22:22:05 +00:00
fi
])
2006-08-30 21:51:31 +00:00
#
# AC_WIRESHARK_LIBPORTAUDIO_CHECK
#
AC_DEFUN([AC_WIRESHARK_LIBPORTAUDIO_CHECK],[
if test "x$portaudio_dir" != "x"
then
#
# The user specified a directory in which libportaudio
# resides, so add the "include" subdirectory of that directory to
# the include file search path and the "lib" subdirectory
# of that directory to the library search path.
#
# XXX - if there's also a libportaudio in a directory that's
Put -D and -I flags into CPPFLAGS rather than into CFLAGS; that should
make them apply to C++ as well as C. That seems to be what the autoconf
documentation suggests:
- Variable: CFLAGS
Debugging and optimization options for the C compiler. If it is not set
in the environment when configure runs, the default value is set when
you call AC_PROG_CC (or empty if you don't). configure uses this
variable when compiling or linking programs to test for C features.
If a compiler option affects only the behavior of the preprocessor
(e.g., -Dname), it should be put into CPPFLAGS instead. If it affects
only the linker (e.g., -Ldirectory), it should be put into LDFLAGS
instead. If it affects only the compiler proper, CFLAGS is the natural
home for it. If an option affects multiple phases of the compiler,
though, matters get tricky. One approach to put such options directly
into CC, e.g., CC='gcc -m64'. Another is to put them into both CPPFLAGS
and LDFLAGS, but not into CFLAGS.
...
- Variable: CPPFLAGS
Preprocessor options for the C, C++, Objective C, and Objective C++
preprocessors and compilers. If it is not set in the environment when
configure runs, the default value is empty. configure uses this variable
when preprocessing or compiling programs to test for C, C++, Objective
C, and Objective C++ features.
This variable's contents should contain options like -I, -D, and -U that
affect only the behavior of the preprocessor. Please see the explanation
of CFLAGS for what you can do if an option affects other phases of the
compiler as well.
svn path=/trunk/; revision=41593
2012-03-16 03:27:45 +00:00
# already in CPPFLAGS or LDFLAGS, this won't make us find
# the version in the specified directory, as the compiler
# and/or linker will search that other directory before it
# searches the specified directory.
2006-08-30 21:51:31 +00:00
#
wireshark_save_CPPFLAGS="$CPPFLAGS"
CPPFLAGS="$CPPFLAGS -I$portaudio_dir/include"
wireshark_save_LIBS="$LIBS"
LIBS="$LIBS -L$portaudio_dir/lib -lportaudio"
wireshark_save_LDFLAGS="$LDFLAGS"
LDFLAGS="$LDFLAGS -L$portaudio_dir/lib"
2008-10-24 18:08:32 +00:00
else
2006-08-30 21:51:31 +00:00
#
# The user specified no directory in which libportaudio resides,
# so just add "-lportaudio" to the used libs.
#
wireshark_save_CPPFLAGS="$CPPFLAGS"
wireshark_save_LDFLAGS="$LDFLAGS"
wireshark_save_LIBS="$LIBS"
LIBS="$LIBS -lportaudio"
fi
#
# Make sure we have "portaudio.h". If we don't, it means we probably
# don't have libportaudio, so don't use it.
#
AC_CHECK_HEADERS(portaudio.h,,
[
if test "x$portaudio_dir" != "x"
then
#
# The user used "--with-portaudio=" to specify a directory
# containing libportaudio, but we didn't find the header file
# there; that either means they didn't specify the
# right directory or are confused about whether libportaudio
# is, in fact, installed. Report the error and give up.
#
AC_MSG_ERROR([libportaudio header not found in directory specified in --with-portaudio])
else
2006-09-04 13:34:48 +00:00
CPPFLAGS="$wireshark_save_CPPFLAGS"
LDFLAGS="$wireshark_save_LDFLAGS"
LIBS="$wireshark_save_LIBS"
PORTAUDIO_LIBS=""
2006-08-30 21:51:31 +00:00
if test "x$want_portaudio" = "xyes"
then
#
# The user tried to force us to use the library, but we
# couldn't find the header file; report an error.
#
AC_MSG_ERROR(Header file portaudio.h not found.)
else
#
# We couldn't find the header file; don't use the
# library, as it's probably not present.
#
want_portaudio=no
fi
fi
])
2006-09-04 13:34:48 +00:00
#
# Check whether we have the right version of portaudio
#
if test "x$want_portaudio" != "xno"
then
2006-09-05 09:17:55 +00:00
AC_CHECK_TYPE(PortAudioStream,
AC_DEFINE(PORTAUDIO_API_1, 1, [Define if we are using version of of the Portaudio library API]),
,
2006-09-04 22:47:16 +00:00
[#include <portaudio.h>])
2006-09-04 13:34:48 +00:00
fi
2006-08-30 21:51:31 +00:00
if test "x$want_portaudio" != "xno"
then
#
# Well, we at least have the portaudio header file.
#
# let's check if the libs are there
#
AC_CHECK_LIB(portaudio, Pa_Initialize,
[
if test "x$portaudio_dir" != "x"
then
#
2012-03-16 08:02:35 +00:00
# Put the "-I" and "-L" flags for portaudio
# into PORTAUDIO_INCLUDES and PORTAUDIO_LIBS,
# respectively.
2006-08-30 21:51:31 +00:00
#
PORTAUDIO_LIBS="-L$portaudio_dir/lib -lportaudio"
PORTAUDIO_INCLUDES="-I$portaudio_dir/include"
else
PORTAUDIO_LIBS="-lportaudio"
PORTAUDIO_INCLUDES=""
fi
AC_DEFINE(HAVE_LIBPORTAUDIO, 1, [Define to use libportaudio library])
2006-10-19 09:16:49 +00:00
want_portaudio=yes
2008-10-24 18:08:32 +00:00
],[
2006-08-30 21:51:31 +00:00
#
Put -D and -I flags into CPPFLAGS rather than into CFLAGS; that should
make them apply to C++ as well as C. That seems to be what the autoconf
documentation suggests:
- Variable: CFLAGS
Debugging and optimization options for the C compiler. If it is not set
in the environment when configure runs, the default value is set when
you call AC_PROG_CC (or empty if you don't). configure uses this
variable when compiling or linking programs to test for C features.
If a compiler option affects only the behavior of the preprocessor
(e.g., -Dname), it should be put into CPPFLAGS instead. If it affects
only the linker (e.g., -Ldirectory), it should be put into LDFLAGS
instead. If it affects only the compiler proper, CFLAGS is the natural
home for it. If an option affects multiple phases of the compiler,
though, matters get tricky. One approach to put such options directly
into CC, e.g., CC='gcc -m64'. Another is to put them into both CPPFLAGS
and LDFLAGS, but not into CFLAGS.
...
- Variable: CPPFLAGS
Preprocessor options for the C, C++, Objective C, and Objective C++
preprocessors and compilers. If it is not set in the environment when
configure runs, the default value is empty. configure uses this variable
when preprocessing or compiling programs to test for C, C++, Objective
C, and Objective C++ features.
This variable's contents should contain options like -I, -D, and -U that
affect only the behavior of the preprocessor. Please see the explanation
of CFLAGS for what you can do if an option affects other phases of the
compiler as well.
svn path=/trunk/; revision=41593
2012-03-16 03:27:45 +00:00
# Restore the versions of CPPFLAGS, LDFLAGS, and
# LIBS before we added the "--with-portaudio="
# directory, as we didn't actually find portaudio
# there.
2006-08-30 21:51:31 +00:00
#
CPPFLAGS="$wireshark_save_CPPFLAGS"
LDFLAGS="$wireshark_save_LDFLAGS"
LIBS="$wireshark_save_LIBS"
PORTAUDIO_LIBS=""
# User requested --with-portaudio but it isn't available
if test "x$want_portaudio" = "xyes"
then
AC_MSG_ERROR(Linking with libportaudio failed.)
fi
want_portaudio=no
])
CPPFLAGS="$wireshark_save_CPPFLAGS"
LDFLAGS="$wireshark_save_LDFLAGS"
LIBS="$wireshark_save_LIBS"
AC_SUBST(PORTAUDIO_LIBS)
AC_SUBST(PORTAUDIO_INCLUDES)
fi
])
2002-01-20 23:05:25 +00:00
#
2006-05-31 19:12:15 +00:00
# AC_WIRESHARK_RPM_CHECK
2002-01-20 23:05:25 +00:00
# Looks for the rpm program, and checks to see if we can redefine "_topdir".
#
2006-05-31 19:12:15 +00:00
AC_DEFUN([AC_WIRESHARK_RPM_CHECK],
2002-01-20 23:05:25 +00:00
[
2006-05-31 19:12:15 +00:00
AC_CHECK_PROG(ac_cv_wireshark_have_rpm, rpm, "yes", "no")
if test "x$ac_cv_wireshark_have_rpm" = "xyes"; then
2002-01-20 23:05:25 +00:00
rpm --define '_topdir /tmp' > /dev/null 2>&1
AC_MSG_CHECKING(to see if we can redefine _topdir)
if test $? -eq 0 ; then
AC_MSG_RESULT(yes)
HAVE_RPM=yes
else
AC_MSG_RESULT(no. You'll have to build packages manually.)
HAVE_RPM=no
fi
fi
])
2002-02-02 21:07:40 +00:00
#
2006-05-31 19:12:15 +00:00
# AC_WIRESHARK_GNU_SED_CHECK
2002-02-02 21:07:40 +00:00
# Checks if GNU sed is the first sed in PATH.
#
2006-05-31 19:12:15 +00:00
AC_DEFUN([AC_WIRESHARK_GNU_SED_CHECK],
2002-02-02 21:07:40 +00:00
[
AC_MSG_CHECKING(for GNU sed as first sed in PATH)
if ( sh -c "sed --version" </dev/null 2> /dev/null | grep "GNU sed" 2>&1 > /dev/null ) ; then
AC_MSG_RESULT(yes)
HAVE_GNU_SED=yes
else
AC_MSG_RESULT(no)
HAVE_GNU_SED=no
fi
])
2003-05-04 18:50:56 +00:00
2008-08-08 00:04:38 +00:00
#
# AC_WIRESHARK_C_ARES_CHECK
#
AC_DEFUN([AC_WIRESHARK_C_ARES_CHECK],
[
want_c_ares=defaultyes
if test "x$want_c_ares" = "xdefaultyes"; then
want_c_ares=yes
if test "x$ac_cv_enable_usr_local" = "xyes" ; then
withval=/usr/local
if test -d "$withval"; then
AC_WIRESHARK_ADD_DASH_L(LDFLAGS, ${withval}/lib)
fi
fi
fi
if test "x$want_c_ares" = "xyes"; then
AC_CHECK_LIB(cares, ares_init,
[
C_ARES_LIBS=-lcares
AC_DEFINE(HAVE_C_ARES, 1, [Define to use c-ares library])
have_good_c_ares=yes
],, $SOCKET_LIBS $NSL_LIBS
)
else
AC_MSG_RESULT(not required)
fi
])
2003-05-04 18:50:56 +00:00
#
2006-05-31 19:12:15 +00:00
# AC_WIRESHARK_ADNS_CHECK
2003-05-04 18:50:56 +00:00
#
2006-05-31 19:12:15 +00:00
AC_DEFUN([AC_WIRESHARK_ADNS_CHECK],
2003-05-04 18:50:56 +00:00
[
want_adns=defaultyes
if test "x$want_adns" = "xdefaultyes"; then
want_adns=yes
2006-10-26 14:50:03 +00:00
if test "x$ac_cv_enable_usr_local" = "xyes" ; then
withval=/usr/local
if test -d "$withval"; then
AC_WIRESHARK_ADD_DASH_L(LDFLAGS, ${withval}/lib)
fi
2003-05-04 18:50:56 +00:00
fi
fi
if test "x$want_adns" = "xyes"; then
AC_CHECK_LIB(adns, adns_init,
[
ADNS_LIBS=-ladns
AC_DEFINE(HAVE_GNU_ADNS, 1, [Define to use GNU ADNS library])
2003-10-10 10:12:18 +00:00
have_good_adns=yes
2003-12-19 01:36:01 +00:00
],, $SOCKET_LIBS $NSL_LIBS
2003-05-04 18:50:56 +00:00
)
else
AC_MSG_RESULT(not required)
fi
])
2004-03-17 18:20:58 +00:00
2007-11-20 16:53:01 +00:00
#
# AC_WIRESHARK_LIBCAP_CHECK
#
AC_DEFUN([AC_WIRESHARK_LIBCAP_CHECK],
[
want_libcap=defaultyes
if test "x$want_libcap" = "xdefaultyes"; then
want_libcap=yes
if test "x$ac_cv_enable_usr_local" = "xyes" ; then
withval=/usr/local
if test -d "$withval"; then
AC_WIRESHARK_ADD_DASH_L(LDFLAGS, ${withval}/lib)
fi
fi
fi
if test "x$want_libcap" = "xyes"; then
AC_CHECK_LIB(cap, cap_set_flag,
[
LIBCAP_LIBS=-lcap
AC_DEFINE(HAVE_LIBCAP, 1, [Define to use the libcap library])
have_good_libcap=yes
],,
)
else
AC_MSG_RESULT(not required)
fi
])
2004-03-17 18:20:58 +00:00
#
2006-05-31 19:12:15 +00:00
# AC_WIRESHARK_KRB5_CHECK
2004-03-17 18:20:58 +00:00
#
2006-05-31 19:12:15 +00:00
AC_DEFUN([AC_WIRESHARK_KRB5_CHECK],
2004-03-17 18:20:58 +00:00
[
2006-05-31 19:12:15 +00:00
wireshark_save_CPPFLAGS="$CPPFLAGS"
2004-03-17 18:20:58 +00:00
if test "x$krb5_dir" != "x"
then
#
# The user specified a directory in which kerberos resides,
# so add the "include" subdirectory of that directory to
# the include file search path and the "lib" subdirectory
# of that directory to the library search path.
#
# XXX - if there's also a kerberos in a directory that's
Put -D and -I flags into CPPFLAGS rather than into CFLAGS; that should
make them apply to C++ as well as C. That seems to be what the autoconf
documentation suggests:
- Variable: CFLAGS
Debugging and optimization options for the C compiler. If it is not set
in the environment when configure runs, the default value is set when
you call AC_PROG_CC (or empty if you don't). configure uses this
variable when compiling or linking programs to test for C features.
If a compiler option affects only the behavior of the preprocessor
(e.g., -Dname), it should be put into CPPFLAGS instead. If it affects
only the linker (e.g., -Ldirectory), it should be put into LDFLAGS
instead. If it affects only the compiler proper, CFLAGS is the natural
home for it. If an option affects multiple phases of the compiler,
though, matters get tricky. One approach to put such options directly
into CC, e.g., CC='gcc -m64'. Another is to put them into both CPPFLAGS
and LDFLAGS, but not into CFLAGS.
...
- Variable: CPPFLAGS
Preprocessor options for the C, C++, Objective C, and Objective C++
preprocessors and compilers. If it is not set in the environment when
configure runs, the default value is empty. configure uses this variable
when preprocessing or compiling programs to test for C, C++, Objective
C, and Objective C++ features.
This variable's contents should contain options like -I, -D, and -U that
affect only the behavior of the preprocessor. Please see the explanation
of CFLAGS for what you can do if an option affects other phases of the
compiler as well.
svn path=/trunk/; revision=41593
2012-03-16 03:27:45 +00:00
# already in CPPFLAGS or LDFLAGS, this won't make us find
# the version in the specified directory, as the compiler
# and/or linker will search that other directory before it
# searches the specified directory.
2004-03-17 18:20:58 +00:00
#
CPPFLAGS="$CPPFLAGS -I$krb5_dir/include"
2004-10-15 06:51:48 +00:00
ac_heimdal_version=`grep heimdal $krb5_dir/include/krb5.h | head -n 1 | sed 's/^.*heimdal.*$/HEIMDAL/'`
2010-05-09 06:33:03 +00:00
# MIT Kerberos moved krb5.h to krb5/krb5.h starting with release 1.5
ac_mit_version_olddir=`grep 'Massachusetts Institute of Technology' $krb5_dir/include/krb5.h | head -n 1 | sed 's/^.*Massachusetts Institute of Technology.*$/MIT/'`
ac_mit_version_newdir=`grep 'Massachusetts Institute of Technology' $krb5_dir/include/krb5/krb5.h | head -n 1 | sed 's/^.*Massachusetts Institute of Technology.*$/MIT/'`
ac_krb5_version="$ac_heimdal_version$ac_mit_version_olddir$ac_mit_version_newdir"
2004-10-15 06:51:48 +00:00
if test "x$ac_krb5_version" = "xHEIMDAL"
then
2011-10-30 16:19:05 +00:00
KRB5_LIBS="-L$krb5_dir/lib -lkrb5 -lasn1 $SSL_LIBS -lroken -lcrypt"
else
2004-10-15 06:51:48 +00:00
KRB5_LIBS="-L$krb5_dir/lib -lkrb5 -lk5crypto -lcom_err"
fi
if test "x$ac_krb5_version" = "xMIT"
then
2005-03-20 19:29:22 +00:00
AC_DEFINE(HAVE_MIT_KERBEROS, 1, [Define to use MIT kerberos])
2004-10-15 06:51:48 +00:00
fi
2004-03-17 18:20:58 +00:00
else
2008-10-24 18:08:32 +00:00
AC_PATH_PROG(KRB5_CONFIG, krb5-config)
2004-05-18 11:11:37 +00:00
if test -x "$KRB5_CONFIG"
2004-03-17 18:20:58 +00:00
then
2004-05-18 11:11:37 +00:00
KRB5_FLAGS=`"$KRB5_CONFIG" --cflags`
2004-09-30 07:14:18 +00:00
KRB5_LIBS=`"$KRB5_CONFIG" --libs`
2004-09-29 17:38:53 +00:00
CPPFLAGS="$CPPFLAGS $KRB5_FLAGS"
2004-09-25 09:33:53 +00:00
#
2004-09-25 23:58:42 +00:00
# If -lcrypto is in KRB5_FLAGS, we require it to build
2004-10-15 06:51:48 +00:00
# with Heimdal/MIT. We don't want to built with it by
2004-09-25 23:58:42 +00:00
# default, due to annoying license incompatibilities
# between the OpenSSL license and the GPL, so:
2004-09-25 09:33:53 +00:00
#
2004-09-25 23:58:42 +00:00
# if SSL_LIBS is set to a non-empty string, we
# remove -lcrypto from KRB5_LIBS and replace
# it with SSL_LIBS;
#
# if SSL_LIBS is not set to a non-empty string
# we fail with an appropriate error message.
#
case "$KRB5_LIBS" in
*-lcrypto*)
if test ! -z "$SSL_LIBS"
then
2004-09-30 07:14:18 +00:00
KRB5_LIBS=`echo $KRB5_LIBS | sed 's/-lcrypto//'`
2004-09-25 23:58:42 +00:00
KRB5_LIBS="$KRB5_LIBS $SSL_LIBS"
else
AC_MSG_ERROR([Kerberos library requires -lcrypto but --with-ssl not specified])
fi
;;
esac
2009-03-06 18:56:53 +00:00
ac_krb5_version=`"$KRB5_CONFIG" --version | head -n 1 | sed -e 's/^.*heimdal.*$/HEIMDAL/' -e 's/^Kerberos .*$/MIT/' -e 's/^Solaris Kerberos .*$/MIT/'`
2004-03-17 18:20:58 +00:00
fi
fi
#
# Make sure we have "krb5.h". If we don't, it means we probably
# don't have kerberos, so don't use it.
#
AC_CHECK_HEADER(krb5.h,,
[
if test "x$krb5_dir" != "x"
then
#
# The user used "--with-krb5=" to specify a directory
# containing kerberos, but we didn't find the header file
# there; that either means they didn't specify the
# right directory or are confused about whether kerberos
# is, in fact, installed. Report the error and give up.
#
AC_MSG_ERROR([kerberos header not found in directory specified in --with-krb5])
else
if test "x$want_krb5" = "xyes"
then
#
# The user tried to force us to use the library, but we
# couldn't find the header file; report an error.
#
AC_MSG_ERROR(Header file krb5.h not found.)
else
#
# We couldn't find the header file; don't use the
# library, as it's probably not present.
#
want_krb5=no
2004-10-15 06:51:48 +00:00
AC_MSG_RESULT(No Heimdal or MIT header found - disabling dissection for some kerberos data in packet decoding)
2004-03-17 18:20:58 +00:00
fi
fi
])
2004-09-26 20:30:44 +00:00
if test "x$want_krb5" != "xno"
2004-03-17 18:20:58 +00:00
then
2004-09-26 00:26:06 +00:00
#
# Well, we at least have the krb5 header file.
2004-10-15 06:51:48 +00:00
# Check whether this is Heimdal or MIT.
2004-09-26 00:26:06 +00:00
#
2004-10-15 06:51:48 +00:00
AC_MSG_CHECKING(whether the Kerberos library is Heimdal or MIT)
if test "x$ac_krb5_version" = "xHEIMDAL" -o "x$ac_krb5_version" = "xMIT"
2004-09-26 00:26:06 +00:00
then
#
2004-09-26 20:30:44 +00:00
# Yes.
# Check whether we have krb5_kt_resolve - and whether
# we need to link with -lresolv when linking with
# the Kerberos library.
2004-09-26 00:26:06 +00:00
#
2004-10-15 06:51:48 +00:00
AC_MSG_RESULT($ac_krb5_version)
2006-05-31 19:12:15 +00:00
wireshark_save_LIBS="$LIBS"
2004-09-26 20:30:44 +00:00
found_krb5_kt_resolve=no
for extras in "" "-lresolv"
do
LIBS="$KRB5_LIBS $extras"
if test -z "$extras"
then
2004-10-15 06:51:48 +00:00
AC_MSG_CHECKING([whether $ac_krb5_version includes krb5_kt_resolve])
2004-09-26 20:30:44 +00:00
else
2004-10-15 06:51:48 +00:00
AC_MSG_CHECKING([whether $ac_krb5_version includes krb5_kt_resolve (linking with $extras)])
2004-09-26 20:30:44 +00:00
fi
AC_TRY_LINK(
[
],
[
krb5_kt_resolve();
],
[
#
# We found "krb5_kt_resolve()", and required
# the libraries in extras as well.
#
AC_MSG_RESULT(yes)
KRB5_LIBS="$LIBS"
AC_DEFINE(HAVE_KERBEROS, 1, [Define to use kerberos])
2004-10-15 06:51:48 +00:00
if test "x$ac_krb5_version" = "xHEIMDAL"
then
AC_DEFINE(HAVE_HEIMDAL_KERBEROS, 1, [Define to use heimdal kerberos])
2005-03-20 19:29:22 +00:00
elif test "x$ac_krb5_version" = "xMIT"
2004-10-15 06:51:48 +00:00
then
AC_DEFINE(HAVE_MIT_KERBEROS, 1, [Define to use MIT kerberos])
fi
2004-09-26 20:30:44 +00:00
found_krb5_kt_resolve=yes
break
],
[
AC_MSG_RESULT(no)
])
done
if test "$found_krb5_kt_resolve" = no
then
#
# We didn't find "krb5_kt_resolve()" in the
# Kerberos library, even when we tried linking
# with -lresolv; we can't link with kerberos.
2004-09-28 04:41:57 +00:00
#
if test "x$want_krb5" = "xyes"
then
#
# The user tried to force us to use the library,
# but we can't do so; report an error.
#
2004-10-15 06:51:48 +00:00
AC_MSG_ERROR(Usable $ac_krb5_version not found)
2004-09-28 04:41:57 +00:00
else
#
Put -D and -I flags into CPPFLAGS rather than into CFLAGS; that should
make them apply to C++ as well as C. That seems to be what the autoconf
documentation suggests:
- Variable: CFLAGS
Debugging and optimization options for the C compiler. If it is not set
in the environment when configure runs, the default value is set when
you call AC_PROG_CC (or empty if you don't). configure uses this
variable when compiling or linking programs to test for C features.
If a compiler option affects only the behavior of the preprocessor
(e.g., -Dname), it should be put into CPPFLAGS instead. If it affects
only the linker (e.g., -Ldirectory), it should be put into LDFLAGS
instead. If it affects only the compiler proper, CFLAGS is the natural
home for it. If an option affects multiple phases of the compiler,
though, matters get tricky. One approach to put such options directly
into CC, e.g., CC='gcc -m64'. Another is to put them into both CPPFLAGS
and LDFLAGS, but not into CFLAGS.
...
- Variable: CPPFLAGS
Preprocessor options for the C, C++, Objective C, and Objective C++
preprocessors and compilers. If it is not set in the environment when
configure runs, the default value is empty. configure uses this variable
when preprocessing or compiling programs to test for C, C++, Objective
C, and Objective C++ features.
This variable's contents should contain options like -I, -D, and -U that
affect only the behavior of the preprocessor. Please see the explanation
of CFLAGS for what you can do if an option affects other phases of the
compiler as well.
svn path=/trunk/; revision=41593
2012-03-16 03:27:45 +00:00
# Restore the versions of CPPFLAGS from before we
# added the flags for Kerberos.
2004-09-28 04:41:57 +00:00
#
2004-10-15 06:51:48 +00:00
AC_MSG_RESULT(Usable $ac_krb5_version not found - disabling dissection for some kerberos data in packet decoding)
2006-05-31 19:12:15 +00:00
CPPFLAGS="$wireshark_save_CPPFLAGS"
2004-09-28 04:41:57 +00:00
KRB5_LIBS=""
want_krb5=no
fi
2005-03-20 19:29:22 +00:00
else
#
# We can link with Kerberos; see whether krb5.h
# defines KEYTYPE_ARCFOUR_56 (where "defines" means
# "as a #define or as an enum member).
#
AC_MSG_CHECKING([whether krb5.h defines KEYTYPE_ARCFOUR_56])
AC_COMPILE_IFELSE(
[
AC_LANG_SOURCE(
[[
#include <krb5.h>
#include <stdio.h>
main()
{
printf("%u\n", KEYTYPE_ARCFOUR_56);
}
]])
],
[
AC_MSG_RESULT(yes)
AC_DEFINE(HAVE_KEYTYPE_ARCFOUR_56, 1, [Define if krb5.h defines KEYTYPE_ARCFOUR_56])
],
[
AC_MSG_RESULT(no)
])
2004-09-28 04:41:57 +00:00
fi
2006-05-31 19:12:15 +00:00
LIBS="$wireshark_save_LIBS"
2004-09-28 04:41:57 +00:00
else
#
2004-10-15 06:51:48 +00:00
# It's not Heimdal or MIT.
2004-09-28 04:41:57 +00:00
#
2004-09-28 04:47:10 +00:00
AC_MSG_RESULT(no)
2004-09-28 04:41:57 +00:00
if test "x$want_krb5" = "xyes"
then
#
# The user tried to force us to use the library,
# but we can't do so; report an error.
#
2004-10-15 06:51:48 +00:00
AC_MSG_ERROR(Kerberos not found)
2004-09-28 04:41:57 +00:00
else
2004-09-26 20:30:44 +00:00
#
Put -D and -I flags into CPPFLAGS rather than into CFLAGS; that should
make them apply to C++ as well as C. That seems to be what the autoconf
documentation suggests:
- Variable: CFLAGS
Debugging and optimization options for the C compiler. If it is not set
in the environment when configure runs, the default value is set when
you call AC_PROG_CC (or empty if you don't). configure uses this
variable when compiling or linking programs to test for C features.
If a compiler option affects only the behavior of the preprocessor
(e.g., -Dname), it should be put into CPPFLAGS instead. If it affects
only the linker (e.g., -Ldirectory), it should be put into LDFLAGS
instead. If it affects only the compiler proper, CFLAGS is the natural
home for it. If an option affects multiple phases of the compiler,
though, matters get tricky. One approach to put such options directly
into CC, e.g., CC='gcc -m64'. Another is to put them into both CPPFLAGS
and LDFLAGS, but not into CFLAGS.
...
- Variable: CPPFLAGS
Preprocessor options for the C, C++, Objective C, and Objective C++
preprocessors and compilers. If it is not set in the environment when
configure runs, the default value is empty. configure uses this variable
when preprocessing or compiling programs to test for C, C++, Objective
C, and Objective C++ features.
This variable's contents should contain options like -I, -D, and -U that
affect only the behavior of the preprocessor. Please see the explanation
of CFLAGS for what you can do if an option affects other phases of the
compiler as well.
svn path=/trunk/; revision=41593
2012-03-16 03:27:45 +00:00
# Restore the versions of CPPFLAGS from before we
# added the flags for Kerberos.
2004-09-26 20:30:44 +00:00
#
2004-10-15 06:51:48 +00:00
AC_MSG_RESULT(Kerberos not found - disabling dissection for some kerberos data in packet decoding)
2006-05-31 19:12:15 +00:00
CPPFLAGS="$wireshark_save_CPPFLAGS"
2004-09-26 20:30:44 +00:00
KRB5_LIBS=""
want_krb5=no
fi
2004-09-26 00:26:06 +00:00
fi
else
#
2004-09-28 04:41:57 +00:00
# The user asked us not to use Kerberos, or they didn't
# say whether they wanted us to use it but we found
# that we couldn't.
2004-09-26 00:26:06 +00:00
#
Put -D and -I flags into CPPFLAGS rather than into CFLAGS; that should
make them apply to C++ as well as C. That seems to be what the autoconf
documentation suggests:
- Variable: CFLAGS
Debugging and optimization options for the C compiler. If it is not set
in the environment when configure runs, the default value is set when
you call AC_PROG_CC (or empty if you don't). configure uses this
variable when compiling or linking programs to test for C features.
If a compiler option affects only the behavior of the preprocessor
(e.g., -Dname), it should be put into CPPFLAGS instead. If it affects
only the linker (e.g., -Ldirectory), it should be put into LDFLAGS
instead. If it affects only the compiler proper, CFLAGS is the natural
home for it. If an option affects multiple phases of the compiler,
though, matters get tricky. One approach to put such options directly
into CC, e.g., CC='gcc -m64'. Another is to put them into both CPPFLAGS
and LDFLAGS, but not into CFLAGS.
...
- Variable: CPPFLAGS
Preprocessor options for the C, C++, Objective C, and Objective C++
preprocessors and compilers. If it is not set in the environment when
configure runs, the default value is empty. configure uses this variable
when preprocessing or compiling programs to test for C, C++, Objective
C, and Objective C++ features.
This variable's contents should contain options like -I, -D, and -U that
affect only the behavior of the preprocessor. Please see the explanation
of CFLAGS for what you can do if an option affects other phases of the
compiler as well.
svn path=/trunk/; revision=41593
2012-03-16 03:27:45 +00:00
# Restore the versions of CPPFLAGS from before we added
# the flags for Kerberos.
2004-09-26 00:26:06 +00:00
#
2006-05-31 19:12:15 +00:00
CPPFLAGS="$wireshark_save_CPPFLAGS"
2004-09-26 00:26:06 +00:00
KRB5_LIBS=""
want_krb5=no
2004-03-17 18:20:58 +00:00
fi
2004-06-29 07:59:12 +00:00
AC_SUBST(KRB5_LIBS)
2004-03-17 18:20:58 +00:00
])
2006-02-04 23:44:05 +00:00
2008-10-27 04:50:57 +00:00
#
# AC_WIRESHARK_GEOIP_CHECK
#
AC_DEFUN([AC_WIRESHARK_GEOIP_CHECK],
[
want_geoip=defaultyes
if test "x$want_geoip" = "xdefaultyes"; then
want_geoip=yes
if test "x$ac_cv_enable_usr_local" = "xyes" ; then
withval=/usr/local
if test -d "$withval"; then
AC_WIRESHARK_ADD_DASH_L(LDFLAGS, ${withval}/lib)
fi
fi
fi
if test "x$want_geoip" = "xyes"; then
AC_CHECK_LIB(GeoIP, GeoIP_new,
[
GEOIP_LIBS=-lGeoIP
AC_DEFINE(HAVE_GEOIP, 1, [Define to use GeoIP library])
have_good_geoip=yes
],,
)
2011-10-05 22:27:51 +00:00
if test "x$have_good_geoip" = "xyes"; then
AC_CHECK_LIB(GeoIP, GeoIP_country_name_by_ipnum_v6,
[
AC_DEFINE(HAVE_GEOIP_V6, 1, [Define if GeoIP supports IPv6 (GeoIP 1.4.5 and later)])
],,
)
fi
2008-10-27 04:50:57 +00:00
else
AC_MSG_RESULT(not required)
fi
])
2011-04-20 08:37:45 +00:00
#AC_WIRESHARK_LDFLAGS_CHECK
2009-08-07 18:49:24 +00:00
#
# $1 : ldflag(s) to test
#
2011-04-20 08:37:45 +00:00
# The macro first determines if the compiler supports "-Wl,{option}" to
# pass options through to the linker. Then it attempts to compile with
# the defined ldflags. The defined flags are added to LDFLAGS only if
# the compilation succeeds.
2009-08-07 18:49:24 +00:00
#
2011-04-20 08:37:45 +00:00
AC_DEFUN([AC_WIRESHARK_LDFLAGS_CHECK],
2009-08-07 18:49:24 +00:00
[GCC_OPTION="$1"
AC_MSG_CHECKING(whether we can add $GCC_OPTION to LDFLAGS)
2011-04-20 08:37:45 +00:00
if test "x$ac_supports_W_linker_passthrough" = "xyes"; then
2011-08-09 19:49:08 +00:00
LDFLAGS_saved="$LDFLAGS"
2009-08-07 18:49:24 +00:00
LDFLAGS="$LDFLAGS $GCC_OPTION"
AC_LINK_IFELSE([
AC_LANG_SOURCE([[
main() { return; }
]])],
[
AC_MSG_RESULT(yes)
],
[
AC_MSG_RESULT(no)
LDFLAGS="$LDFLAGS_saved"
])
else
AC_MSG_RESULT(no)
fi
])
2007-04-22 09:27:21 +00:00
#
# AC_WIRESHARK_GCC_CFLAGS_CHECK
#
# $1 : cflags to test
2012-03-16 00:49:01 +00:00
# $2 : if supplied, C for C-only flags, CXX for C++-only flags
2007-04-22 09:27:21 +00:00
#
2011-04-20 08:37:45 +00:00
# The macro first determines if the compiler supports GCC-style flags.
# Then it attempts to compile with the defined cflags. The defined
# flags are added to CFLAGS only if the compilation succeeds.
#
# We do this because not all such options are necessarily supported by
# the version of the particular compiler we're using.
2007-04-22 09:27:21 +00:00
#
2011-04-20 09:16:44 +00:00
# NOTE: clang, by default, only warns about unknown -W options.
# If we're using clang, we turn on -Werror=unknown-warning-option
# so that it fails if we pass it a -W option it doesn't know about
# but doesn't fail for any other warning that the test program might
# produce.
#
2007-04-22 09:27:21 +00:00
AC_DEFUN([AC_WIRESHARK_GCC_CFLAGS_CHECK],
[GCC_OPTION="$1"
2012-03-16 00:49:01 +00:00
case "$2" in
C)
AC_MSG_CHECKING(whether we can add $GCC_OPTION to CFLAGS)
;;
CXX)
AC_MSG_CHECKING(whether we can add $GCC_OPTION to CXXFLAGS)
;;
*)
AC_MSG_CHECKING(whether we can add $GCC_OPTION to CFLAGS and CXXFLAGS)
;;
esac
2011-04-20 08:37:45 +00:00
if test "x$ac_supports_gcc_flags" = "xyes" ; then
2012-03-16 00:49:01 +00:00
if test "$2" != CXX ; then
#
# Not C++-only; if this can be added to the C compiler flags, add them.
#
CFLAGS_saved="$CFLAGS"
CFLAGS="$CFLAGS $GCC_OPTION"
if test "x$CC" = "xclang" ; then
#
# Force clang to fail on an unknown warning option; by default,
# it whines but doesn't fail, so we add unknown options and,
# as a result, get a lot of that whining when we compile.
#
CFLAGS="$CFLAGS -Werror=unknown-warning-option"
fi
AC_COMPILE_IFELSE([
AC_LANG_SOURCE([[
int foo;
]])],
[
AC_MSG_RESULT(yes)
#
# Remove -Werror=unknown-warning-option, if we
# added it, by setting CFLAGS to the saved value
# plus just the new option.
#
CFLAGS="$CFLAGS_saved $GCC_OPTION"
if test "$2" != C ; then
#
# Add it to the C++ flags as well.
#
CXXFLAGS="$CXXFLAGS $GCC_OPTION"
fi
],
[
AC_MSG_RESULT(no)
CFLAGS="$CFLAGS_saved"
])
else
#
# C++-only; if this can be added to the C++ compiler flags, add them.
#
CXXFLAGS_saved="$CXXFLAGS"
CXXFLAGS="$CXXFLAGS $GCC_OPTION"
if test "x$CC" = "xclang" ; then
CXXFLAGS="$CXXFLAGS -Werror=unknown-warning-option"
fi
AC_LANG_PUSH([C++])
AC_COMPILE_IFELSE([
AC_LANG_SOURCE([[
int foo;
]])],
[
AC_MSG_RESULT(yes)
],
[
AC_MSG_RESULT(no)
CXXFLAGS="$CXXFLAGS_saved"
])
AC_LANG_POP([C++])
2011-04-20 09:16:44 +00:00
fi
2007-04-22 09:27:21 +00:00
else
AC_MSG_RESULT(no)
fi
])
2008-10-24 18:08:32 +00:00
#
2010-05-25 00:35:44 +00:00
# AC_WIRESHARK_OSX_INTEGRATION_CHECK
2008-10-24 18:08:32 +00:00
#
2008-10-26 20:09:54 +00:00
# Checks for the presence of OS X integration functions in the GTK+ framework
# or as a separate library.
#
2010-05-25 00:35:44 +00:00
# http://sourceforge.net/apps/trac/gtk-osx/wiki/Integrate
2008-10-24 18:08:32 +00:00
#
2010-05-25 00:35:44 +00:00
# http://live.gnome.org/GTK%2B/OSX/Integration
# for the old Carbon-based integration functions
#
# http://gtk-osx.sourceforge.net/ige-mac-integration/
# for the new Cocoa-based integration functions
#
AC_DEFUN([AC_WIRESHARK_OSX_INTEGRATION_CHECK],
2008-10-24 18:08:32 +00:00
[
ac_save_CFLAGS="$CFLAGS"
ac_save_LIBS="$LIBS"
CFLAGS="$CFLAGS $GTK_CFLAGS"
LIBS="$GTK_LIBS $LIBS"
2010-05-25 00:35:44 +00:00
#
2010-06-05 22:04:28 +00:00
# Check for the new integration functions in a -ligemacintegration
# library.
2010-05-25 00:35:44 +00:00
#
2010-06-05 22:04:28 +00:00
AC_CHECK_LIB(igemacintegration, gtk_osxapplication_set_menu_bar,
2008-10-24 18:08:32 +00:00
[
2010-06-05 22:04:28 +00:00
AC_DEFINE(HAVE_GTKOSXAPPLICATION, 1,
[Define to 1 if -ligemacintegration includes the GtkOSXApplication Integration functions.])
2008-12-23 03:25:56 +00:00
have_ige_mac=yes
2008-12-22 16:10:14 +00:00
# We don't want gtk stuff in LIBS (which is reset below) so
# manually set GTK_LIBS (which is more appropriate)
2010-06-05 22:04:28 +00:00
GTK_LIBS="$GTK_LIBS -ligemacintegration"
2008-12-23 03:25:56 +00:00
])
2011-04-20 08:37:45 +00:00
if test x$have_ige_mac = x
2008-12-23 03:25:56 +00:00
then
2010-05-25 00:35:44 +00:00
#
# Not found - check for the old integration functions in
2010-06-05 22:04:28 +00:00
# the Gtk framework.
2010-05-25 00:35:44 +00:00
#
2010-06-05 22:04:28 +00:00
AC_CHECK_LIB(Gtk, ige_mac_menu_set_menu_bar,
2008-12-22 16:10:14 +00:00
[
AC_DEFINE(HAVE_IGE_MAC_INTEGRATION, 1,
2010-06-05 22:04:28 +00:00
[Define to 1 if the the Gtk+ framework or a separate library includes the Imendio IGE Mac OS X Integration functions.])
have_ige_mac=yes
2008-12-22 16:10:14 +00:00
# We don't want gtk stuff in LIBS (which is reset below) so
# manually set GTK_LIBS (which is more appropriate)
2010-06-05 22:04:28 +00:00
GTK_LIBS="$GTK_LIBS -lGtk"
2008-12-22 16:10:14 +00:00
])
2008-12-23 03:25:56 +00:00
fi
2010-06-05 22:04:28 +00:00
2011-04-20 08:37:45 +00:00
if test x$have_ige_mac = x
2010-05-25 00:35:44 +00:00
then
#
2010-06-05 22:04:28 +00:00
# Not found - check for the old integration functions in
2010-05-25 00:35:44 +00:00
# a -ligemacintegration library.
#
2010-06-05 22:04:28 +00:00
AC_CHECK_LIB(igemacintegration, ige_mac_menu_set_menu_bar,
2010-05-25 00:35:44 +00:00
[
2010-06-05 22:04:28 +00:00
AC_DEFINE(HAVE_IGE_MAC_INTEGRATION, 1,
[Define to 1 if the the Gtk+ framework or a separate library includes the Imendio IGE Mac OS X Integration functions.])
2010-05-25 00:35:44 +00:00
have_ige_mac=yes
# We don't want gtk stuff in LIBS (which is reset below) so
# manually set GTK_LIBS (which is more appropriate)
GTK_LIBS="$GTK_LIBS -ligemacintegration"
])
fi
2008-12-19 02:48:19 +00:00
CFLAGS="$ac_save_CFLAGS"
LIBS="$ac_save_LIBS"
2008-10-24 18:08:32 +00:00
])
2009-05-29 21:10:40 +00:00
#
# AC_WIRESHARK_PYTHON_CHECK
#
# Check whether python devel package is present
#
AC_DEFUN([AC_WIRESHARK_PYTHON_CHECK],
[
#
# Checking whether we have a python devel environment available
#
# AC_CACHE_CHECK([checking python devel package], ac_cv_wireshark_python_devel,
# [
2011-04-28 02:24:46 +00:00
AC_CHECK_PROG([ac_ws_python_config], python-config, "yes", "no")
if test "x$ac_ws_python_config" = "xno"; then
ac_cv_wireshark_python_devel=no
2011-06-11 21:49:24 +00:00
if test "x$want_python" = "xyes"
then
#
# The user tried to force us to use Python, but we
# couldn't find the python-config tool; report an error.
#
AC_MSG_ERROR("python-config not found")
fi
#
# Set want_python to no, so we report that we aren't using
# the Python interpreter.
#
want_python=no
2009-05-29 21:10:40 +00:00
else
AC_MSG_CHECKING([python devel])
ac_save_ws_cflags=$CFLAGS
ac_save_ws_libs=$LIBS
CFLAGS=$(python-config --includes)
LIBS=$(python-config --ldflags)
AC_COMPILE_IFELSE(
[
AC_LANG_PROGRAM(
[[#include <Python.h>]],
[[Py_Initialiaze();]]
)
],
[
#
# Compilation successful, we have python devel available
#
ac_cv_wireshark_python_devel=yes
PY_LIBS=$LIBS
PY_CFLAGS=$CFLAGS
AC_SUBST(PY_LIBS)
AC_SUBST(PY_CFLAGS)
CFLAGS="$ac_save_ws_cflags"
LIBS="$ac_save_ws_libs"
AC_DEFINE(HAVE_PYTHON, 1, [Define if python devel package available])
AC_MSG_RESULT([yes])
],
[
#
# Compilation unsuccessful, python devel not available
#
ac_cv_wireshark_python_devel=no
CFLAGS=$ac_save_ws_cflags
LIBS=$ac_save_ws_libs
2011-06-11 21:49:24 +00:00
if test "x$want_python" = "xyes"
then
#
# The user tried to force us to use Python, but we
# couldn't compile the test program; report an error.
#
AC_MSG_ERROR("Python test program failed compilation")
fi
2009-05-29 21:10:40 +00:00
AC_MSG_RESULT([no])
2011-06-11 19:05:17 +00:00
#
2011-06-11 21:49:24 +00:00
# Set want_python to no, so we report that we aren't using
2011-06-11 19:05:17 +00:00
# the Python interpreter.
#
2011-06-11 21:49:24 +00:00
want_python=no
2009-05-29 21:10:40 +00:00
])
fi
# ])
])