Re: [PATCH] fixes for /usr/lib64 systems
| From: | James Devenish | Date: | Thu, 06 Mar 2003 11:27:05 +0000 |
| Subject: | Re: [PATCH] fixes for /usr/lib64 systems | ||
| References: | 1 | Groups: | php.dev |
| Request: | Send a blank email to php-dev+get-94832@lists.php.net to get a copy of this message | ||
In message <20030306102514.GA31291@redhat.com>
on Thu, Mar 06, 2003 at 10:25:14AM +0000, Joe Orton wrote:
> Hi, I've got a bunch of fixes for systems which have system libraries in
> /usr/lib64 rather than /usr/lib - these are needed for some upcoming
> 64-bit Linux ports. These fixes are based on patches from SuSE
> developers <uli@suse.de> <ro@suse.de>.
>
> Should I submit changes to ext/*/config.m4 in bulk or individually?
>
> Here's the first fix to prevent adding /usr/lib64 to LDFLAGS:
[...]
> + -L/usr/lib|-L/usr/lib/|-L/usr/lib64|-L/usr/lib64/) ;;
Of all the problems I've had using PHP on 64-bit platforms (e.g. bug
#21973, which refers mainly to lib directory naming under commercial
64-bit environments), this was not one of them -- yay.
So I am curious:
- What is the purpose of having the mechanism to remove or not remove
/usr/lib (and why not do the same for /lib and other vendor
directories)?
- Why do 64-bit Linux operating systems need the special hard-coded
treatment?
- Will the same be done for other operating systems?