⭐ 欢迎来到虫虫下载站! | 📦 资源下载 📁 资源专辑 ℹ️ 关于我们
⭐ 虫虫下载站

📄 aclocal.m4

📁 linux文本方式下的外挂中文环境,很好用,有源码.功能很全.我都用它
💻 M4
📖 第 1 页 / 共 5 页
字号:
# aclocal.m4 generated automatically by aclocal 1.5# Copyright 1996, 1997, 1998, 1999, 2000, 2001# 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.# Do all the work for Automake.  This macro actually does too much --# some checks are only needed if your package does certain things.# But this isn't really a big deal.# serial 5# 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...# We require 2.13 because we rely on SHELL being computed by configure.AC_PREREQ([2.13])# AC_PROVIDE_IFELSE(MACRO-NAME, IF-PROVIDED, IF-NOT-PROVIDED)# -----------------------------------------------------------# If MACRO-NAME is provided do IF-PROVIDED, else IF-NOT-PROVIDED.# The purpose of this macro is to provide the user with a means to# check macros which are provided without letting her know how the# information is coded.# If this macro is not defined by Autoconf, define it here.ifdef([AC_PROVIDE_IFELSE],      [],      [define([AC_PROVIDE_IFELSE],              [ifdef([AC_PROVIDE_$1],                     [$2], [$3])])])# AM_INIT_AUTOMAKE(PACKAGE,VERSION, [NO-DEFINE])# ----------------------------------------------AC_DEFUN([AM_INIT_AUTOMAKE],[AC_REQUIRE([AC_PROG_INSTALL])dnl# test to see if srcdir already configuredif test "`CDPATH=:; cd $srcdir && pwd`" != "`pwd`" &&   test -f $srcdir/config.status; then  AC_MSG_ERROR([source directory already configured; run \"make distclean\" there first])fi# Define the identity of the package.PACKAGE=$1AC_SUBST(PACKAGE)dnlVERSION=$2AC_SUBST(VERSION)dnlifelse([$3],,[AC_DEFINE_UNQUOTED(PACKAGE, "$PACKAGE", [Name of package])AC_DEFINE_UNQUOTED(VERSION, "$VERSION", [Version number of package])])# Autoconf 2.50 wants to disallow AM_ names.  We explicitly allow# the ones we care about.ifdef([m4_pattern_allow],      [m4_pattern_allow([^AM_[A-Z]+FLAGS])])dnl# Autoconf 2.50 always computes EXEEXT.  However we need to be# compatible with 2.13, for now.  So we always define EXEEXT, but we# don't compute it.AC_SUBST(EXEEXT)# Similar for OBJEXT -- only we only use OBJEXT if the user actually# requests that it be used.  This is a bit dumb.: ${OBJEXT=o}AC_SUBST(OBJEXT)# Some tools Automake needs.AC_REQUIRE([AM_SANITY_CHECK])dnlAC_REQUIRE([AC_ARG_PROGRAM])dnlAM_MISSING_PROG(ACLOCAL, aclocal)AM_MISSING_PROG(AUTOCONF, autoconf)AM_MISSING_PROG(AUTOMAKE, automake)AM_MISSING_PROG(AUTOHEADER, autoheader)AM_MISSING_PROG(MAKEINFO, makeinfo)AM_MISSING_PROG(AMTAR, tar)AM_PROG_INSTALL_SHAM_PROG_INSTALL_STRIP# We need awk for the "check" target.  The system "awk" is bad on# some platforms.AC_REQUIRE([AC_PROG_AWK])dnlAC_REQUIRE([AC_PROG_MAKE_SET])dnlAC_REQUIRE([AM_DEP_TRACK])dnlAC_REQUIRE([AM_SET_DEPDIR])dnlAC_PROVIDE_IFELSE([AC_PROG_][CC],                  [_AM_DEPENDENCIES(CC)],                  [define([AC_PROG_][CC],                          defn([AC_PROG_][CC])[_AM_DEPENDENCIES(CC)])])dnlAC_PROVIDE_IFELSE([AC_PROG_][CXX],                  [_AM_DEPENDENCIES(CXX)],                  [define([AC_PROG_][CXX],                          defn([AC_PROG_][CXX])[_AM_DEPENDENCIES(CXX)])])dnl])## Check to make sure that the build environment is sane.## serial 3# AM_SANITY_CHECK# ---------------AC_DEFUN([AM_SANITY_CHECK],[AC_MSG_CHECKING([whether build environment is sane])# Just in casesleep 1echo timestamp > conftest.file# Do `set' in a subshell so we don't clobber the current shell's# arguments.  Must try -L first in case configure is actually a# symlink; some systems play weird games with the mod time of symlinks# (eg FreeBSD returns the mod time of the symlink's containing# directory).if (   set X `ls -Lt $srcdir/configure conftest.file 2> /dev/null`   if test "$[*]" = "X"; then      # -L didn't work.      set X `ls -t $srcdir/configure conftest.file`   fi   rm -f conftest.file   if test "$[*]" != "X $srcdir/configure conftest.file" \      && test "$[*]" != "X conftest.file $srcdir/configure"; then      # If neither matched, then we have a broken ls.  This can happen      # if, for instance, CONFIG_SHELL is bash and it inherits a      # broken ls alias from the environment.  This has actually      # happened.  Such a system could not be considered "sane".      AC_MSG_ERROR([ls -t appears to fail.  Make sure there is not a brokenalias in your environment])   fi   test "$[2]" = conftest.file   )then   # Ok.   :else   AC_MSG_ERROR([newly created file is older than distributed files!Check your system clock])fiAC_MSG_RESULT(yes)])# serial 2# AM_MISSING_PROG(NAME, PROGRAM)# ------------------------------AC_DEFUN([AM_MISSING_PROG],[AC_REQUIRE([AM_MISSING_HAS_RUN])$1=${$1-"${am_missing_run}$2"}AC_SUBST($1)])# AM_MISSING_HAS_RUN# ------------------# Define MISSING if not defined so far and test if it supports --run.# If it does, set am_missing_run to use it, otherwise, to nothing.AC_DEFUN([AM_MISSING_HAS_RUN],[AC_REQUIRE([AM_AUX_DIR_EXPAND])dnltest x"${MISSING+set}" = xset || MISSING="\${SHELL} $am_aux_dir/missing"# Use eval to expand $SHELLif eval "$MISSING --run true"; then  am_missing_run="$MISSING --run "else  am_missing_run=  am_backtick='`'  AC_MSG_WARN([${am_backtick}missing' script is too old or missing])fi])# AM_AUX_DIR_EXPAND# 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], [# expand $ac_aux_dir to an absolute patham_aux_dir=`CDPATH=:; cd $ac_aux_dir && pwd`])# AM_PROG_INSTALL_SH# ------------------# Define $install_sh.AC_DEFUN([AM_PROG_INSTALL_SH],[AC_REQUIRE([AM_AUX_DIR_EXPAND])dnlinstall_sh=${install_sh-"$am_aux_dir/install-sh"}AC_SUBST(install_sh)])# One issue with vendor `install' (even GNU) is that you can't# specify the program used to strip binaries.  This is especially# annoying in cross-compiling environments, where the build's strip# is unlikely to handle the host's binaries.# Fortunately install-sh will honor a STRIPPROG variable, so we# always use install-sh in `make install-strip', and initialize# STRIPPROG with the value of the STRIP variable (set by the user).AC_DEFUN([AM_PROG_INSTALL_STRIP],[AC_REQUIRE([AM_PROG_INSTALL_SH])dnlINSTALL_STRIP_PROGRAM="\${SHELL} \$(install_sh) -c -s"AC_SUBST([INSTALL_STRIP_PROGRAM])])# serial 4						-*- Autoconf -*-# 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" 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], 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  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    # 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.    echo '#include "conftest.h"' > conftest.c    echo 'int i;' > conftest.h    echo "${am__include} ${am__quote}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=conftest.c object=conftest.o \       depfile=conftest.Po tmpdepfile=conftest.TPo \       $SHELL ./depcomp $depcc -c conftest.c -o conftest.o >/dev/null 2>&1 &&       grep conftest.h conftest.Po > /dev/null 2>&1 &&       ${MAKE-make} -s -f confmf > /dev/null 2>&1; then      am_cv_$1_dependencies_compiler_type=$depmode      break    fi  done  cd ..  rm -rf conftest.direlse  am_cv_$1_dependencies_compiler_type=nonefi])$1DEPMODE="depmode=$am_cv_$1_dependencies_compiler_type"AC_SUBST([$1DEPMODE])])# AM_SET_DEPDIR# -------------

⌨️ 快捷键说明

复制代码 Ctrl + C
搜索代码 Ctrl + F
全屏模式 F11
切换主题 Ctrl + Shift + D
显示快捷键 ?
增大字号 Ctrl + =
减小字号 Ctrl + -