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

On Sat, 25 Sep 2004, James Devenish wrote: > In message <41EE526EC2D3C74286415780D3BA9F87046F7AFC@ehost011-1.exch011.intermedia.net> > on Fri, Sep 24, 2004 at 07:21:45PM -0700, Hans Zaunere wrote: > > However, there is one issue I'm pretty unclear on - and, unfortunately > > it might relate to some of the other issues, which makes matters more > > confusion. > [...] > > -- In general, I've found that PHP's ./configure tends to assume things > > are in /usr/lib. However, on this and other 64bit x86 platforms, what > > we want is typically in /usr/lib64. A prime example of this is libjpeg. > [...] > > configure: error: libjpeg.(a|so) not found. > [...] > > The solution: symlink libjpeg.so from /usr/lib64 into /usr/lib - but is > > this right? I've tried numerous flags to configure, but nothing worked. > > When examining config.log in this case, I see "gcc -o conftest > > -L/usr/lib64...." which looks to be on the right track, yet ./configure > > is still breaking. > > Yes, the PHP4 ./configure internals have been broken in this way for a > number of years and bug reports have been filed accordingly. As you have > noted, the compiler has no difficulty finding the libs but the configure > script itself fails while performing its own (spurious) path search. > This is an artificial failure and cannot be corrected with command-line > options in the version you are using (4.3.8, by the looks of it). Can't you just do: LDFLAGS=-L/usr/lib64 ./configure ... CPPFLAGS for compile-time stuff -Rasmus