|
| programming |
index
-summary
-history
-testscript
perl / python
problems
-with callframes
-with structures
-largefile seeks
-broken builds
systems
-freeBSD/darwin
-linux/solaris
-64on32 mix
-distro makers
-win32/other (2)
libraries
-
libc ..(3264)
-
zlib ..(-32-)
-
gtk2 ..(-64-)
converting
-old non-off_t code
-going largefile
-longlong default
-face dualmode
-make twinlibs
-and defend (it)
programming
-largefile default
-off_t in headers
-make export64
-find mismatch
-the autowrappers
-environ changes
-best practice?
old library
-dualmode renames
-the extra function
-largefile64_source
-glibc headers
-libgz example ***
new library
-dual export
-largefiles win32
-compat32 calls
-compat32 library
-long32 dualmode
links
-some quotes
-sitemap / mpl
-large.file Group*
-ac-archive Site*
(C) 2002-01-13
Guido U. Draheim
Programming
Programming Support has a number of hints ..... how to enable the largefile support on systems that do not do so by default ..... a recommended style on the usage of off_t in headers when that seems to be needed ..... how to make up dualmode libraries in 64on32 ..... and finding mismatches in the software setup when everythings done.
And these are preprocessor defines that your system will look for:
- -D_LARGEFILE_SOURCE
- Make extra symbols visible as defined after the large file summit (LFS). These are "off_t", "fseeko", "ftello", the errno "EOVERFLOW" and the open-flag "O_LARGEFILE". The unix98 systems will export these by default.
- -D_LARGEFILE64_SOURCE
- Make the 64bit-modified symbols visible when on a 64on32 system. It allows to use "off64_t" variables with "fseeko64". An "fopen64" will wrap an "fopen" with an added mode-flag "O_LARGEFILE".
- -D_FILE_OFFSET_BITS=64
- On a 64on32 system, make a `typedef off64_t off_t`, and implant redefines so that any source using "fseek" will fact link with an api-call "fseek64". The typeshifting magic.
-D_FILE_OFFSET_BITS=64 -D_LARGEFILE_SOURCE