FS#24720 - GDAL should be built against internal libtiff / libgeotiff

Attached to Project: Community Packages
Opened by Andrew Zaborowski (balrog) - Tuesday, 14 June 2011, 13:21 GMT
Last edited by Jelle van der Waa (jelly) - Tuesday, 19 July 2011, 21:12 GMT
Task Type Feature Request
Category Packages
Status Closed
Assigned To Jaroslav Lichtblau (Dragonlord)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:
GDAL supports large ( > 4GB) tiff files since about 1.6.1, but the GDAL 1.8.0 package in community still exits with error when crossing the 4GB boundary writing a tiff. This is because it builds against external libtiff / libgeotiff instead of using its internal fixed version.

(the error looks like this, repeated many times:
ERROR 1: TIFFAppendToStrip:Maximum TIFF file size exceeded
ERROR 1: WriteEncodedTile/Strip() failed.
)

This can be fixed by replacing the configure line in PKGBUILD with:

./configure --prefix=/usr --with-netcdf --with-libtiff=internal \
--with-sqlite3 --with-jpeg=internal --with-geotiff=internal \
--with-mysql --with-python --without-libtool --with-curl \
--with-hdf5 --with-perl --with-geos --with-png

and the depends line with:

depends=('curl' 'geos' 'giflib' 'hdf5' 'libpng' 'netcdf' 'python2' 'python2-numpy' 'cfitsio' 'sqlite3' 'libmysqlclient' 'postgresql-libs')
This task depends upon

Closed by  Jelle van der Waa (jelly)
Tuesday, 19 July 2011, 21:12 GMT
Reason for closing:  Won't implement
Additional comments about closing:  libtiff should be fixed to handle >4GB files.
Comment by Jelle van der Waa (jelly) - Sunday, 03 July 2011, 09:47 GMT
Actaully this is a bug with libtiff

Loading...