[EMAIL PROTECTED] writes:
> Modified: . configure.in
> xml/expat configure.in
> Log:
> Use aplibtool on OS/2.
>
> Index: configure.in
> ===================================================================
> RCS file: /home/cvs/apr-util/configure.in,v
> retrieving revision 1.14
> retrieving revision 1.15
> diff -u -r1.14 -r1.15
> --- configure.in 2001/03/09 14:02:45 1.14
> +++ configure.in 2001/03/29 15:53:24 1.15
> @@ -39,7 +39,18 @@
> dnl prep libtool
> dnl
> echo "performing libtool configuration..."
> -AC_PROG_LIBTOOL
> +
> +AC_CANONICAL_SYSTEM
> +case "$host_alias" in
> +*os2*)
> + # Use a custom made libtool replacement
> + echo "using aplibtool"
> + LIBTOOL="$APR_SOURCE_DIR/build/aplibtool"
> + ;;
> +*)
> + AC_PROG_LIBTOOL
> + ;;
> +esac
Same comment as before... just provide AC_PROG_LIBTOOL which does the
right thing...
> 1.2 +12 -2 apr-util/xml/expat/configure.in
>
> Index: configure.in
> ===================================================================
> RCS file: /home/cvs/apr-util/xml/expat/configure.in,v
> retrieving revision 1.1
> retrieving revision 1.2
> diff -u -r1.1 -r1.2
> --- configure.in 2001/02/28 14:41:25 1.1
> +++ configure.in 2001/03/29 15:53:26 1.2
> @@ -45,8 +45,18 @@
>
> AC_CONFIG_HEADER(config.h)
>
> -AC_LIBTOOL_WIN32_DLL
It seemed cleaner to me to provide an empty AC_LIBTOOL_WIN32_DLL macro
than to change the expat build.
> -AC_PROG_LIBTOOL
> +AC_CANONICAL_SYSTEM
> +case "$host_alias" in
> +*os2*)
> + # Use a custom made libtool replacement
> + echo Using aplibtool
> + LIBTOOL="$srcdir/../../../apr/build/aplibtool"
> + ;;
> +*)
> + AC_LIBTOOL_WIN32_DLL
> + AC_PROG_LIBTOOL
> + ;;
> +esac
as before, do this in AC_PROG_LIBTOOL
--
Jeff Trawick | [EMAIL PROTECTED] | PGP public key at web site:
http://www.geocities.com/SiliconValley/Park/9289/
Born in Roswell... married an alien...
