Greetings, after removing expat from srclib, I'd seen the following problems with the current implementation of --enable-static-build :
1) needed for bootstrap, otherwise the package generated will have an empty srclib (this is most likely a bug and not documented in README.svnusers) 2) makes no sense for expat once it has been removed from srclib, because there is no way to force libtool into using a static library if it is part of an installed library and has also a dynamic counterpart (at least in a portable way) this means IMHO that supporting static builds without srclib won't be possible (specially considering that apr was also scheduled to be removed) and that there only 2 options going forward : 1) drop support for static builds and therefore all of srclib (including confuse) 2) update srclib and keep it in tree for static builds I am guessing the first option will be preferred (as it requires less work and is coherent with pushing the modular approach that is core for 3.1.0) but of course this could prevent some people to migrate to 3.1 because of lack of packaged dependencies on their distributions (cygwin probably being the most notable case) and therefore in the long run (until that problem is fixed) of a little more flexibility into backported patches for the 3.0 branch. any comments? Carlo ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Ganglia-developers mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/ganglia-developers
