[GRASS-dev] Re: [GRASS GIS] #1125: wingrass7 - ctypes - compiling
error
GRASS GIS
trac at osgeo.org
Tue Aug 10 12:45:35 EDT 2010
#1125: wingrass7 - ctypes - compiling error
------------------------------+---------------------------------------------
Reporter: hellik | Owner: grass-dev@…
Type: defect | Status: new
Priority: blocker | Milestone: 6.5.0
Component: Compiling | Version: svn-trunk
Keywords: wingrass, ctypes | Platform: MSWindows Vista
Cpu: x86-32 |
------------------------------+---------------------------------------------
Comment(by glynn):
Replying to [comment:13 martinl]:
> > BTW, is there a way how to disable LFS? - {{{--disable-largefile}}}
doesn't seems to work.
>
> using {{{--disable-largefile}}} I am getting on *MS Windows*
>
{{{
checking for _LARGEFILE_SOURCE value needed for large files... no
checking for fseeko... no
checking if system supports Large Files at all... yes
}}}
>
> and
>
{{{
USE_LARGEFILES = 1
}}}
> Not sure why it's not working on MS Windows.
The "meta" answer is: because the code was lifted wholesale from cdrtools
without any attempt at understanding it.
The Windows check for "if system supports Large Files at all" tests that
off64_t can represent 2^63-1, and that fseeko64 and ftello64 exist. This
check will always pass.
The Linux check tests that off_t can represent 2^63-1 and that fseeko and
ftello exist. These checks will only pass if the relevant feature macros
have been defined.
Essentially, Linux has macros to enable the LFS features and to make LFS
the default. Windows has neither; the LFS features are always available
but must be used explicitly.
The USE_LARGEFILES setting is based upon whether the LFS check passes, not
whether you requested LFS. On Linux, they're effectively the same thing,
as the LFS check will only pass if you ask for it; on Windows, it always
passes.
--
Ticket URL: <http://trac.osgeo.org/grass/ticket/1125#comment:14>
GRASS GIS <http://grass.osgeo.org>
More information about the grass-dev
mailing list