From mboxrd@z Thu Jan 1 00:00:00 1970 From: Keir Fraser Subject: Re: build fixes Date: Tue, 12 Jan 2010 18:44:04 +0000 Message-ID: References: <4B4CB49A.90802@cs.ubc.ca> Mime-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <4B4CB49A.90802@cs.ubc.ca> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Patrick Colp Cc: Christoph Egger , "xen-devel@lists.xensource.com" , Ian Jackson List-Id: xen-devel@lists.xenproject.org On 12/01/2010 17:42, "Patrick Colp" wrote: >> We build everything under tools/ with LFS support enabled, so off_t is 64 >> bits even in 32-bit environments. FYI The bits to enable LFS support are in >> tools/Rules.mk. > > According to the lseek64 man page, for 32-bit architectures to have 64-bit > off_t, you need: > > #define _FILE_OFFSET_BITS 64 > > Which, as far as I know, isn't set. LFS just makes lseek64 available > (without it, the function doesn't exist). I don't think so. 'getconf LFS_CFLAGS' returns -D_FILE_OFFSET_BITS=64 on a 32-bit host. It's LFS64_CFLAGS that gets you the explicit model for large-file access (i.e., where you have to explicitly use the 64-bit off_t and lseek variants). -- Keir