On Tue, 12 Oct 2004, Hans Zaunere wrote: > > > > The patch shown is what SuSE did for their RPM distribution of PHP. > > > > > > One solution may be with the --with-<module>= directive is to assume > that > > > dir may be an absolute path as well. > > > > > > --with-domxml=/usr/lib64 > > > > No, this is too different from what PHP always has been doing... thus > a > > bad idea. > > Out of curiosity, what has PHP been doing? I always see people specify > a full directory, which typically works.
That's a co-incidence then, as this: --with-domxml=/usr/lib is NOT working as you might think. You always need to do: --with-domxml=/usr as the php checks add /lib for you. > As I mentioned in my original post, --with-module and > --with-module-dir seem to have some inconsistencies themselves as > well. What is the behavior? Where are the inconsistencies, can you point those out? > Going back to 64bit platforms, this is going to be a problem moving > forward. AMD64 is all over the place, and thus having lib and lib64 > directories. While a SuSE patch works for SuSE, what about other AMD64 > distros? What happens on FreeBSD? Can PHP's ./configure be fixed to be > flexible, as a ./configure script should be, or will platform specific > hacks need to be made (which seems counter-intuitive, since that's what > ./configure is for). PHP's ./configure needs to be fixed of course, though for now the suggested patches are a bit suboptimal iirc. I would like to give it a shot, but I'll need to have access to a linux running on 64bit first :) Derick -- Derick Rethans http://derickrethans.nl | http://ez.no | http://xdebug.org -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
