# generated automatically by aclocal 1.10.1 -*- Autoconf -*-# Copyright (C) 1996, 1997, 1998, 1999, 2000, 2001, 2002, 2003, 2004,# 2005, 2006, 2007, 2008  Free Software Foundation, Inc.# This file is free software; the Free Software Foundation# gives unlimited permission to copy and/or distribute it,# with or without modifications, as long as this notice is preserved.# This program is distributed in the hope that it will be useful,# but WITHOUT ANY WARRANTY, to the extent permitted by law; without# even the implied warranty of MERCHANTABILITY or FITNESS FOR A# PARTICULAR PURPOSE.m4_ifndef([AC_AUTOCONF_VERSION],  [m4_copy([m4_PACKAGE_VERSION], [AC_AUTOCONF_VERSION])])dnlm4_if(AC_AUTOCONF_VERSION, [2.61],,[m4_warning([this file was generated for autoconf 2.61.You have another version of autoconf.  It may work, but is not guaranteed to.If you have problems, you may need to regenerate the build system entirely.To do so, use the procedure documented by the package, typically `autoreconf'.])])# Copyright (C) 2002, 2003, 2005, 2006, 2007  Free Software Foundation, Inc.## This file is free software; the Free Software Foundation# gives unlimited permission to copy and/or distribute it,# with or without modifications, as long as this notice is preserved.# AM_AUTOMAKE_VERSION(VERSION)# ----------------------------# Automake X.Y traces this macro to ensure aclocal.m4 has been# generated from the m4 files accompanying Automake X.Y.# (This private macro should not be called outside this file.)AC_DEFUN([AM_AUTOMAKE_VERSION],[am__api_version='1.10'dnl Some users find AM_AUTOMAKE_VERSION and mistake it for a way todnl require some minimum version.  Point them to the right macro.m4_if([$1], [1.10.1], [],      [AC_FATAL([Do not call $0, use AM_INIT_AUTOMAKE([$1]).])])dnl])# _AM_AUTOCONF_VERSION(VERSION)# -----------------------------# aclocal traces this macro to find the Autoconf version.# This is a private macro too.  Using m4_define simplifies# the logic in aclocal, which can simply ignore this definition.m4_define([_AM_AUTOCONF_VERSION], [])# AM_SET_CURRENT_AUTOMAKE_VERSION# -------------------------------# Call AM_AUTOMAKE_VERSION and AM_AUTOMAKE_VERSION so they can be traced.# This function is AC_REQUIREd by AC_INIT_AUTOMAKE.AC_DEFUN([AM_SET_CURRENT_AUTOMAKE_VERSION],[AM_AUTOMAKE_VERSION([1.10.1])dnlm4_ifndef([AC_AUTOCONF_VERSION],  [m4_copy([m4_PACKAGE_VERSION], [AC_AUTOCONF_VERSION])])dnl_AM_AUTOCONF_VERSION(AC_AUTOCONF_VERSION)])# AM_AUX_DIR_EXPAND                                         -*- Autoconf -*-# Copyright (C) 2001, 2003, 2005  Free Software Foundation, Inc.## This file is free software; the Free Software Foundation# gives unlimited permission to copy and/or distribute it,# with or without modifications, as long as this notice is preserved.# For projects using AC_CONFIG_AUX_DIR([foo]), Autoconf sets# $ac_aux_dir to `$srcdir/foo'.  In other projects, it is set to# `$srcdir', `$srcdir/..', or `$srcdir/../..'.## Of course, Automake must honor this variable whenever it calls a# tool from the auxiliary directory.  The problem is that $srcdir (and# therefore $ac_aux_dir as well) can be either absolute or relative,# depending on how configure is run.  This is pretty annoying, since# it makes $ac_aux_dir quite unusable in subdirectories: in the top# source directory, any form will work fine, but in subdirectories a# relative path needs to be adjusted first.## $ac_aux_dir/missing#    fails when called from a subdirectory if $ac_aux_dir is relative# $top_srcdir/$ac_aux_dir/missing#    fails if $ac_aux_dir is absolute,#    fails when called from a subdirectory in a VPATH build with#          a relative $ac_aux_dir## The reason of the latter failure is that $top_srcdir and $ac_aux_dir# are both prefixed by $srcdir.  In an in-source build this is usually# harmless because $srcdir is `.', but things will broke when you# start a VPATH build or use an absolute $srcdir.## So we could use something similar to $top_srcdir/$ac_aux_dir/missing,# iff we strip the leading $srcdir from $ac_aux_dir.  That would be:#   am_aux_dir='\$(top_srcdir)/'`expr "$ac_aux_dir" : "$srcdir//*\(.*\)"`# and then we would define $MISSING as#   MISSING="\${SHELL} $am_aux_dir/missing"# This will work as long as MISSING is not called from configure, because# unfortunately $(top_srcdir) has no meaning in configure.# However there are other variables, like CC, which are often used in# configure, and could therefore not use this "fixed" $ac_aux_dir.## Another solution, used here, is to always expand $ac_aux_dir to an# absolute PATH.  The drawback is that using absolute paths prevent a# configured tree to be moved without reconfiguration.AC_DEFUN([AM_AUX_DIR_EXPAND],[dnl Rely on autoconf to set up CDPATH properly.AC_PREREQ([2.50])dnl# expand $ac_aux_dir to an absolute patham_aux_dir=`cd $ac_aux_dir && pwd`])# AM_CONDITIONAL                                            -*- Autoconf -*-# Copyright (C) 1997, 2000, 2001, 2003, 2004, 2005, 2006# Free Software Foundation, Inc.## This file is free software; the Free Software Foundation# gives unlimited permission to copy and/or distribute it,# with or without modifications, as long as this notice is preserved.# serial 8# AM_CONDITIONAL(NAME, SHELL-CONDITION)# -------------------------------------# Define a conditional.AC_DEFUN([AM_CONDITIONAL],[AC_PREREQ(2.52)dnl ifelse([$1], [TRUE],  [AC_FATAL([$0: invalid condition: $1])],	[$1], [FALSE], [AC_FATAL([$0: invalid condition: $1])])dnlAC_SUBST([$1_TRUE])dnlAC_SUBST([$1_FALSE])dnl_AM_SUBST_NOTMAKE([$1_TRUE])dnl_AM_SUBST_NOTMAKE([$1_FALSE])dnlif $2; then  $1_TRUE=  $1_FALSE='#'else  $1_TRUE='#'  $1_FALSE=fiAC_CONFIG_COMMANDS_PRE([if test -z "${$1_TRUE}" && test -z "${$1_FALSE}"; then  AC_MSG_ERROR([[conditional "$1" was never defined.Usually this means the macro was only invoked conditionally.]])fi])])# Copyright (C) 1999, 2000, 2001, 2002, 2003, 2004, 2005, 2006# Free Software Foundation, Inc.## This file is free software; the Free Software Foundation# gives unlimited permission to copy and/or distribute it,# with or without modifications, as long as this notice is preserved.# serial 9# There are a few dirty hacks below to avoid letting `AC_PROG_CC' be# written in clear, in which case automake, when reading aclocal.m4,# will think it sees a *use*, and therefore will trigger all it's# C support machinery.  Also note that it means that autoscan, seeing# CC etc. in the Makefile, will ask for an AC_PROG_CC use...# _AM_DEPENDENCIES(NAME)# ----------------------# See how the compiler implements dependency checking.# NAME is "CC", "CXX", "GCJ", or "OBJC".# We try a few techniques and use that to set a single cache variable.## We don't AC_REQUIRE the corresponding AC_PROG_CC since the latter was# modified to invoke _AM_DEPENDENCIES(CC); we would have a circular# dependency, and given that the user is not expected to run this macro,# just rely on AC_PROG_CC.AC_DEFUN([_AM_DEPENDENCIES],[AC_REQUIRE([AM_SET_DEPDIR])dnlAC_REQUIRE([AM_OUTPUT_DEPENDENCY_COMMANDS])dnlAC_REQUIRE([AM_MAKE_INCLUDE])dnlAC_REQUIRE([AM_DEP_TRACK])dnlifelse([$1], CC,   [depcc="$CC"   am_compiler_list=],       [$1], CXX,  [depcc="$CXX"  am_compiler_list=],       [$1], OBJC, [depcc="$OBJC" am_compiler_list='gcc3 gcc'],       [$1], UPC,  [depcc="$UPC"  am_compiler_list=],       [$1], GCJ,  [depcc="$GCJ"  am_compiler_list='gcc3 gcc'],                   [depcc="$$1"   am_compiler_list=])AC_CACHE_CHECK([dependency style of $depcc],               [am_cv_$1_dependencies_compiler_type],[if test -z "$AMDEP_TRUE" && test -f "$am_depcomp"; then  # We make a subdir and do the tests there.  Otherwise we can end up  # making bogus files that we don't know about and never remove.  For  # instance it was reported that on HP-UX the gcc test will end up  # making a dummy file named `D' -- because `-MD' means `put the output  # in D'.  mkdir conftest.dir  # Copy depcomp to subdir because otherwise we won't find it if we're  # using a relative directory.  cp "$am_depcomp" conftest.dir  cd conftest.dir  # We will build objects and dependencies in a subdirectory because  # it helps to detect inapplicable dependency modes.  For instance  # both Tru64's cc and ICC support -MD to output dependencies as a  # side effect of compilation, but ICC will put the dependencies in  # the current directory while Tru64 will put them in the object  # directory.  mkdir sub  am_cv_$1_dependencies_compiler_type=none  if test "$am_compiler_list" = ""; then     am_compiler_list=`sed -n ['s/^#*\([a-zA-Z0-9]*\))$/\1/p'] < ./depcomp`  fi  for depmode in $am_compiler_list; do    # Setup a source with many dependencies, because some compilers    # like to wrap large dependency lists on column 80 (with \), and    # we should not choose a depcomp mode which is confused by this.    #    # We need to recreate these files for each test, as the compiler may    # overwrite some of them when testing with obscure command lines.    # This happens at least with the AIX C compiler.    : > sub/conftest.c    for i in 1 2 3 4 5 6; do      echo '#include "conftst'$i'.h"' >> sub/conftest.c      # Using `: > sub/conftst$i.h' creates only sub/conftst1.h with      # Solaris 8's {/usr,}/bin/sh.      touch sub/conftst$i.h    done    echo "${am__include} ${am__quote}sub/conftest.Po${am__quote}" > confmf    case $depmode in    nosideeffect)      # after this tag, mechanisms are not by side-effect, so they'll      # only be used when explicitly requested      if test "x$enable_dependency_tracking" = xyes; then	continue      else	break      fi      ;;    none) break ;;    esac    # We check with `-c' and `-o' for the sake of the "dashmstdout"    # mode.  It turns out that the SunPro C++ compiler does not properly    # handle `-M -o', and we need to detect this.    if depmode=$depmode \       source=sub/conftest.c object=sub/conftest.${OBJEXT-o} \       depfile=sub/conftest.Po tmpdepfile=sub/conftest.TPo \       $SHELL ./depcomp $depcc -c -o sub/conftest.${OBJEXT-o} sub/conftest.c \         >/dev/null 2>conftest.err &&       grep sub/conftst1.h sub/conftest.Po > /dev/null 2>&1 &&       grep sub/conftst6.h sub/conftest.Po > /dev/null 2>&1 &&       grep sub/conftest.${OBJEXT-o} sub/conftest.Po > /dev/null 2>&1 &&       ${MAKE-make} -s -f confmf > /dev/null 2>&1; then      # icc doesn't choke on unknown options, it will just issue warnings      # or remarks (even with -Werror).  So we grep stderr for any message      # that says an option was ignored or not supported.      # When given -MP, icc 7.0 and 7.1 complain thusly:      #   icc: Command line warning: ignoring option '-M'; no argument required      # The diagnosis changed in icc 8.0:      #   icc: Command line remark: option '-MP' not supported      if (grep 'ignoring option' conftest.err ||          grep 'not supported' conftest.err) >/dev/null 2>&1; then :; else        am_cv_$1_dependencies_compiler_type=$depmode        break      fi    fi  done  cd ..  rm -rf conftest.direlse  am_cv_$1_dependencies_compiler_type=nonefi])AC_SUBST([$1DEPMODE], [depmode=$am_cv_$1_dependencies_compiler_type])AM_CONDITIONAL([am__fastdep$1], [  test "x$enable_dependency_tracking" != xno \  && test "$am_cv_$1_dependencies_compiler_type" = gcc3])])# AM_SET_DEPDIR# -------------# Choose a directory name for dependency files.# This macro is AC_REQUIREd in _AM_DEPENDENCIESAC_DEFUN([AM_SET_DEPDIR],[AC_REQUIRE([AM_SET_LEADING_DOT])dnlAC_SUBST([DEPDIR], ["${am__leading_dot}deps"])dnl])# AM_DEP_TRACK# ------------AC_DEFUN([AM_DEP_TRACK],[AC_ARG_ENABLE(dependency-tracking,[  --disable-dependency-tracking  speeds up one-time build  --enable-dependency-tracking   do not reject slow dependency extractors])if test "x$enable_dependency_tracking" != xno; then  am_depcomp="$ac_aux_dir/depcomp"  AMDEPBACKSLASH='\'fiAM_CONDITIONAL([AMDEP], [test "x$enable_dependency_tracking" != xno])AC_SUBST([AMDEPBACKSLASH])dnl_AM_SUBST_NOTMAKE([AMDEPBACKSLASH])dnl