Build with old TIFF
Posted: 2011-11-14T01:02:34-07:00
I am using RHEL4 that has libtiff-3.6.1-12.el4_8.4 installed. Although this is an old distro and an old version of libtiff, we are obliged to use it.
When configuring the latest version of ImageMagick with the tiff option the test for TIFFIsBigEndian for fails, which is ok for this libtiff version. Alas, failure of this test fails the tiff support for incomplete package.
Looking around in the posts, it was suggested in previous versions to comment out the relevant call in coders/tiff.c.
It seems a reasonable suggestion as this is not a major issue.
The problem I am facing is that I cannot make automatic builds of recent ImageMagick versions with my older env, that do contain tiff support.
I suggest to either make this part of the code depends on the presence of TIFFIsBigEndian and/or add a replacement code that performs this check, and remove the dependency between the existence of it and the completeness of tiff check.
I think this is the a main concept in using configure prior to build, so the most appropriate code is used, while taking the chance that some of the functionality will not work with old dependent packages.
Needless to say, this will resolve the conflict I have...
When configuring the latest version of ImageMagick with the tiff option the test for TIFFIsBigEndian for fails, which is ok for this libtiff version. Alas, failure of this test fails the tiff support for incomplete package.
Looking around in the posts, it was suggested in previous versions to comment out the relevant call in coders/tiff.c.
It seems a reasonable suggestion as this is not a major issue.
The problem I am facing is that I cannot make automatic builds of recent ImageMagick versions with my older env, that do contain tiff support.
I suggest to either make this part of the code depends on the presence of TIFFIsBigEndian and/or add a replacement code that performs this check, and remove the dependency between the existence of it and the completeness of tiff check.
I think this is the a main concept in using configure prior to build, so the most appropriate code is used, while taking the chance that some of the functionality will not work with old dependent packages.
Needless to say, this will resolve the conflict I have...