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 |
SystemsThe system makes have taken different approaches on the problem of supporting largefile systems. One approach is simply changing the old off_t from 32bit into 64bit and to recompile all the software, in other words, to start an incompatible system. The other approach is trying to support both old software with 32bit-off_t and newer software with 64bit-off_t in the very same system. However, we see problems when binaries, libraries and plugins are mixed up with different off_t models. It should actually be the task system makers to ensure that no invalid mixture of 32bit and 64bit off_t-size comes into existance, however many are not aware of it - and in the opensource world it isn't easy either. It may however be helped with an automatic tool that checks for invalid mixes - shown with the testscript to be found on this site. | ||