Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:13308
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Tue, 12 Oct 2004 18:25:07 -0700
Message-ID: <41EE526EC2D3C74286415780D3BA9F8704E58AAE@ehost011-1.exch011.intermedia.net>
Thread-Topic: [PHP-DEV] ./configure, PHP, SuSE and the AMD64
thread-index: AcSkwRoCJPkmhWtwTk6eRqhufr/4fQMAY8+w
To: "Derick Rethans" <derick@php.net>,
	"Robert Silva" <junkmail@bobsilva.com>
Cc: <internals@lists.php.net>
Subject: RE: [PHP-DEV] ./configure, PHP, SuSE and the AMD64
From: hans@nyphp.com ("Hans Zaunere")


> > The patch shown is what SuSE did for their RPM distribution of PHP.
> >
> > One solution may be with the --with-<module>=3D directive is to =
assume
that
> > dir may be an absolute path as well.
> >
> > --with-domxml=3D/usr/lib64
>=20
> 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