> > 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

-- 
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php

Reply via email to