Configure Error When Checking For libjpeg On x86_64 Platforms

[email protected] (Robert L Cochran)
Newsgroups php.install
Message-ID <[email protected]>
Hello,

I'm attempting to compile php-5.0.2 on an AMD Athlon 64 machine running 
the x86_64 arch of Fedora Core 3 Linux.

I believe the configure script is checking the wrong libraries when it 
attempts to find shared or static libraries for libjpeg. This results in 
a configure failure, telling me it cannot find the libraries even though 
both are installed.

Even if you use the option:

--with-jpeg-dir=/usr/lib64 \

configure will not look in this library because it is hardcoded to look 
in $i/lib/...

I've resolved this by removing the hardcoding so that configure looks 
for $i/libjpeg...

Here is a diff of configure showing precisely what I've changed:

[rlc@bobcp4 php-5.0.2]$ diff configure configure.original.version
21205c21205
<       if test -f "$i/libjpeg.$SHLIB_SUFFIX_NAME" -o -f "$i/libjpeg.a"; 
then
---
 >       if test -f "$i/lib/libjpeg.$SHLIB_SUFFIX_NAME" -o -f 
"$i/lib/libjpeg.a"; then
30282c30282
<       test -f $i/libjpeg.$SHLIB_SUFFIX_NAME -o -f $i/libjpeg.a && 
GD_JPEG_DIR=$i && break
---
 >       test -f $i/lib/libjpeg.$SHLIB_SUFFIX_NAME -o -f 
$i/lib/libjpeg.a && GD_JPEG_DIR=$i && break
32072c32072
<       test -f $i/libjpeg.$SHLIB_SUFFIX_NAME -o -f $i/libjpeg.a && 
GD_JPEG_DIR=$i && break
---
 >       test -f $i/lib/libjpeg.$SHLIB_SUFFIX_NAME -o -f 
$i/lib/libjpeg.a && GD_JPEG_DIR=$i && break

On the  < is the correction I've worked.
On the > is the original version of configure as downloaded.

This fix seems to work, however I have hit a similar issue with libpng 
that I'll address tomorrow.

Would running autoconf correct this? Is autoconf smart enough to look at 
my platform and adjust library checking accordingly?

Does anyone else have this problem, and is there a better workaround?

Thanks

Bob Cochran
Greenbelt, Maryland, USA
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.