RE: ./configure, PHP, SuSE and the AMD64

php.internals

Hans Zaunere

21 years ago
> > 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

Derick Rethans

21 years ago
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

Sascha Schumann

21 years ago
> 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
That is hardly a new issue. Irix and other systems have had different lib directories for many years. The users of those systems always coped with the directory layouts the system providers imposed upon them. I am sure the same will work for users of the AMD64 platform.
> 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
FreeBSD amd64 installs its libraries into /usr/lib, as any sane OS does. - Sascha

Joerg Behrens

21 years ago
> > 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 > > That is hardly a new issue. Irix and other systems have had > different lib directories for many years. The users of those > systems always coped with the directory layouts the system > providers imposed upon them. I am sure the same will work > for users of the AMD64 platform.
There is a difference between IRIX and the others. IRIX supports up to 3 ABIs named o32, n32 and 64 at once. Befor someone starts asking.. n32 is the new 32bit ABI which is now used since serveral years. The directory named usr/lib for o32, usr/lib32 for n32 and at least usr/lib64. Official freeware software pakages for IRIX from their freeware.sgi.com page have all modification to match to this layout. For php they used a patched configure with a var called $ABILIB which is similar to the suse patch or so Take a look to http://freeware.sgi.com/source/php/patches
> > 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 > > FreeBSD amd64 installs its libraries into /usr/lib, as any > sane OS does.
Our AMD64 boxes which are runing a 64bit gentoo-linux have a usr/lib64 .... but the dudes have also a /usr/lib which is a symlink to the lib64 directory. I cant believe that they have made any big changes to all of the configures. How does it looks to other OSs like Tru64 and Solaris? regards Joerg

Joe Orton

21 years ago
On Wed, Oct 13, 2004 at 09:55:15AM +0200, Sascha Schumann wrote:
> >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 > > That is hardly a new issue. Irix and other systems have had > different lib directories for many years. The users of those > systems always coped with the directory layouts the system > providers imposed upon them. I am sure the same will work > for users of the AMD64 platform.
IRIX and other systems don't ship with copies of MySQL, Postgres, cURL, Berkeley DB libraries, blah blah blah, which it's useful to be able to use from PHP.
> >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 > > FreeBSD amd64 installs its libraries into /usr/lib, as any > sane OS does.
So other than vague slurs on OS sanity, are there objections to committing my --with-libdir patch to HEAD? http://news.php.net/php.internals/13012 joe

Sascha Schumann

21 years ago
On Wed, 13 Oct 2004, Joe Orton wrote:
> On Wed, Oct 13, 2004 at 09:55:15AM +0200, Sascha Schumann wrote: >>> 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 >> >> That is hardly a new issue. Irix and other systems have had >> different lib directories for many years. The users of those >> systems always coped with the directory layouts the system >> providers imposed upon them. I am sure the same will work >> for users of the AMD64 platform. > > IRIX and other systems don't ship with copies of MySQL, Postgres, cURL,
Not true. Refer to Joerg's post for counterexamples.
> Berkeley DB libraries, blah blah blah, which it's useful to be able to > use from PHP. > >>> 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 >> >> FreeBSD amd64 installs its libraries into /usr/lib, as any >> sane OS does. > > So other than vague slurs on OS sanity, are there objections to > committing my --with-libdir patch to HEAD?
I will look at it later. - Sascha

Joe Orton

21 years ago
On Wed, Oct 13, 2004 at 05:12:22PM +0200, Sascha Schumann wrote:
> On Wed, 13 Oct 2004, Joe Orton wrote: > >So other than vague slurs on OS sanity, are there objections to > >committing my --with-libdir patch to HEAD? > > I will look at it later.
Have you had a chance to look at it, Sascha? joe

Derick Rethans

21 years ago
On Wed, 13 Oct 2004, Joe Orton wrote:
> > FreeBSD amd64 installs its libraries into /usr/lib, as any > > sane OS does. > > So other than vague slurs on OS sanity,
Hey, even Debian sid does it ;-)
> are there objections to > committing my --with-libdir patch to HEAD? > > http://news.php.net/php.internals/13012
No objections from me, though this will not fix extensions in PECL or other third party exts. Derick
-- Derick Rethans http://derickrethans.nl | http://ez.no | http://xdebug.org