> AOLserver's configure script has an --{enable,disable}-shared
> arg which as far as I can tell is pointless. AOLserver
> builds shared or static based on how Tcl was built and
> REFUSES to build unless it matches.
>
> In other words: if Tcl is built shared, AOLserver must also
> be. If Tcl is built static, AOLserver must also be.
>
> So, what's the point of presenting the option? Is it (or
> rather, should it be) possible to build a statically linked
> AOLserver against a shared Tcl or vice versa?
On Linux I build all test images of the Tcl core with
--disable-shared due to the broken behavior of LD_LIBRARY_PATH
on linux. This is just a convenience to ensure that I can have
a gazillion different core builds all dependably different.
That said, for extensions in general, there is no reason that
you could use a --enable-shared extension on top of a
non-shared core build. Thus, I wouldn't force --disable-shared
just because that's what the core did.
Jeff Hobbs, The Tcl Guy
http://www.ActiveState.com/, a division of Sophos
--
AOLserver - http://www.aolserver.com/
To Remove yourself from this list, simply send an email to <[EMAIL PROTECTED]> with the
body of "SIGNOFF AOLSERVER" in the email message. You can leave the Subject: field of
your email blank.
