Re: ./configure, PHP, SuSE and the AMD64
| From: | Sascha Schumann | Date: | Wed, 13 Oct 2004 15:12:22 +0000 |
| Subject: | Re: ./configure, PHP, SuSE and the AMD64 | ||
| References: | 1 2 3 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-13324@lists.php.net to get a copy of this message | ||
On Wed, 13 Oct 2004, Joe Orton wrote:
On Wed, Oct 13, 2004 at 09:55:15AM +0200, Sascha Schumann wrote:IRIX and other systems don't ship with copies of MySQL, Postgres, cURL,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 lib64That 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.
Not true. Refer to Joerg's post for counterexamples.
Berkeley DB libraries, blah blah blah, which it's useful to be able to use from PHP.So other than vague slurs on OS sanity, are there objections to committing my --with-libdir patch to HEAD?directories. While a SuSE patch works for SuSE, what about other AMD64 distros? What happens on FreeBSD? Can PHP's ./configure be fixed to beFreeBSD amd64 installs its libraries into /usr/lib, as any sane OS does.
I will look at it later.
- Sascha