diff options
| author | Bill Wendling <wendling@ncsa.uiuc.edu> | 2001-05-08 00:04:50 (GMT) |
|---|---|---|
| committer | Bill Wendling <wendling@ncsa.uiuc.edu> | 2001-05-08 00:04:50 (GMT) |
| commit | 4a72a04048b88c49a4bea654b5256aa6eaac2663 (patch) | |
| tree | 55e5baeecb4617f00c0cbf54129c9ad9b06956d3 /COPYING | |
| parent | ee5b6b12af650a74b559575cda88f7e6480b8c98 (diff) | |
| download | hdf5-4a72a04048b88c49a4bea654b5256aa6eaac2663.zip hdf5-4a72a04048b88c49a4bea654b5256aa6eaac2663.tar.gz hdf5-4a72a04048b88c49a4bea654b5256aa6eaac2663.tar.bz2 | |
[svn-r3891] Purpose:
Bug Fix
Description:
Linux does actually support 64 bit files (those greater than 2GB),
you just have to defined a bunch of, seemingly meaningless, macros in
order to coax glibc to work with you. 64 bit file support is in the
2.3 and above kernels by default. For lower, well...upgrade or
something. The one weird thing, the "-mdouble-align" flag was causing
hdf5 to barf when the large file support was compiled in there. It
has something to do with the structures and their alignment or
something. Very weird.
Solution:
Added a test to see if we're on a Linux boxen with kernel >2.3 and if
so then specify the flags for LFS support. Removed the -mdouble-align
flag if we do use LFS support since it causes damage.
Platforms tested:
Linux (Dangermouse)
Diffstat (limited to 'COPYING')
0 files changed, 0 insertions, 0 deletions