"Brian Havard" <[EMAIL PROTECTED]> writes:
> On 29 Mar 2001 11:07:31 -0500, Jeff Trawick wrote:
>
> >It seemed cleaner to me to provide an empty AC_LIBTOOL_WIN32_DLL macro
> >than to change the expat build.
>
> Err, actually it's just moved, not removed, into the "everything but OS/2"
> section (see below). It could probably have stayed where it was come to
> think of it. If it doesn't hurt on unix it probably won't hurt OS/2 either.
> I've no idea what it does though.
I didn't say you removed it. I'm saying that the change and
OS/2-specific path wasn't needed.
My point is that you can (and IMHO should) minimize special-case logic
in the apache/apr/expat/whatever build to deal with your libtool.
What happens when your libtool is taught to handle another system?
These same sections of build code have to be updated again.
FYI... AC_LIBTOOL_WIN32_DLL certainly doesn't hurt on Unix. I have
no idea what it does either, but an empty macro works fine for me on
OS/390.
--
Jeff Trawick | [EMAIL PROTECTED] | PGP public key at web site:
http://www.geocities.com/SiliconValley/Park/9289/
Born in Roswell... married an alien...
