apr-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "William A. Rowe Jr." <wr...@rowe-clan.net>
Subject Re: comments on configure.in r835608
Date Fri, 13 Nov 2009 22:28:39 GMT
Jeff Trawick wrote:
> (odd form of comment in 3rd or 4th attempt to get my mail accepted)
> 
> +AC_CONFIG_MACRO_DIR(build)
>  AC_CONFIG_AUX_DIR(build)
>  AC_CONFIG_MACRO_DIR(build)
> 
> why two of these invocations?

Fixed.  I didn't realize Justin had started this, but hadn't yet backported
any of the fixes to 1.x/1.3 branches, so when the patch applied I just
plowed ahead :)

> +    dnl should become LT_INIT(win32-dll)
>  AC_PROG_LIBTOOL
> +AC_LIBTOOL_WIN32_DLL
> 
> I see these warnings with autoconf 2.61:
> 
> configure.in:220: warning: AC_LIBTOOL_SETUP was called before
> AC_LIBTOOL_WIN32_DLL
> build/libtool.m4:1902: AC_LIBTOOL_WIN32_DLL is expanded from...
> configure.in:220: the top level
> buildconf: creating configure ...
> configure.in:220: warning: AC_LIBTOOL_SETUP was called before
> AC_LIBTOOL_WIN32_DLL
> build/libtool.m4:1902: AC_LIBTOOL_WIN32_DLL is expanded from...
> configure.in:220: the top level

Not seeing this on 2.63 :(

Does reversing the order of AC_LIBTOOL_WIN32_DLL with the line above
fix things on 2.61?

Mime
View raw message