Re: ./configure, PHP, SuSE and the AMD64
| From: | Joe Orton | Date: | Mon, 13 Dec 2004 10:34:03 +0000 |
| Subject: | Re: ./configure, PHP, SuSE and the AMD64 | ||
| References: | 1 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-14057@lists.php.net to get a copy of this message | ||
On Sun, Dec 12, 2004 at 02:56:25PM -0800, Hans Zaunere wrote:
> Some more interesting things that threw me off at first. While 4.3.10
> and 5.0.3 do handle lib64 much better than previous versions, and will
> compile with the basic extensions enabled on a lib64 only system, only
> HEAD really implements --with-libdir. These versions will break when
> more extensions are enabled.
4.3.10 and 5.0.3 don't have any lib64-type fixes in AFAIK - they should
work no better or worse than previous versions: i.e. it should be OK
until you start enabling any of the extensions which require libraries
out of /usr/lib{,64}.
> On HEAD, with-libdir has a significant effect with some of the
> extensions.
>
> However, with HEAD as of two minutes ago, it appears that the GD
> extension isn't fully aware of PHP_LIBDIR. The supporting jpeg, png,
> xpm, etc. libs are found correctly under /usr/lib64, but libgd itself
> isn't.
>
> Looking at ext/gd/config.m4, the trouble might be around the for loop on
> line 366 (there's no hint of PHP_LIBDIR). This results in the
> ./configure time error of:
>
> configure: error: Unable to find libgd.(a|so) anywhere under /usr
OK, I've just fixed that. Thanks for testing this stuff out!
Regards,
joe