After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 335764 - configure can't find libtiff under Fedora Core 5
configure can't find libtiff under Fedora Core 5
Status: RESOLVED FIXED
Product: GIMP
Classification: Other
Component: General
2.3.x
Other All
: Normal normal
: 2.4
Assigned To: GIMP Bugs
GIMP Bugs
Depends on:
Blocks:
 
 
Reported: 2006-03-23 23:06 UTC by Colin Brace
Modified: 2008-01-15 14:06 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Colin Brace 2006-03-23 23:06:18 UTC 
Please describe the problem:
When compiling from source, configure can't find libtiff, even though it is
installed (in this case, as part of the base OS in Fedora Core 5). 
If you supply the "--without-libtiff" parameter, configure completes and
indictates tiff support will be included, but in the resulting build this is not
the case. 

Steps to reproduce:
1. ensure libtiff is present
2. run ./configure
3. run ./configure --without-libtiff
4. 


Actual results:
configure fails without the --without-libtiff parameter
configure completes with --without-libtiff parameter, indicates tiff support
will be included, but tiff support is not in fact included

Expected results:
libtiff to be found, tiff support to be included

Does this happen every time?
yes

Other information:
Comment 1 Carol 2006-03-23 23:47:32 UTC 
I am going to passte the original problem from your email to the gimp-user lisst:
I installed Fedora Core 5 yesterday and am recompiling 2.3.7. Alas,
configure returns an error message:
  [...]
  checking for TIFFReadScanline in -ltiff... no
  checking for TIFFWriteScanline in -ltiff... no
  checking for TIFFFlushData in -ltiff34... no
  configure: error:
  *** Checks for TIFF libary failed. You can build without it by passing
  *** --without-libtiff to configure but you won't be able to use TIFFs then.

However, libtiff is most definitely installed:
  $ rpm -q libtiff
  libtiff-3.7.4-3.2.1

Any ideas why configure isn't seeing it?

This is the problem mentioned when configuring as in 2.
I am wondering if you have libtiff-dev available for configure to find.


The problem with configuration mentioned in 3. is probably a bug in the ./configure script and should be looked at.
Comment 2 Sven Neumann 2006-03-24 08:14:08 UTC 
I have fixed the problem that the summary is wrong if libtiff has been explicitely disabled. The user should read INSTALL and check the output of "configure --help" to get more information on how to make the configure script detect libtiff.