Re: ./configure, PHP, SuSE and the AMD64

In message <Pine.LNX.4.58.0409251306510.13895@t42p.lerdorf.com> on Sat, Sep 25, 2004 at 01:12:15PM -0700, Rasmus Lerdorf wrote: > Can't you just do: > > LDFLAGS=-L/usr/lib64 ./configure ... > > CPPFLAGS for compile-time stuff The compiler and linker have no problem. The problem is that the ./configure script does its *own* library path search, independently of the compiler and linker (why?) and it uses its own hard-coded paths. The compiler and linker have *no* problem finding the libraries, yet the ./configure attempts to pre-empt them and fails. Failure of ./configure does *not* indicate any compilation or linking problem in these cases. The failed tests have no bearing on the success or failure of PHP -- ./configure doesn't even set any flags as a consequence of these tests. The practice has been on the increase in the ./configure system and appears to be used in both PHP 4.3.9 and 5.0.1. For example: % cd php-4.3.9; grep 'test -f.*/lib/lib' ./configure | wc -l 42 % cd ../php-5.0.1; grep 'test -f.*/lib/lib' ./configure | wc -l 36