Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:13323
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Date: Wed, 13 Oct 2004 15:25:59 +0100
To: internals@lists.php.net
Message-ID: <20041013142559.GA1701@redhat.com>
Mail-Followup-To: internals@lists.php.net
References: <41EE526EC2D3C74286415780D3BA9F8704E58AAE@ehost011-1.exch011.intermedia.net> <Pine.LNX.4.61.0410130951380.12292@chatserv>
Mime-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
In-Reply-To: <Pine.LNX.4.61.0410130951380.12292@chatserv>
User-Agent: Mutt/1.4.1i
Subject: Re: [PHP-DEV] ./configure, PHP, SuSE and the AMD64
From: jorton@redhat.com (Joe Orton)

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