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) 2004-04-22 Guido U. Draheim |
converting to largefile
The conversion of existing code to become largefile resistant is not a quick task despite some documents telling you otherwise. If you want to write portable code then you have to get away with different sizes of a seek-pointer plus the shapeshifter problems of systems using 64on32. However, the conversion into the largefile world is not tricky atleast if you know the steps and the dark corners to watch out for. This site will tell you about it, trying to let you turn over into a modern world and rather smoothly. If you find software that is still not largefile resistant then please tell their maintainers and at best point them to this site.
|