[gdal-dev] Motion: Promote GDAL/OGR 1.7.3RC2 to final release

[Peter Hopfgartner]

Hi Frank,

gdal was configured with:

        --with-geotiff=external   \
        --with-tiff=external      \
        --with-libtiff=external   \

and libtiff is the one that comes with CentOS 5.5:

[rpmbuild at rpm-devel gdalautotest-1.7.0]$ rpm -qa | grep tiff
libgeotiff-1.2.4-3.el5
libtiff-devel-3.8.2-7.el5_5.5
libgeotiff-devel-1.2.4-3.el5
libtiff-3.8.2-7.el5_5.5

Regards,

Peter
 
R3 GIS Srl - GmbH
http://www.r3-gis.com


--------Frank Warmerdam <warmerdam at pobox.com> wrote--------
Subject: Re: [gdal-dev] Motion: Promote GDAL/OGR 1.7.3RC2 to final release
Date: 09.11.2010 16:32

>Peter Hopfgartner wrote:
>> I wrapped a quick rpm package, installed the rpms and tried to run
>autotest. The tests comes to this point:
>> 
>> Running tests from gcore/mask.py
>>   TEST: mask_1 ... success
>>   TEST: mask_2 ... success
>>   TEST: mask_3 ... success
>>   TEST: mask_4 ... success
>>   TEST: mask_5 ... ERROR 1: ZIPDecode:tmp/mask_4.pnm.msk: Decoding
>error at scanline 0, incorrect header check
>> ERROR 1: TIFFReadEncodedTile() failed.
>> 
>> ERROR 1: IReadBlock failed at X offset 0, Y offset 0
>> ERROR 1: GetBlockRef failed at X block offset 0, Y block offset 0
>> Segmentation fault
>> 
>> The platform id CentOS 5.5/x86_64, with some packages from EPEL and
>elgis.
>
>Peter,
>
>What libtiff is this using?  Internal?  External libtiff4?  libtiff3.x?
>
>The test suite pushes many boundary cases that only work with the latest
>libtiff4 code particularly because GDAL tends to be the client that
>pushes the boundaries of libtiff.
>
>Best regards,
>-- 
>---------------------------------------+--------------------------------------
>I set the clouds in motion - turn up   | Frank Warmerdam,
>warmerdam at pobox.com
>light and sound - activate the windows | http://pobox.com/~warmerdam
>and watch the world go round - Rush    | Geospatial Programmer for Rent
>
>