blob: 93a9e6a8adec59e97cfea571cfd5edfa5a898358 [file] [log] [blame]
# Process this file with autoconf to produce a configure script.
# Copyright (C) 1995-2024 Free Software Foundation, Inc.
#
# This program is free software; you can redistribute it and/or modify
# it under the terms of the GNU General Public License as published by
# the Free Software Foundation; either version 2, or (at your option)
# any later version.
#
# This program is distributed in the hope that it will be useful,
# but WITHOUT ANY WARRANTY; without even the implied warranty of
# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
# GNU General Public License for more details.
#
# You should have received a copy of the GNU General Public License
# along with this program. If not, see <https://www.gnu.org/licenses/>.
AC_PREREQ([2.69])
AC_INIT([GNU Automake], [1.16.92], [bug-automake@gnu.org])
AC_CONFIG_SRCDIR([bin/automake.in])
AC_CONFIG_AUX_DIR([lib])
AM_SILENT_RULES([yes])
AC_CANONICAL_HOST
AC_CANONICAL_BUILD
# Save the AUTOCONF setting before AM_INIT_AUTOMAKE overrides it; this
# way we can run Autoconf tests from configure (or from the test
# suite) without being bothered by 'missing'. Likewise for autom4te,
# autoreconf, autoheader, and autoupdate.
AC_SUBST([am_AUTOCONF], ["${AUTOCONF-autoconf}"])
AC_SUBST([am_AUTOM4TE], ["${AUTOM4TE-autom4te}"])
AC_SUBST([am_AUTORECONF], ["${AUTORECONF-autoreconf}"])
AC_SUBST([am_AUTOHEADER], ["${AUTOHEADER-autoheader}"])
AC_SUBST([am_AUTOUPDATE], ["${AUTOUPDATE-autoupdate}"])
dnl We call AC_PROG_CC in an unusual way, and only for use in our
dnl testsuite, so also use 'no-dependencies' and 'no-define' among
dnl the automake options to avoid bloating and potential problems.
AM_INIT_AUTOMAKE([-Wall -Werror dist-xz filename-length-max=99
no-define no-dependencies])
# Keep this on a line of its own, since it must be found and processed
# by the 'update-copyright' rule in our Makefile.
RELEASE_YEAR=2024
AC_SUBST([RELEASE_YEAR])
# The API version is the base version. We must guarantee
# compatibility for all releases with the same API version.
APIVERSION=1.16
AC_SUBST([APIVERSION])
AC_SUBST([pkgvdatadir], ["\${datadir}/$PACKAGE-$APIVERSION"])
AC_SUBST([scriptdir], ["\${pkgvdatadir}"])
AC_SUBST([amdir], ["\${pkgvdatadir}/am"])
AC_SUBST([automake_acdir], ["\${datadir}/aclocal-$APIVERSION"])
AC_SUBST([system_acdir], ["\${datadir}/aclocal"])
# Our build system is bootstrapped with the bleeding-edge versions of
# aclocal and automake, hence the remake rules must use those versions
# as well. The extra quoting is to cater to cases when the build
# directory contains whitespace or shell metacharacters.
ACLOCAL="\"`pwd`/pre-inst-env\" aclocal-$APIVERSION"
AUTOMAKE="\"`pwd`/pre-inst-env\" automake-$APIVERSION"
AC_PROG_LN_S
AC_PATH_PROG([PERL], [perl])
case $PERL in
'')
AC_MSG_ERROR([perl not found])
;;
*' '* | *' '*)
AC_MSG_ERROR([The path to your Perl contains spaces or tabs.
This would cause build failures later or unusable programs.
Please use a path without spaces and try again.])
;;
esac
# Save details about the selected perl interpreter in config.log.
AM_RUN_LOG([$PERL --version])
$PERL -e 'require 5.006;' || {
AC_MSG_ERROR(
[perl 5.6 or better is required; perl 5.10 or better
is recommended. If you have several perl versions
installed, select the one Automake should use using
./configure PERL=/path/to/perl])
}
# The test suite will skip some tests if tex is absent.
AC_CHECK_PROG([TEX], [tex], [tex])
# Save details about the selected TeX program in config.log.
# Redirect input from /dev/null, as TeX might otherwise hang waiting
# for input from the terminal.
AM_RUN_LOG([$TEX --version </dev/null])
# The test suite will skip some tests if no lex or yacc program is
# available.
# We don't use AC_PROG_LEX nor AC_PROG_YACC here because:
# 1. we don't want flex (resp. bison) to be preferred to system lex
# (resp. system yacc);
# 2. we don't want $LEX (resp. $YACC) to be defined to ':' (resp. 'yacc')
# by default;
# 3. we prefer not to have the variables YFLAGS, LEX_OUTPUT_ROOT and
# LEXLIB to be calculated and/or AC_SUBST'd;
# 4. we prefer that the YACC and LEX variables are not reported in the
# configure help screen.
AC_CHECK_PROGS([YACC], [yacc byacc 'bison -y'], [false])
AC_CHECK_PROGS([LEX], [lex flex], [false])
# Test for Autoconf. We run Autoconf in a subdirectory to ease
# deletion of any files created (such as those added to
# autom4te.cache). We used to perform only the last of the three
# following tests, but some users were unable to figure out that their
# installation was broken since --version appeared to work.
AC_SUBST([required_autoconf_version], [2.65])
AC_CACHE_CHECK([whether autoconf is installed], [am_cv_autoconf_installed],
[if AM_RUN_LOG([$am_AUTOCONF --version]);
then
am_cv_autoconf_installed=yes
else
am_cv_autoconf_installed=no
fi])
if test "$am_cv_autoconf_installed" = no; then
AC_MSG_ERROR([Autoconf $required_autoconf_version or better is required.
Please make sure it is installed and in your PATH.])
fi
AC_CACHE_CHECK([whether autoconf works], [am_cv_autoconf_works],
[mkdir conftest
printf '%s\n' > conftest/conftest.ac \
'AC''_INIT([smoke-test], [1])' \
'AC''_OUTPUT'
if AM_RUN_LOG([cd conftest && $am_AUTOCONF -o /dev/null conftest.ac]);
then
am_cv_autoconf_works=yes
else
am_cv_autoconf_works=no
fi
rm -rf conftest])
if test "$am_cv_autoconf_works" = no; then
AC_MSG_ERROR([The installed version of autoconf does not work.
Please check config.log for error messages before this one.])
fi
AC_CACHE_CHECK([whether autoconf is recent enough], [am_cv_autoconf_version],
[mkdir conftest
dnl Creative quoting required to avoid spurious expansion of AC_PREREQ macro
printf '%s\n' > conftest/conftest.ac \
'AC'"_PREREQ([[$required_autoconf_version]])" \
'AC''_INIT([smoke-test], [1])' \
'AC''_OUTPUT'
if AM_RUN_LOG([cd conftest && $am_AUTOCONF -o /dev/null conftest.ac]);
then
am_cv_autoconf_version=yes
else
am_cv_autoconf_version=no
fi
rm -rf conftest])
if test "$am_cv_autoconf_version" = no; then
AC_MSG_ERROR([Autoconf $required_autoconf_version or better is required.])
fi
# Test for ln. We need use it to install the versioned binaries.
AC_MSG_CHECKING([whether ln works])
AC_CACHE_VAL([am_cv_prog_ln], [
rm -f conftest conftest.file
: >conftest.file
if ln conftest.file conftest 2>/dev/null; then
am_cv_prog_ln=ln
else
am_cv_prog_ln='cp -p'
fi
rm -f conftest conftest.file])
AC_SUBST([LN], [$am_cv_prog_ln])
result=no
test "x$am_cv_prog_ln" = xln && result=yes
AC_MSG_RESULT([$result])
## ------------------------------------------- ##
## Test for things needed by the test suite. ##
## ------------------------------------------- ##
AC_PROG_EGREP
AC_PROG_FGREP
# The test suite needs to know the resolution of timestamps
# supported by the filesystem hosting the build. The value
# will be acceptable to 'sleep' on this system.
MTIME_RESOLUTION=$am_cv_filesystem_timestamp_resolution
if test -z "$MTIME_RESOLUTION"; then
AC_MSG_NOTICE(am_cv_filesystem_timestamp_resolution strangely not set; using 1)
MTIME_RESOLUTION=1
fi
AC_SUBST([MTIME_RESOLUTION])
dnl FIXME: could we extract this in a simpler way through autoconf
dnl FIXME: idioms or internals?
AC_DEFUN(
[_AM_INIT_BOURNE_COMPATIBLE_VAR],
[am_bourne_compatible="AS_ESCAPE(_m4_expand([AS_BOURNE_COMPATIBLE]))"])
dnl
dnl Arguments to this macro:
dnl
dnl $1 - shell to test
dnl $2 - description of the tested feature
dnl $3 - shell code used to check the feature; to indicate success,
dnl it can either exit with status 77, or have the last command
dnl returning with exit status of zero
dnl $4 - shell code to execute if the check on the shell is successful
dnl (defaults to nothing)
dnl $5 - shell code to execute if the check on the shell is not
dnl successful (defaults to nothing)
dnl
AC_DEFUN([_AM_CHECK_SHELL_FEATURE],
[AC_REQUIRE([_AM_INIT_BOURNE_COMPATIBLE_VAR])
AC_MSG_CHECKING([whether $1 $2])
if { $1 -c "$am_bourne_compatible
AS_ESCAPE([$3])
test \$? -eq 0 || exit 1
# Use 77 to indicate success (rather than 0), in case some shell
# acts like Solaris 10's /bin/sh, exiting successfully on some
# syntax errors.
exit 77" >&AS_MESSAGE_LOG_FD 2>&1; test $? -eq 77; }
then
AC_MSG_RESULT([yes])
$4
else
AC_MSG_RESULT([no])
$5
fi])
# AM_CHECK_CANDIDATE_TEST_SHELL(SHELL-PATH)
# -----------------------------------------
#
# Check if the given shell is good enough to run our test scripts.
# Inspired to gnulib's 'tests/init.sh'.
#
# We require POSIX and XSI features (e.g., '$(...)' for command
# substitutions, '$((...))' for shell arithmetic, and support for
# '${var#...}' and '${var%...}' parameter expansions).
#
# We require that the shell can correctly trap EXIT when 'set -e' is in
# effect (OSF1/Tru64 sh failed to do so, see commit v1.10b-52-g9fe8259).
#
# We want to able to define shell aliases with the same name of shell
# builtins.
#
# We also prefer shells that, when 'set -x' is in effect, do not also
# redirect traces upon stderr redirections. For example,
# $ set -x; echo x 2>file
# would emit "+ echo x" into file with older zsh versions. Similarly,
# $ set -x; P=1 true 2>file
# would emit "P=1" into file with /usr/xpg4/bin/sh from Solaris 10 and
# /bin/sh from SunOS 5.11 and OpenBSD 4.7.
#
# Use '$am_score' to indicate the degree of acceptability of the shell.
# A score of "10" means that the shell is good enough for our needs;
# a score of "9" means that the shell has some minor bugs or limitation,
# but is still (barely) acceptable for our uses. Any other score means
# that the shell is broken or unfit.
#
AC_DEFUN([_AM_CHECK_CANDIDATE_SHELL],
[am_score=10
while :; do
_AM_CHECK_SHELL_FEATURE([$1],
[supports \$(cmd)],
[test "$(echo x)" = x],
[], [am_score=1; break])
_AM_CHECK_SHELL_FEATURE([$1],
[supports \$((expr))],
[test $((1 + 2 * 3)) = 7],
[], [am_score=1; break])
_AM_CHECK_SHELL_FEATURE([$1],
[supports \${@%:@var}],
[zero='' one='x' twelve=' foobar baz!' \
&& test ${@%:@zero} -eq 0 \
&& test ${@%:@one} -eq 1 \
&& test ${@%:@twelve} -eq 12],
[], [am_score=1; break])
_AM_CHECK_SHELL_FEATURE([$1],
[supports \${var@%:@glob} and \${var%glob}],
[v=a/b/c \
&& test ${v@%:@*/} = b/c \
&& test ${v@%:@@%:@*/} = c \
&& test ${v%/*} = a/b \
&& test ${v%%/*} = a],
[], [am_score=1; break])
_AM_CHECK_SHELL_FEATURE([$1],
[preserves exit traps with "set -e"],
[set -e; trap 'exit $?' 0; (exit 77); exit 77],
[], [am_score=1; break])
_AM_CHECK_SHELL_FEATURE([$1],
[can define exit traps in a shell function],
[fail=0 && foo() { trap 'fail=1' 0; } && foo && test $fail = 0],
[], [am_score=1; break])
_AM_CHECK_SHELL_FEATURE([$1],
[corrupts stderr with "set -x"],
[(set -x; P=1 true 2>&3) 3>&1 2>/dev/null | grep P=1],
[am_score=9], [])
echo 'return 34' > conftest-return.sh
echo 'ok=no' >> conftest-return.sh
_AM_CHECK_SHELL_FEATURE([$1],
[can return early from "dot-sourced" files],
[ok=yes; . ./conftest-return.sh; test $? -eq 34 && test $ok = yes],
[rm -f conftest-return.sh],
[rm -f conftest-return.sh; am_score=1; break])
echo 'alias false=echo' > conftest-alias.sh
echo 'false && test "$(false 97)" = 97' >> conftest-alias.sh
_AM_CHECK_SHELL_FEATURE([$1],
[supports alias named like shell builtins],
[. ./conftest-alias.sh],
[rm -f conftest-alias.sh],
[rm -f conftest-alias.sh; am_score=1; break])
_AM_CHECK_SHELL_FEATURE([$1],
[supports "test -e"],
[test -e config.log && test -e . && test ! -e nonesuch],
[], [am_score=1; break])
break
done])
# These messages only goes to the config.log file.
AC_MSG_NOTICE([will now look for a sturdy POSIX shell, for our testsuite])
AC_CACHE_VAL(
[ac_cv_AM_TEST_RUNNER_SHELL],
[if test "$AM_TEST_RUNNER_SHELL"; then
# Let the user override it.
ac_cv_AM_TEST_RUNNER_SHELL=$AM_TEST_RUNNER_SHELL
else
ac_cv_AM_TEST_RUNNER_SHELL=no
am_candidate_shells=${CONFIG_SHELL-}
# For the benefit of Solaris.
am_PATH=$PATH$PATH_SEPARATOR/usr/xpg6/bin$PATH_SEPARATOR/usr/xpg4/bin
for am_sh in sh sh5 dash ash bash zsh ksh pdksh; do
AC_PATH_PROG([am_candidate_sh], [$am_sh], [], [$am_PATH])
if test -n "$am_candidate_sh"; then
am_candidate_shells="$am_candidate_shells $am_candidate_sh"
fi
AM_SUBST_NOTMAKE([am_candidate_sh])
# Must nullify these in order not to interfere with the checks in
# the next loop.
AS_UNSET([am_candidate_sh])
AS_UNSET([ac_cv_path_am_candidate_sh])
done
AS_UNSET([am_PATH]) # Not required anymore
for am_sh in $am_candidate_shells; do
am_score=0
_AM_CHECK_CANDIDATE_SHELL([$am_sh])
if test $am_score -eq 9; then
# The shell is barely acceptable for our needs. We might
# still find one that is even better, so continue looking.
AC_MSG_NOTICE([shell $am_sh is acceptable, but we might do better])
ac_cv_AM_TEST_RUNNER_SHELL=$am_sh
elif test $am_score -eq 10; then
AC_MSG_NOTICE([shell $am_sh is good enough, stop looking])
ac_cv_AM_TEST_RUNNER_SHELL=$am_sh
break
fi
done
fi
AM_TEST_RUNNER_SHELL=$ac_cv_AM_TEST_RUNNER_SHELL])
if test $AM_TEST_RUNNER_SHELL = no; then
AC_MSG_FAILURE([m4_normalize([no POSIX shell found that is good
enough to be used in our testsuite])])
else
AC_MSG_NOTICE([will use $AM_TEST_RUNNER_SHELL as the testsuite shell])
fi
AC_ARG_VAR([AM_TEST_RUNNER_SHELL],
[a sturdy POSIX shell for our testsuite])
###########################################################################
# Look for C, C++ and fortran compilers to be used in the testsuite.
dnl We don't want to abort our configuration script if no C compiler is
dnl available, as such a compiler is only required to run part of the
dnl testsuite, not to build or install Automake. Ditto for C++, Fortran
dnl and Fortran 77 compilers. Unfortunately, autoconf does not offer an
dnl easy way to obtain this behavior, so we'll need a few hacks.
dnl We want the body of this macro to expand as a single shell statement,
dnl thus we wrap it into { ... } brackets.
AC_DEFUN([_AM_WRAP_MSG_ERROR], [ {
AC_MSG_WARN([$1])
am__failed=yes
break
} ])
AC_DEFUN([_AM_COMPILER_CAN_FAIL], [
m4_pushdef([AC_MSG_FAILURE], m4_defn([_AM_WRAP_MSG_ERROR]))
m4_pushdef([AC_MSG_ERROR], m4_defn([_AM_WRAP_MSG_ERROR]))
am__failed=no
while :; do
$1
break
done
AS_IF([test $am__failed = yes], [$2])
# We have to clear these cache variables, so that future checks on
# compilers for different languages won't be confused.
unset ac_cv_objext ac_cv_exeext
# We also need to meddle with the autoconf internals to ensure that
# checks to find object and executable extensions will be run anew.
# FIXME: In the long run, the better thing to do would be to fix
# FIXME: autoconf instead ...
m4_undefine([m4_provide(_AC_COMPILER_OBJEXT)])
m4_undefine([m4_provide(_AC_COMPILER_EXEEXT)])
m4_popdef([AC_MSG_FAILURE])
m4_popdef([AC_MSG_ERROR])
])
AC_DEFUN([_AM_SKIP_COMP_TESTS],
[AC_MSG_NOTICE([tests requiring the $1 compiler will be skipped])])
# Prefer generic compilers to GNU ones when possible. This will ensure
# more testsuite coverage "in the wild".
# Note that we don't look for the MSVC C/C++ compiler here. This is
# deliberate; for more discussion and rationale, see:
# <https://lists.gnu.org/archive/html/automake-patches/2012-01/msg00130.html>
AC_MSG_NOTICE([will now look for generic compilers])
# C compiler.
_AM_COMPILER_CAN_FAIL(dnl
[AC_PROG_CC([cc gcc])],
[CC=false; _AM_SKIP_COMP_TESTS([C])])
AS_IF([test x"$GCC" = x"yes"], [am_CC_is_GNU=yes], [am_CC_is_GNU=no])
# On case-insensitive file systems (seen e.g. on Cygwin and Mac OS X)
# we must avoid looking for 'CC', because that would be the same as
# 'cc', and could cause $CXX to point to the C compiler, instead of
# to a C++ compiler as expected (see automake bugs #11893 and #10766).
# Similarly, we must avoid looking for 'RCC', as that can point to the
# Qt4 "Resource Compiler": <http://doc.qt.digia.com/4.2/rcc.html>
# And we avoid looking for 'KCC' as that can be a kerberos tool under
# macOS systems.
if test -f /bIn/rMdIr || test -f /uSr/bIn/rMdIr; then
# Case-insensitive file system, don't look for CC.
am_CC= am_RCC= am_KCC=
else
am_CC=CC am_RCC=RCC am_KCC=KCC
fi
# The list of C++ compilers here has been copied, pasted and edited
# from 'lib/autoconf/c.m4:AC_PROG_CXX' in the Autoconf distribution.
# Keep it in sync, or better again, find out a way to avoid this code
# duplication.
_AM_COMPILER_CAN_FAIL([AC_PROG_CXX(dnl
[aCC $am_CC FCC $am_KCC $am_RCC xlC_r xlC c++ cxx cc++ gpp g++ clang++])],
[CXX=false; _AM_SKIP_COMP_TESTS([C++])])
AS_IF([test x"$GXX" = x"yes"], [am_CXX_is_GNU=yes], [am_CXX_is_GNU=no])
# The lists of Fortran compilers here has been copied, pasted and edited
# from file 'lib/autoconf/fortran.m4' in the Autoconf distribution.
# Keep it in sync, or better again, find out a way to avoid this code
# duplication.
_AM_COMPILER_CAN_FAIL([AC_PROG_FC(dnl
[xlf95 f95 fort ifort ifc efc pgfortran pgf95 lf95 ftn nagfor] dnl
[xlf90 f90 armflang flang pgf90 pghpf epcf90 g95 gfortran])],
[FC=false; _AM_SKIP_COMP_TESTS([Fortran])])
AS_IF([test x"$GFC" = x"yes"], [am_FC_is_GNU=yes], [am_FC_is_GNU=no])
_AM_COMPILER_CAN_FAIL([AC_PROG_F77(dnl
[xlf f77 frt pgf77 cf77 fort77 fl32 af77 g77 armflang flang gfortran])],
[F77=false; _AM_SKIP_COMP_TESTS([Fortran 77])])
AS_IF([test x"$G77" = x"yes"], [am_F77_is_GNU=yes], [am_F77_is_GNU=no])
# Some tests will need the GNU compilers. Searching for them here would
# be overkill, since our testsuite already handles their search and setup
# pretty well. But in case the compilers already found are the GNU ones,
# we want to use them in the testsuite where GNU compilers are required.
# Also, in case the compilers detected above (at configure time) are not
# the GNU ones, we cannot use the values of CFLAGS, CXXFLAGS, FCFLAGS and
# FFLAGS detected for them with the GNU compilers too, since it's likely
# they won't be compatible. So we allow the user to define variants of
# these variables for the GNU compilers separately.
AC_MSG_NOTICE([will now look for GNU compilers])
# GNU C compiler.
AC_ARG_VAR([GNU_CC], [GNU C compiler])
AC_ARG_VAR([GNU_CFLAGS], [GNU C compiler flags])
if test $am_CC_is_GNU = yes; then
AC_MSG_NOTICE([$CC is already a GNU C compiler])
GNU_CC=$CC GNU_CFLAGS=${GNU_CFLAGS-$CFLAGS}
else
AC_CHECK_TOOLS([GNU_CC], [gcc], [false])
fi
if test "$GNU_CC" != false; then
AS_IF([AM_RUN_LOG([$GNU_CC --version && $GNU_CC -v])], [],
[AC_MSG_WARN([botched installation for GNU C compiler])
_AM_SKIP_COMP_TESTS([GNU C])])
fi
# GNU C++ compiler.
AC_ARG_VAR([GNU_CXX], [GNU C++ compiler])
AC_ARG_VAR([GNU_CXXFLAGS], [GNU C++ compiler flags])
if test $am_CXX_is_GNU = yes; then
AC_MSG_NOTICE([$CXX is already a GNU C++ compiler])
GNU_CXX=$CXX
GNU_CXXFLAGS=${GNU_CXXFLAGS-$CXXFLAGS}
else
AC_CHECK_TOOLS([GNU_CXX], [g++ gpp], [false])
fi
if test "$GNU_CXX" != false; then
AS_IF([AM_RUN_LOG([$GNU_CXX --version && $GNU_CXX -v])], [],
[AC_MSG_WARN([botched installation for GNU C++ compiler])
_AM_SKIP_COMP_TESTS([GNU C++])])
fi
# GNU Fortran compiler.
AC_ARG_VAR([GNU_FC], [GNU Fortran compiler])
AC_ARG_VAR([GNU_FCFLAGS], [GNU Fortran compiler flags])
if test $am_FC_is_GNU = yes; then
AC_MSG_NOTICE([$FC is already a GNU Fortran compiler])
GNU_FC=$FC
GNU_FCFLAGS=${GNU_FCFLAGS-$FCFLAGS}
else
AC_CHECK_TOOLS([GNU_FC], [gfortran], [false])
fi
if test "$GNU_FC" != false; then
AS_IF([AM_RUN_LOG([$GNU_FC --version && $GNU_FC -v])], [],
[AC_MSG_WARN([botched installation for GNU Fortran compiler])
_AM_SKIP_COMP_TESTS([GNU Fortran])])
fi
# GNU Fortran 77 compiler.
AC_ARG_VAR([GNU_F77], [GNU Fortran 77 compiler])
AC_ARG_VAR([GNU_FFLAGS], [GNU Fortran 77 compiler flags])
if test $am_F77_is_GNU = yes; then
AC_MSG_NOTICE([$F77 is already a GNU Fortran 77 compiler])
GNU_F77=$F77
GNU_FFLAGS=${GNU_FFLAGS-$FFLAGS}
else
AC_CHECK_TOOLS([GNU_F77], [g77 gfortran], [false])
fi
if test "$GNU_F77" != false; then
AS_IF([AM_RUN_LOG([$GNU_F77 --version && $GNU_F77 -v])], [],
[AC_MSG_WARN([botched installation for GNU Fortran 77 compiler])
_AM_SKIP_COMP_TESTS([GNU Fortran 77])])
fi
# GNU Java compiler.
AC_ARG_VAR([GNU_GCJ], [GNU Java compiler])
AC_ARG_VAR([GNU_GCJFLAGS], [GNU Java compiler flags])
AC_CHECK_TOOLS([GNU_GCJ], [gcj], [false])
if test "$GNU_GCJ" != false; then
AS_IF([AM_RUN_LOG([$GNU_GCJ --version && $GNU_GCJ -v])], [],
[AC_MSG_WARN([botched installation for GNU Java compiler])
_AM_SKIP_COMP_TESTS([GNU Java])])
fi
# If we have been able to find at least a working compiler above, we
# know what the object and executable extensions for this platform are.
OBJEXT=${ac_cv_objext-UNKNOWN}
EXEEXT=${ac_cv_exeext-UNKNOWN}
AC_SUBST([OBJEXT])
AC_SUBST([EXEEXT])
###########################################################################
## ---------------------- ##
## Create output files. ##
## ---------------------- ##
AC_CONFIG_FILES([Makefile])
AC_CONFIG_LINKS([GNUmakefile:GNUmakefile])
AC_CONFIG_FILES([pre-inst-env], [chmod +x pre-inst-env])
AC_OUTPUT
# Inform the user if this version of automake is a beta release or
# a development snapshot. Except, as of 1.17 (January 2024), don't bother.
# Just call all pretests development snapshots.
#
am_stable_version_rx='[[1-9]\.[0-9]+(\.[0-9]+)?]'
# This won't match anything as of 1.17, since we switched to
# .90-numbered test releases. But if we wanted to, according to HACKING,
# the version of a development snapshot should end with an odd number
# (91, 93, ...) and a beta release should end with an even number (90,
# 92, ...).
am_beta_version_rx="[$am_stable_version_rx[bdfhjlnprtvxz]]" # no match
am_release_type=`AS_ECHO(["$PACKAGE_VERSION"]) | LC_ALL=C awk ["
/^$am_stable_version_rx$/ { print \"stable\"; exit(0); }
/^$am_beta_version_rx$/ { print \"beta version\"; exit(0); }
{ print \"development snapshot\"; }"]`
# '$silent' is set to yes if configure is passed the '--quiet' option.
test "$am_release_type" = stable || test "$silent" = yes || cat <<EOF
WARNING: You are about to use a $am_release_type of automake.
WARNING: It could well suffer from new bugs or regressions.
WARNING: You are strongly advised not to use it in production code.
Please report bugs, problems and feedback to <AC_PACKAGE_BUGREPORT>,
since that is the whole point of a test release.
EOF
AS_EXIT([0])