AC_CHECK_FUNC and AC_LIBOBJ in 2.59

[Anton Ertl]

The Gforth-0.6.2 configure.in contains the line:

AC_CHECK_FUNC(_sync_cache_range,true,AC_LIBOBJ(../arch/power/_sync_cache_range))

(simplified configure.in below).

Autoconf-2.59 translates this into

... [main part of AC_CHECK_FUNC] ...
|if test $ac_cv_func__sync_cache_range = yes; then
|  true
|else
|  case $LIBOBJS in
|    "../arch/power/_sync_cache_range.$ac_objext"   | \
|  *" ../arch/power/_sync_cache_range.$ac_objext"   | \
|    "../arch/power/_sync_cache_range.$ac_objext "* | \
|  *" ../arch/power/_sync_cache_range.$ac_objext "*
|fi
| ;;
|  *) LIBOBJS="$LIBOBJS ../arch/power/_sync_cache_range.$ac_objext" ;;
|esac
|)

And bash then chokes on the improperly nested "fi".

In autoconf-2.57 the output was better:

... [main part of AC_CHECK_FUNC] ...
|if test $ac_cv_func__sync_cache_range = yes; then
|  true
|else
|  LIBOBJS="$LIBOBJS ../arch/power/_sync_cache_range.$ac_objext"
|fi

- anton

Here's the simplified configure.in:

AC_INIT([gforth],[0.6.2],[https://savannah.gnu.org/bugs/?func=addbug&group=gforth])
AC_PREREQ(2.54)
#snapshots have numbers major.minor.release-YYYYMMDD
#note that lexicographic ordering must be heeded.
#I.e., 0.4.1-YYYYMMDD must not exist before 0.4.1!
UPDATED="August 25, 2003"
AC_SUBST(UPDATED)
AC_CONFIG_HEADERS(engine/config.h)

AC_CHECK_FUNC(_sync_cache_range,true,AC_LIBOBJ(../arch/power/_sync_cache_range))

AC_SUBST(machine)
AC_CONFIG_FILES([
Makefile
Makedist
gforthmi
vmgen
machpc.fs
engine/Makefile
doc/version.texi ])
AC_CONFIG_COMMANDS([stamp-h],[[echo timestamp > stamp-h
chmod +x gforthmi
chmod +x vmgen
test -d kernel||mkdir kernel]],[[]])
AC_OUTPUT