trawick 01/05/09 10:10:33
Modified: . configure.in
Log:
AC_PROG_LIBTOOL can't be invoked more than once in a configure.in
without causing weird side-effects, so split up a case statement
into two case statements each with a singular purpose.
This gets rid of this failure during apache configuration:
------------------/home/regress/regress/logs/configure.stderr.diff---------------
2a3,5
> ltconfig: you must specify a host type if you use `--no-verify'
> Try `ltconfig --help' for more information.
> configure: error: libtool configure failed
Revision Changes Path
1.22 +13 -6 apr-util/configure.in
Index: configure.in
===================================================================
RCS file: /home/cvs/apr-util/configure.in,v
retrieving revision 1.21
retrieving revision 1.22
diff -u -r1.21 -r1.22
--- configure.in 2001/05/09 12:36:14 1.21
+++ configure.in 2001/05/09 17:10:28 1.22
@@ -43,17 +43,24 @@
AC_CANONICAL_SYSTEM
LDFLAGS=""
case "$host_alias" in
-*os2*)
- # Use a custom-made libtool replacement
- echo "using aplibtool"
- LIBTOOL="$APR_SOURCE_DIR/build/aplibtool"
- ;;
*beos*)
# Horrible Hack !!!
# if we're building a shared lib then we need to add in the
# apr library to the build...
LDFLAGS="$APR_SOURCE_DIR/libapr.la"
-AC_PROG_LIBTOOL
+ ;;
+*)
+ ;;
+esac
+
+dnl AC_PROG_LIBTOOL can't be invoked more than once, so this
+dnl logic can't be combined with the previous case statement
+
+case "$host_alias" in
+*os2*)
+ # Use a custom-made libtool replacement
+ echo "using aplibtool"
+ LIBTOOL="$APR_SOURCE_DIR/build/aplibtool"
;;
*) dnl libtoolize requires that the following not be indented
AC_PROG_LIBTOOL
