Justin, > httpd-2.0 doesn't build with the stock libtool-1.4.2 either. So, > if you're using Apache 2.0, you're going to need a patched libtool > anyway. I'd imagine that binary distributions of httpd-2.0 will > include the patched libtool in its installbuilddir (whomever built > the binary needs a good libtool), so that may be a way to work > around the problem - leverage httpd's libtool on Darwin. > > It's a point of contention that we've been trying to bring to Apple's > attention (Fred and I have been emailing the Core OS team). We're > trying to get them to a) include it in Jaguar and b) submit it > upstream. I'm crossing my fingers, but I'm not really optimistic on > this point that Apple is going to address this. I believe JimJag is > tasked with trying to submit ASF-desired patches to GNU tools > upstream to FSF.
You have in this message illustrated the precise reasons why I want to steer PHP clear of libtool on Darwin and Mac OS X. It is not likely that this issue will be resolved any time soon. Wouldn't it be possible to resolve the .la's and whatnot into normal library dependencies when building the apr-config and apu-config themselves? I can think of a few ways of doing just that. I also think that it would add tremendous value to ap{ru}-config if they enabled projects to link against them *without* libtool. I'm also trying to take the long view here ... It is entirely possible that Apple will ship systems with Apache 2 before the libtool issue is resolved. They might not even include your patched libtool. How should we compile PHP --with-apxs2 in such a scenario? --Marko -- PHP Development Mailing List <http://www.php.net/> To unsubscribe, visit: http://www.php.net/unsub.php