On Wed, 4 Jun 2008, Dan Fandrich wrote:

>> curl_off_t data type would be the same no matter if LFS is enabled or
>> disabled when building the library and would also be the same when building
>> an app that uses the library no matter if LFS is enabled or disabled when
>> building the app. This is the "only" benefit of doing this.
>
> This change will cause a binary compatibility break on any architecture that
> supports 64 bit integers but has a 32 bit off_t. That will need to be
> clearly documented so that packagers will know to handle the situation
> appropriately.

Yeps. What known systems do/did this?

I know Windows is one of these but we have our own ways around that, and I
figure we can find oldish Linux boxes with this problem but our configure
detections should run on those and thus avoid the problem for us there as
well.

-- 
  / daniel.haxx.se