1 2bzip2-1.0.3 should compile without problems on the vast majority of 3platforms. Using the supplied Makefile, I've built and tested it 4myself for x86-linux and x86_64-linux. With makefile.msc, Visual C++ 56.0 and nmake, you can build a native Win32 version too. Large file 6support seems to work correctly on at least alpha-tru64unix and 7x86-cygwin32 (on Windows 2000). 8 9When I say "large file" I mean a file of size 2,147,483,648 (2^31) 10bytes or above. Many older OSs can't handle files above this size, 11but many newer ones can. Large files are pretty huge -- most files 12you'll encounter are not Large Files. 13 14Earlier versions of bzip2 (0.1, 0.9.0, 0.9.5) compiled on a wide 15variety of platforms without difficulty, and I hope this version will 16continue in that tradition. However, in order to support large files, 17I've had to include the define -D_FILE_OFFSET_BITS=64 in the Makefile. 18This can cause problems. 19 20The technique of adding -D_FILE_OFFSET_BITS=64 to get large file 21support is, as far as I know, the Recommended Way to get correct large 22file support. For more details, see the Large File Support 23Specification, published by the Large File Summit, at 24 http://ftp.sas.com/standards/large.file 25 26As a general comment, if you get compilation errors which you think 27are related to large file support, try removing the above define from 28the Makefile, ie, delete the line 29 BIGFILES=-D_FILE_OFFSET_BITS=64 30from the Makefile, and do 'make clean ; make'. This will give you a 31version of bzip2 without large file support, which, for most 32applications, is probably not a problem. 33 34Alternatively, try some of the platform-specific hints listed below. 35 36You can use the spewG.c program to generate huge files to test bzip2's 37large file support, if you are feeling paranoid. Be aware though that 38any compilation problems which affect bzip2 will also affect spewG.c, 39alas. 40