RE: [PHP-DEV] ./configure, PHP, SuSE and the AMD64
| From: | Hans Zaunere | Date: | Wed, 13 Oct 2004 01:25:07 +0000 |
| Subject: | RE: [PHP-DEV] ./configure, PHP, SuSE and the AMD64 | ||
| Groups: | php.internals | ||
| Request: | Send a blank email to internals+get-13308@lists.php.net to get a copy of this message | ||
> > 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. 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?
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).
H