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 |
making largefile the default
If you just have an application using autoconf then you should simple
go and use the
All other might want to check $ getconf LFS_CFLAGS -D_FILE_OFFSET_BITS=64
When you are writing a library then it might be the best to follow the
style of GTK to just use off_t internally - that will allow you to
compile the library again with If you still have some dependency on off_t in the exported interface of your binary or library then it is a good thing to mark that somewhere. And simply reject when software gets compiled with the wrong model than your library was compiled as: # if _FILE_OFFSET_BITS+0 != 64 && MYLIB_FILE_OFFSET_BITS == 64 # error need to compile as largefile when using MYLIB # endif
See also: widely used
|