Re: lseek: Value too large for defined data type
- From: David Schwartz <davids@xxxxxxxxxxxxx>
- Date: Sat, 21 Jul 2007 01:06:34 -0700
On Jul 20, 7:49 pm, phil-news-nos...@xxxxxxxx wrote:
One of these days we need to fix all this ... basically migrate to purely
64-bit file offset platforms. It should "just work" without any changes
needed at that point, if they do it right (which is not a given). If old
programs compiled on legacy 32-bit file offset platforms break, so be it.
It is all fixed. It does just work. No changes are needed.
All that is needed is '-D_FILE_OFFSET_BITS=64' and complaining about
that is like arguing that PTHREADS support doesn't "just work" because
you have to specify '-pthread' on the command line when you compile/
link.
DS
.
- Follow-Ups:
- Re: lseek: Value too large for defined data type
- From: phil-news-nospam
- Re: lseek: Value too large for defined data type
- References:
- lseek: Value too large for defined data type
- From: guru
- Re: lseek: Value too large for defined data type
- From: Tim Southerwood
- Re: lseek: Value too large for defined data type
- From: phil-news-nospam
- lseek: Value too large for defined data type
- Prev by Date: Re: lseek: Value too large for defined data type
- Next by Date: Question on getimeofday
- Previous by thread: Re: lseek: Value too large for defined data type
- Next by thread: Re: lseek: Value too large for defined data type
- Index(es):