RE: [PHP-DEV] ./configure, PHP, SuSE and the AMD64

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 for i in "" lib; do if test -f $DOMXML_DIR/$i/library.a -o -f $DOMXML_DIR/$i/library.so ... Instead of hardcoding to check a "lib" directory. As you can tell by the size of the patch suse made, there are a lot of areas where its assumed the library is located in a "lib" directory. While standard, I don't think it should be required. Actually, since most distributions have to make patches to work with their directory layout, maybe a more flexible solution is needed overall? Bob Silva -----Original Message----- From: Derick Rethans [mailto:derick@php.net] Sent: Monday, September 27, 2004 1:13 AM To: Robert Silva Cc: internals@lists.php.net Subject: RE: [PHP-DEV] ./configure, PHP, SuSE and the AMD64 On Sat, 25 Sep 2004, Robert Silva wrote: > The root of your problem is that ext/domxml/config.m4 looks for libxml2 > specifically in $DOMXML_DIR/lib > > And if it doesn't find it there, then it defaults to using -lxml instead of > -lxml2. Now where this breaks for you is that libxml doesn't exist, but > libxml2 does. > > If you look at that config.m4 file, you will see tests around line 54 that > are hardcoded to $DOMXML_DIR/lib > > Again, if you look at the Suse php config patch it will show you what you > need to change to get it up and running. > > http://www.bobsilva.com/php-4.3.3-lib64.diff I think this patch is the way to go for this, but it won't address issues when you mix both 64bit and 32bit libraries as this one simply requires you to have everything in either 32bit or 64bit. So we can't really commit it. Derick -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php