Return-Path: <tiff-bounces@lists.maptools.org>
Received: from inas024.isp.belgacom.be (localhost [127.0.0.1])
        by inav024.isp.belgacom.be (8.12.11.20060308/8.12.11/Skynet-IN-AV-3.00) with ESMTP id k95DLjZx032552
        for <joris.at.lebbeke@skynet.be>; Thu, 5 Oct 2006 15:21:46 +0200
        (envelope-from <tiff-bounces@lists.maptools.org>)
Received: from inmx019.isp.belgacom.be (inmx019.isp.belgacom.be [195.238.5.138])
        by inas024.isp.belgacom.be (8.12.11.20060308/8.12.11/Skynet-IN-AS-2.03) with ESMTP id k95DLVvH024283
        for <joris.at.lebbeke@skynet.be>; Thu, 5 Oct 2006 15:21:40 +0200
        (envelope-from <tiff-bounces@lists.maptools.org>)
Received: from duke.maptools.org (r153.dmsolutions.ca [209.217.116.153] (may be forged))
        by inmx019.isp.belgacom.be (8.12.11.20060308/8.12.11/Skynet-IN-2.32) with ESMTP id k95DLMJh025891
        for <joris.at.lebbeke@skynet.be>; Thu, 5 Oct 2006 15:21:22 +0200
        (envelope-from <tiff-bounces@lists.maptools.org>)
Received: from duke.maptools.org (duke.maptools.org [127.0.0.1])
	by duke.maptools.org (8.12.11/8.12.10) with ESMTP id k95D2s93019430;
	Thu, 5 Oct 2006 09:03:56 -0400
Received: from py-out-1112.google.com (py-out-1112.google.com [64.233.166.182])
	by duke.maptools.org (8.12.11/8.12.10) with ESMTP id k95D2pqw019427
	for <tiff@lists.maptools.org>; Thu, 5 Oct 2006 09:02:51 -0400
Received: by py-out-1112.google.com with SMTP id z59so617754pyg
	for <tiff@lists.maptools.org>; Thu, 05 Oct 2006 06:02:50 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com;
	h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
	b=NHmQkK5n6Svv7riBFuI+bZ85itx4h7B8QS8bnE7v14qOr7/e8wMxMadJZFn2cicThROOynL2PTjW09Mu9eY3F66OkS4WpYUUzHW5QT4DZK53OK4fNEgCalZUtlqUSJoYdGZT8x+cx/7RyCc9MqiMdpOWDOJ/RxClXzLiNPws6HQ=
Received: by 10.35.97.17 with SMTP id z17mr3485122pyl;
	Thu, 05 Oct 2006 06:02:50 -0700 (PDT)
Received: by 10.35.58.10 with HTTP; Thu, 5 Oct 2006 06:02:49 -0700 (PDT)
Message-ID: <29bcc0df0610050602r262274c8w57a06c0ff6b78d21@mail.gmail.com>
Date: Thu, 5 Oct 2006 17:02:50 +0400
From: "Andrey Kiselev" <andrey.kiselev@gmail.com>
To: tiff@lists.maptools.org
Subject: Re: [Tiff] 64-bit libtiff
In-Reply-To: <452408F3.4060703@conterra.de>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Disposition: inline
References: <452408F3.4060703@conterra.de>
X-MIME-Autoconverted: from quoted-printable to 8bit by duke.maptools.org id
	k95D2pqw019427
X-BeenThere: tiff@lists.maptools.org
X-Mailman-Version: 2.1.4
Precedence: list
List-Id: TIFF and libtiff discussion <tiff.lists.maptools.org>
List-Unsubscribe: <http://lists.maptools.org/mailman/listinfo/tiff>,
	<mailto:tiff-request@lists.maptools.org?subject=unsubscribe>
List-Archive: <http://lists.maptools.org/mailman/private/tiff>
List-Post: <mailto:tiff@lists.maptools.org>
List-Help: <mailto:tiff-request@lists.maptools.org?subject=help>
List-Subscribe: <http://lists.maptools.org/mailman/listinfo/tiff>,
	<mailto:tiff-request@lists.maptools.org?subject=subscribe>
Sender: tiff-bounces@lists.maptools.org
Errors-To: tiff-bounces@lists.maptools.org
Content-Transfer-Encoding: quoted-printable
X-MIME-Autoconverted: from 8bit to quoted-printable by inav024.isp.belgacom.be id k95DLjZx032552
X-UIDL: 000000000023ceae.00001b72
X-MSP-STORE: Thu, 05 Oct 2006 15:21:51 +0200
Status:   

On 10/4/06, Dieter St=FCken <stueken@conterra.de> wrote:
> I tracked down the problem and found the reason was the definition of "=
tsize_t"
> which is still 32 bit, in contrast to size_t or void*, which become 64 =
bit.
> Thus I can't use TIFFmalloc(tsize_t) to handle memory >2G :-( So, even =
if the
> tiff file format itself is limited to 32 bit, there is no reason to lim=
it the
> virtual image size, too. Indeed I simply tried to change "tsize_t" to 6=
4 bit
> and it seems to work without problems so far! I did not test everything=
, but
> the binary tiff file layout seems not being affected by this.

There is existing bug report on this problem:

http://bugzilla.remotesensing.org/show_bug.cgi?id=3D487

> Unfortunately this change makes my own tiff library incompatible to any=
 binary
> distributions, and I have no idea, how to introduce this change without=
 problems.

You can install your new libtiff separately, somewhere in
/usr/local/libtiff-64/ directory, and link your utilities against that
version using rpath (path embedding). Other tools will work with old
library in /usr/lib (or where it is located on your system). The only
thing you should be sure is that tsize_t defined as a signed data type
in your customized build.

Regards,
Andrey

--=20
Andrey V. Kiselev
ICQ# 26871517

_______________________________________________
Tiff mailing list: Tiff@lists.maptools.org
http://lists.maptools.org/mailman/listinfo/tiff
http://www.remotesensing.org/libtiff/
