Bug #11840 Updated: Can't find libjpeg after upgrade to 4.0.6

ID: 11840 Updated by: sniper Reported By: pete@byways.org Old Status: Feedback Status: Closed Bug Type: Compile Failure Operating System: Linux 2.4/RedHat 7.1 PHP Version: 4.0.6 New Comment: No feedback. And most likely user error. --Jani Previous Comments: ------------------------------------------------------------------------ [2001-08-03 19:50:30] sniper@php.net How exactly did you configure PDFLIB ?? If you didn't configure it with jpeg support, of course you won't need it for PHP.. --Jani ------------------------------------------------------------------------ [2001-07-05 17:49:50] rjs@php.net PDFlib V4.x has support for jpeg, tiff and zlib build in. So these configure options would be obsolte if support to build PHP with PDFlib V3.x would be dropped. This would simplify the configuration of the PDFlib binding a lot. One possible solution would be to have to configure options: --with-pdflib3 for the old PDFlib version and --with-pdflib for V4.x ------------------------------------------------------------------------ [2001-07-02 13:48:09] pete@byways.org Configure will complete without errors if I leave out --with-jpeg-dir. Of course, PDFlib probably won't let me use JPEG files now, but that's not a problem for me. ------------------------------------------------------------------------ [2001-07-02 13:28:38] derick@php.net I've exactly th esame config here, and I got no problems. Can you try not to use the --with-jpeg-dir (as I didn't use that in my configure line). Derick ------------------------------------------------------------------------ [2001-07-02 13:08:18] pete@byways.org [pete@xx lib]$ nm libjpeg.so | grep jpeg_read_header 0000c2f0 T jpeg_read_header [pete@xx lib]$ rpm -q libjpeg libjpeg-6b-15 [pete@xx lib]$ ls | grep jpeg libimlib-jpeg.a libimlib-jpeg.so libjpeg.a libjpeg.la libjpeg.so libjpeg.so.62 libjpeg.so.62.0.0 ------------------------------------------------------------------------ The remainder of the comments for this report are too long. To view the rest of the comments, please view the bug report online at http://bugs.php.net/?id=11840 Edit this bug report at http://bugs.php.net/?id=11840&edit=1