[GRASS-dev] Re: About the vector changes
markus.metz.giswork at googlemail.com
Mon Aug 10 03:23:52 EDT 2009
>> Is it possible that configure sets LFS_FLAGS as a result of the LFS
>> tests which are stolen from cdrtools and in aclocal.m4?
>> It would be easier if configure could check if all we need is
>> _FILE_OFFSET_BITS and not also conditionally _LARGE_FILES,
>> _LARGEFILE_SOURCE, -n32 for LFS to work on 32bit systems.
> Until everything is made LFS-aware, we need the separate macros so
> that modules can use specific features without having to worry about
> libraries which may not be LFS-aware.
> OTOH, we're already in trouble due to the whole of lib/gis using
> _FILE_OFFSET_BITS=64. This means that G_fopen_old() etc will open
> files >2GiB, even though the caller may not be LFS-aware.
> Unfortunately, there isn't an fopen32(). Once you set
> _FILE_OFFSET_BITS=64, there's no way to get at the original 32-bit
> fopen() function for specific cases.
Maybe it is less effort and less complicated to make everything LFS-safe
instead of creating workarounds for modules that are not LFS-safe when
LFS is enabled for lib/gis? One way or the other, I guess these modules
need to be identified and possibly modified.
More information about the grass-dev