[
https://issues.apache.org/jira/browse/LUCY-178?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marvin Humphrey updated LUCY-178:
---------------------------------
Attachment: largefile_probing.patch
The attached diff, largefile_probing.patch, provides the following:
* Increased granularity in probing and reporting of large file support -
instead of defining HAS_LARGE_FILE_SUPPORT, Charmonizer will now define
HAS_64BIT_OFFSET_TYPE, HAS_64BIT_LSEEK, etc.
* The TestLargeFiles tests will now be skipped on systems which do not
provide stdio support for large files, rather than failing to build.
* POSIX IO large file support is now verified in TestLargeFiles, though
the tests are disabled unless 1) the system supports large files with
stdio, and 2) the volume that TestLargeFiles is running on supports
sparse files.
A further improvement to TestLargeFiles would be to make testing of POSIX IO
completely independent of stdio. However, the only known compiler/system
affected is Visual Studio 6, and from what I've seen, the tests would
typically not run anyway because of the sparse files requirement. Thus, the
only real benefit would be to enable a manual force of the TestLargeFiles
under Visual Studio 6.
> Discriminate between stdio and POSIX in large file support probing.
> -------------------------------------------------------------------
>
> Key: LUCY-178
> URL: https://issues.apache.org/jira/browse/LUCY-178
> Project: Lucy
> Issue Type: Bug
> Components: Charmonizer
> Affects Versions: 0.1.0 (incubating), 0.2.0 (incubating), 0.2.1
> (incubating)
> Reporter: Marvin Humphrey
> Assignee: Marvin Humphrey
> Priority: Minor
> Fix For: 0.2.2 (incubating)
>
> Attachments: largefile_probing.patch
>
>
> The Lucy core has been updated and now depends on large file support in POSIX
> IO rather than stdio, but Charmonizer has not been fully updated so that Lucy
> will build and test clean on systems which *only* support large files with
> POSIX IO (while stdio is limited to 2 GB files).
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
