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 |
Libraries ExamplesThere is very different support of largefile and 64on32 mixtures within the libraries around. Some have started to use off_t in their headers without regard of the fact that it is not a constant type anymore. Others are just not aware of file-descriptor inheritance problems. And a few are trying to be smart - exporting a dual interface for both 32bit-off_t and 64bit-off_t and recognizing the various largefile defines that can be given. The C library and largefile specification are given as an example for a dual interface library, that exports both API calls for 32bit-off_t and 64bit-off_t. You will find that some other libraries in a typical system do so too, the testscript of this site will try to auto-recognize these. The zlib library is discussed for being compiled as 32bit-off_t usually and many many programs to link to it even that those are compiled as 64bit-off_t. And GTK2 library is discussed for showing how to do it right even in the existance of exported API calls that look very much alike the unix system calls, like "lseek()" and such. |