Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:14057
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Date: Mon, 13 Dec 2004 10:34:03 +0000
To: internals@lists.php.net
Message-ID: <20041213103403.GA28986@redhat.com>
Mail-Followup-To: internals@lists.php.net
References: <41EE526EC2D3C74286415780D3BA9F8706A1DFB7@ehost011-1.exch011.intermedia.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
In-Reply-To: <41EE526EC2D3C74286415780D3BA9F8706A1DFB7@ehost011-1.exch011.intermedia.net>
User-Agent: Mutt/1.4.1i
Subject: Re: [PHP-DEV] ./configure, PHP, SuSE and the AMD64
From: jorton@redhat.com (Joe Orton)

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