Author: qboosh Date: Mon Jun 20 22:07:42 2005 GMT
Module: SOURCES Tag: HEAD
---- Log message:
- grrr, don't replace CHANGES and LICENSE with renamed outdated copies
---- Files affected:
SOURCES:
bzip2-libtoolizeautoconf.patch (1.7 -> 1.8)
---- Diffs:
================================================================
Index: SOURCES/bzip2-libtoolizeautoconf.patch
diff -u SOURCES/bzip2-libtoolizeautoconf.patch:1.7
SOURCES/bzip2-libtoolizeautoconf.patch:1.8
--- SOURCES/bzip2-libtoolizeautoconf.patch:1.7 Mon Jun 20 18:27:16 2005
+++ SOURCES/bzip2-libtoolizeautoconf.patch Tue Jun 21 00:07:37 2005
@@ -1,499 +1,3 @@
-diff -Nru bzip2-1.0.2/AUTHORS bzip2-1.0.2.new/AUTHORS
---- bzip2-1.0.2/AUTHORS Thu Jan 1 01:00:00 1970
-+++ bzip2-1.0.2.new/AUTHORS Fri Feb 1 04:18:59 2002
-@@ -0,0 +1 @@
-+Julian Seward <[EMAIL PROTECTED]>
-diff -Nru bzip2-1.0.2/CHANGES bzip2-1.0.2.new/CHANGES
---- bzip2-1.0.2/CHANGES Sat Jan 26 01:02:57 2002
-+++ bzip2-1.0.2.new/CHANGES Thu Jan 1 01:00:00 1970
-@@ -1,253 +0,0 @@
--
--
--0.9.0
--~~~~~
--First version.
--
--
--0.9.0a
--~~~~~~
--Removed 'ranlib' from Makefile, since most modern Unix-es
--don't need it, or even know about it.
--
--
--0.9.0b
--~~~~~~
--Fixed a problem with error reporting in bzip2.c. This does not effect
--the library in any way. Problem is: versions 0.9.0 and 0.9.0a (of the
--program proper) compress and decompress correctly, but give misleading
--error messages (internal panics) when an I/O error occurs, instead of
--reporting the problem correctly. This shouldn't give any data loss
--(as far as I can see), but is confusing.
--
--Made the inline declarations disappear for non-GCC compilers.
--
--
--0.9.0c
--~~~~~~
--Fixed some problems in the library pertaining to some boundary cases.
--This makes the library behave more correctly in those situations. The
--fixes apply only to features (calls and parameters) not used by
--bzip2.c, so the non-fixedness of them in previous versions has no
--effect on reliability of bzip2.c.
--
--In bzlib.c:
-- * made zero-length BZ_FLUSH work correctly in bzCompress().
-- * fixed bzWrite/bzRead to ignore zero-length requests.
-- * fixed bzread to correctly handle read requests after EOF.
-- * wrong parameter order in call to bzDecompressInit in
-- bzBuffToBuffDecompress. Fixed.
--
--In compress.c:
-- * changed setting of nGroups in sendMTFValues() so as to
-- do a bit better on small files. This _does_ effect
-- bzip2.c.
--
--
--0.9.5a
--~~~~~~
--Major change: add a fallback sorting algorithm (blocksort.c)
--to give reasonable behaviour even for very repetitive inputs.
--Nuked --repetitive-best and --repetitive-fast since they are
--no longer useful.
--
--Minor changes: mostly a whole bunch of small changes/
--bugfixes in the driver (bzip2.c). Changes pertaining to the
--user interface are:
--
-- allow decompression of symlink'd files to stdout
-- decompress/test files even without .bz2 extension
-- give more accurate error messages for I/O errors
-- when compressing/decompressing to stdout, don't catch control-C
-- read flags from BZIP2 and BZIP environment variables
-- decline to break hard links to a file unless forced with -f
-- allow -c flag even with no filenames
-- preserve file ownerships as far as possible
-- make -s -1 give the expected block size (100k)
-- add a flag -q --quiet to suppress nonessential warnings
-- stop decoding flags after --, so files beginning in - can be handled
-- resolved inconsistent naming: bzcat or bz2cat ?
-- bzip2 --help now returns 0
--
--Programming-level changes are:
--
-- fixed syntax error in GET_LL4 for Borland C++ 5.02
-- let bzBuffToBuffDecompress return BZ_DATA_ERROR{_MAGIC}
-- fix overshoot of mode-string end in bzopen_or_bzdopen
-- wrapped bzlib.h in #ifdef __cplusplus ... extern "C" { ... }
-- close file handles under all error conditions
-- added minor mods so it compiles with DJGPP out of the box
-- fixed Makefile so it doesn't give problems with BSD make
-- fix uninitialised memory reads in dlltest.c
--
--0.9.5b
--~~~~~~
--Open stdin/stdout in binary mode for DJGPP.
--
--0.9.5c
--~~~~~~
--Changed BZ_N_OVERSHOOT to be ... + 2 instead of ... + 1. The + 1
--version could cause the sorted order to be wrong in some extremely
--obscure cases. Also changed setting of quadrant in blocksort.c.
--
--0.9.5d
--~~~~~~
--The only functional change is to make bzlibVersion() in the library
--return the correct string. This has no effect whatsoever on the
--functioning of the bzip2 program or library. Added a couple of casts
--so the library compiles without warnings at level 3 in MS Visual
--Studio 6.0. Included a Y2K statement in the file Y2K_INFO. All other
--changes are minor documentation changes.
--
--1.0
--~~~
--Several minor bugfixes and enhancements:
--
--* Large file support. The library uses 64-bit counters to
-- count the volume of data passing through it. bzip2.c
-- is now compiled with -D_FILE_OFFSET_BITS=64 to get large
-- file support from the C library. -v correctly prints out
-- file sizes greater than 4 gigabytes. All these changes have
-- been made without assuming a 64-bit platform or a C compiler
-- which supports 64-bit ints, so, except for the C library
-- aspect, they are fully portable.
--
--* Decompression robustness. The library/program should be
-- robust to any corruption of compressed data, detecting and
-- handling _all_ corruption, instead of merely relying on
-- the CRCs. What this means is that the program should
-- never crash, given corrupted data, and the library should
-- always return BZ_DATA_ERROR.
--
--* Fixed an obscure race-condition bug only ever observed on
-- Solaris, in which, if you were very unlucky and issued
-- control-C at exactly the wrong time, both input and output
-- files would be deleted.
--
--* Don't run out of file handles on test/decompression when
-- large numbers of files have invalid magic numbers.
--
--* Avoid library namespace pollution. Prefix all exported
-- symbols with BZ2_.
--
--* Minor sorting enhancements from my DCC2000 paper.
--
--* Advance the version number to 1.0, so as to counteract the
-- (false-in-this-case) impression some people have that programs
-- with version numbers less than 1.0 are in some way, experimental,
-- pre-release versions.
--
--* Create an initial Makefile-libbz2_so to build a shared library.
-- Yes, I know I should really use libtool et al ...
--
--* Make the program exit with 2 instead of 0 when decompression
-- fails due to a bad magic number (ie, an invalid bzip2 header).
-- Also exit with 1 (as the manual claims :-) whenever a diagnostic
-- message would have been printed AND the corresponding operation
-- is aborted, for example
-- bzip2: Output file xx already exists.
-- When a diagnostic message is printed but the operation is not
-- aborted, for example
-- bzip2: Can't guess original name for wurble -- using wurble.out
-- then the exit value 0 is returned, unless some other problem is
-- also detected.
--
-- I think it corresponds more closely to what the manual claims now.
--
--
--1.0.1
--~~~~~
--* Modified dlltest.c so it uses the new BZ2_ naming scheme.
--* Modified makefile-msc to fix minor build probs on Win2k.
--* Updated README.COMPILATION.PROBLEMS.
--
--There are no functionality changes or bug fixes relative to version
--1.0.0. This is just a documentation update + a fix for minor Win32
--build problems. For almost everyone, upgrading from 1.0.0 to 1.0.1 is
--utterly pointless. Don't bother.
--
--
--1.0.2
--~~~~~
--A bug fix release, addressing various minor issues which have appeared
--in the 18 or so months since 1.0.1 was released. Most of the fixes
--are to do with file-handling or documentation bugs. To the best of my
--knowledge, there have been no data-loss-causing bugs reported in the
--compression/decompression engine of 1.0.0 or 1.0.1.
--
--Note that this release does not improve the rather crude build system
--for Unix platforms. The general plan here is to autoconfiscate/
--libtoolise 1.0.2 soon after release, and release the result as 1.1.0
--or perhaps 1.2.0. That, however, is still just a plan at this point.
--
--Here are the changes in 1.0.2. Bug-reporters and/or patch-senders in
--parentheses.
--
--* Fix an infinite segfault loop in 1.0.1 when a directory is
-- encountered in -f (force) mode.
-- (Trond Eivind Glomsrod, Nicholas Nethercote, Volker Schmidt)
--
--* Avoid double fclose() of output file on certain I/O error paths.
-- (Solar Designer)
--
--* Don't fail with internal error 1007 when fed a long stream (> 48MB)
-- of byte 251. Also print useful message suggesting that 1007s may be
-- caused by bad memory.
-- (noticed by Juan Pedro Vallejo, fixed by me)
--
--* Fix uninitialised variable silly bug in demo prog dlltest.c.
-- (Jorj Bauer)
--
--* Remove 512-MB limitation on recovered file size for bzip2recover
-- on selected platforms which support 64-bit ints. At the moment
-- all GCC supported platforms, and Win32.
-- (me, Alson van der Meulen)
--
--* Hard-code header byte values, to give correct operation on platforms
-- using EBCDIC as their native character set (IBM's OS/390).
-- (Leland Lucius)
--
--* Copy file access times correctly.
-- (Marty Leisner)
--
--* Add distclean and check targets to Makefile.
-- (Michael Carmack)
--
--* Parameterise use of ar and ranlib in Makefile. Also add $(LDFLAGS).
-- (Rich Ireland, Bo Thorsen)
--
--* Pass -p (create parent dirs as needed) to mkdir during make install.
-- (Jeremy Fusco)
--
--* Dereference symlinks when copying file permissions in -f mode.
-- (Volker Schmidt)
--
--* Majorly simplify implementation of uInt64_qrm10.
-- (Bo Lindbergh)
--
--* Check the input file still exists before deleting the output one,
-- when aborting in cleanUpAndFail().
-- (Joerg Prante, Robert Linden, Matthias Krings)
--
--Also a bunch of patches courtesy of Philippe Troin, the Debian maintainer
--of bzip2:
--
--* Wrapper scripts (with manpages): bzdiff, bzgrep, bzmore.
--
--* Spelling changes and minor enhancements in bzip2.1.
--
--* Avoid race condition between creating the output file and setting its
-- interim permissions safely, by using fopen_output_safely().
-- No changes to bzip2recover since there is no issue with file
-- permissions there.
--
--* do not print senseless report with -v when compressing an empty
-- file.
--
--* bzcat -f works on non-bzip2 files.
--
--* do not try to escape shell meta-characters on unix (the shell takes
-- care of these).
--
--* added --fast and --best aliases for -1 -9 for gzip compatibility.
--
-diff -Nru bzip2-1.0.2/COPYING bzip2-1.0.2.new/COPYING
---- bzip2-1.0.2/COPYING Thu Jan 1 01:00:00 1970
-+++ bzip2-1.0.2.new/COPYING Wed Jan 2 05:12:07 2002
-@@ -0,0 +1,39 @@
-+
-+This program, "bzip2" and associated library "libbzip2", are
-+copyright (C) 1996-2002 Julian R Seward. All rights reserved.
-+
-+Redistribution and use in source and binary forms, with or without
-+modification, are permitted provided that the following conditions
-+are met:
-+
-+1. Redistributions of source code must retain the above copyright
-+ notice, this list of conditions and the following disclaimer.
-+
-+2. The origin of this software must not be misrepresented; you must
-+ not claim that you wrote the original software. If you use this
-+ software in a product, an acknowledgment in the product
-+ documentation would be appreciated but is not required.
-+
-+3. Altered source versions must be plainly marked as such, and must
-+ not be misrepresented as being the original software.
-+
-+4. The name of the author may not be used to endorse or promote
-+ products derived from this software without specific prior written
-+ permission.
-+
-+THIS SOFTWARE IS PROVIDED BY THE AUTHOR ``AS IS'' AND ANY EXPRESS
-+OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
-+WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
-+ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY
-+DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
-+DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE
-+GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS
-+INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY,
-+WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING
-+NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS
-+SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
-+
-+Julian Seward, Cambridge, UK.
[EMAIL PROTECTED]
-+bzip2/libbzip2 version 1.0.2 of 30 December 2001
-+
-diff -Nru bzip2-1.0.2/ChangeLog bzip2-1.0.2.new/ChangeLog
---- bzip2-1.0.2/ChangeLog Thu Jan 1 01:00:00 1970
-+++ bzip2-1.0.2.new/ChangeLog Fri Feb 1 04:19:04 2002
-@@ -0,0 +1 @@
-+
-diff -Nru bzip2-1.0.2/INSTALL bzip2-1.0.2.new/INSTALL
---- bzip2-1.0.2/INSTALL Thu Jan 1 01:00:00 1970
-+++ bzip2-1.0.2.new/INSTALL Fri Feb 1 04:19:04 2002
-@@ -0,0 +1,182 @@
-+Basic Installation
-+==================
-+
-+ These are generic installation instructions.
-+
-+ The `configure' shell script attempts to guess correct values for
-+various system-dependent variables used during compilation. It uses
-+those values to create a `Makefile' in each directory of the package.
-+It may also create one or more `.h' files containing system-dependent
-+definitions. Finally, it creates a shell script `config.status' that
-+you can run in the future to recreate the current configuration, a file
-+`config.cache' that saves the results of its tests to speed up
-+reconfiguring, and a file `config.log' containing compiler output
-+(useful mainly for debugging `configure').
-+
-+ If you need to do unusual things to compile the package, please try
-+to figure out how `configure' could check whether to do them, and mail
-+diffs or instructions to the address given in the `README' so they can
-+be considered for the next release. If at some point `config.cache'
-+contains results you don't want to keep, you may remove or edit it.
-+
-+ The file `configure.in' is used to create `configure' by a program
-+called `autoconf'. You only need `configure.in' if you want to change
-+it or regenerate `configure' using a newer version of `autoconf'.
-+
-+The simplest way to compile this package is:
-+
-+ 1. `cd' to the directory containing the package's source code and type
-+ `./configure' to configure the package for your system. If you're
-+ using `csh' on an old version of System V, you might need to type
-+ `sh ./configure' instead to prevent `csh' from trying to execute
-+ `configure' itself.
-+
-+ Running `configure' takes awhile. While running, it prints some
-+ messages telling which features it is checking for.
-+
-+ 2. Type `make' to compile the package.
-+
-+ 3. Optionally, type `make check' to run any self-tests that come with
-+ the package.
-+
-+ 4. Type `make install' to install the programs and any data files and
-+ documentation.
-+
-+ 5. You can remove the program binaries and object files from the
-+ source code directory by typing `make clean'. To also remove the
-+ files that `configure' created (so you can compile the package for
-+ a different kind of computer), type `make distclean'. There is
-+ also a `make maintainer-clean' target, but that is intended mainly
-+ for the package's developers. If you use it, you may have to get
-+ all sorts of other programs in order to regenerate files that came
-+ with the distribution.
-+
-+Compilers and Options
-+=====================
-+
-+ Some systems require unusual options for compilation or linking that
-+the `configure' script does not know about. You can give `configure'
-+initial values for variables by setting them in the environment. Using
-+a Bourne-compatible shell, you can do that on the command line like
-+this:
-+ CC=c89 CFLAGS=-O2 LIBS=-lposix ./configure
-+
-+Or on systems that have the `env' program, you can do it like this:
-+ env CPPFLAGS=-I/usr/local/include LDFLAGS=-s ./configure
-+
-+Compiling For Multiple Architectures
-+====================================
-+
-+ You can compile the package for more than one kind of computer at the
-+same time, by placing the object files for each architecture in their
-+own directory. To do this, you must use a version of `make' that
-+supports the `VPATH' variable, such as GNU `make'. `cd' to the
-+directory where you want the object files and executables to go and run
-+the `configure' script. `configure' automatically checks for the
-+source code in the directory that `configure' is in and in `..'.
-+
-+ If you have to use a `make' that does not supports the `VPATH'
-+variable, you have to compile the package for one architecture at a time
-+in the source code directory. After you have installed the package for
-+one architecture, use `make distclean' before reconfiguring for another
-+architecture.
-+
-+Installation Names
-+==================
-+
-+ By default, `make install' will install the package's files in
-+`/usr/local/bin', `/usr/local/man', etc. You can specify an
-+installation prefix other than `/usr/local' by giving `configure' the
-+option `--prefix=PATH'.
-+
-+ You can specify separate installation prefixes for
-+architecture-specific files and architecture-independent files. If you
-+give `configure' the option `--exec-prefix=PATH', the package will use
-+PATH as the prefix for installing programs and libraries.
-+Documentation and other data files will still use the regular prefix.
-+
-+ In addition, if you use an unusual directory layout you can give
-+options like `--bindir=PATH' to specify different values for particular
-+kinds of files. Run `configure --help' for a list of the directories
-+you can set and what kinds of files go in them.
-+
-+ If the package supports it, you can cause programs to be installed
-+with an extra prefix or suffix on their names by giving `configure' the
-+option `--program-prefix=PREFIX' or `--program-suffix=SUFFIX'.
-+
-+Optional Features
-+=================
-+
-+ Some packages pay attention to `--enable-FEATURE' options to
-+`configure', where FEATURE indicates an optional part of the package.
-+They may also pay attention to `--with-PACKAGE' options, where PACKAGE
-+is something like `gnu-as' or `x' (for the X Window System). The
-+`README' should mention any `--enable-' and `--with-' options that the
-+package recognizes.
-+
-+ For packages that use the X Window System, `configure' can usually
-+find the X include and library files automatically, but if it doesn't,
-+you can use the `configure' options `--x-includes=DIR' and
-+`--x-libraries=DIR' to specify their locations.
-+
-+Specifying the System Type
-+==========================
-+
-+ There may be some features `configure' can not figure out
-+automatically, but needs to determine by the type of host the package
-+will run on. Usually `configure' can figure that out, but if it prints
-+a message saying it can not guess the host type, give it the
-+`--host=TYPE' option. TYPE can either be a short name for the system
-+type, such as `sun4', or a canonical name with three fields:
-+ CPU-COMPANY-SYSTEM
-+
-+See the file `config.sub' for the possible values of each field. If
-+`config.sub' isn't included in this package, then this package doesn't
-+need to know the host type.
-+
-+ If you are building compiler tools for cross-compiling, you can also
-+use the `--target=TYPE' option to select the type of system they will
-+produce code for and the `--build=TYPE' option to select the type of
-+system on which you are compiling the package.
-+
-+Sharing Defaults
-+================
-+
-+ If you want to set default values for `configure' scripts to share,
-+you can create a site shell script called `config.site' that gives
-+default values for variables like `CC', `cache_file', and `prefix'.
-+`configure' looks for `PREFIX/share/config.site' if it exists, then
-+`PREFIX/etc/config.site' if it exists. Or, you can set the
-+`CONFIG_SITE' environment variable to the location of the site script.
-+A warning: not all `configure' scripts look for a site script.
-+
-+Operation Controls
-+==================
-+
-+ `configure' recognizes the following options to control how it
-+operates.
-+
-+`--cache-file=FILE'
-+ Use and save the results of the tests in FILE instead of
-+ `./config.cache'. Set FILE to `/dev/null' to disable caching, for
-+ debugging `configure'.
-+
-+`--help'
-+ Print a summary of the options to `configure', and exit.
-+
-+`--quiet'
-+`--silent'
-+`-q'
-+ Do not print messages saying which checks are being made. To
-+ suppress all normal output, redirect it to `/dev/null' (any error
-+ messages will still be shown).
-+
-+`--srcdir=DIR'
-+ Look for the package's source code in directory DIR. Usually
-+ `configure' can determine that directory automatically.
-+
-+`--version'
-+ Print the version of Autoconf used to generate the `configure'
-+ script, and exit.
-+
-+`configure' also accepts some other, not widely useful, options.
diff -Nru bzip2-1.0.2/Makefile.am bzip2-1.0.2.new/Makefile.am
--- bzip2-1.0.2/Makefile.am Thu Jan 1 01:00:00 1970
+++ bzip2-1.0.2.new/Makefile.am Fri Feb 1 04:19:09 2002
@@ -529,263 +33,6 @@
+install-exec-hook:
+ $(LN_S) -f bzip2 $(DESTDIR)$(bindir)/bunzip2
+ $(LN_S) -f bzip2 $(DESTDIR)$(bindir)/bzcat
-diff -Nru bzip2-1.0.2/NEWS bzip2-1.0.2.new/NEWS
---- bzip2-1.0.2/NEWS Thu Jan 1 01:00:00 1970
-+++ bzip2-1.0.2.new/NEWS Sat Jan 26 01:02:57 2002
-@@ -0,0 +1,253 @@
-+
-+
-+0.9.0
-+~~~~~
-+First version.
-+
-+
-+0.9.0a
-+~~~~~~
-+Removed 'ranlib' from Makefile, since most modern Unix-es
-+don't need it, or even know about it.
-+
-+
-+0.9.0b
-+~~~~~~
-+Fixed a problem with error reporting in bzip2.c. This does not effect
-+the library in any way. Problem is: versions 0.9.0 and 0.9.0a (of the
-+program proper) compress and decompress correctly, but give misleading
-+error messages (internal panics) when an I/O error occurs, instead of
-+reporting the problem correctly. This shouldn't give any data loss
-+(as far as I can see), but is confusing.
-+
-+Made the inline declarations disappear for non-GCC compilers.
-+
-+
-+0.9.0c
-+~~~~~~
-+Fixed some problems in the library pertaining to some boundary cases.
-+This makes the library behave more correctly in those situations. The
-+fixes apply only to features (calls and parameters) not used by
-+bzip2.c, so the non-fixedness of them in previous versions has no
-+effect on reliability of bzip2.c.
-+
-+In bzlib.c:
-+ * made zero-length BZ_FLUSH work correctly in bzCompress().
-+ * fixed bzWrite/bzRead to ignore zero-length requests.
-+ * fixed bzread to correctly handle read requests after EOF.
-+ * wrong parameter order in call to bzDecompressInit in
-+ bzBuffToBuffDecompress. Fixed.
-+
-+In compress.c:
-+ * changed setting of nGroups in sendMTFValues() so as to
-+ do a bit better on small files. This _does_ effect
-+ bzip2.c.
-+
-+
-+0.9.5a
-+~~~~~~
-+Major change: add a fallback sorting algorithm (blocksort.c)
-+to give reasonable behaviour even for very repetitive inputs.
-+Nuked --repetitive-best and --repetitive-fast since they are
-+no longer useful.
-+
-+Minor changes: mostly a whole bunch of small changes/
-+bugfixes in the driver (bzip2.c). Changes pertaining to the
-+user interface are:
-+
-+ allow decompression of symlink'd files to stdout
-+ decompress/test files even without .bz2 extension
-+ give more accurate error messages for I/O errors
-+ when compressing/decompressing to stdout, don't catch control-C
-+ read flags from BZIP2 and BZIP environment variables
-+ decline to break hard links to a file unless forced with -f
-+ allow -c flag even with no filenames
-+ preserve file ownerships as far as possible
-+ make -s -1 give the expected block size (100k)
-+ add a flag -q --quiet to suppress nonessential warnings
-+ stop decoding flags after --, so files beginning in - can be handled
-+ resolved inconsistent naming: bzcat or bz2cat ?
-+ bzip2 --help now returns 0
-+
-+Programming-level changes are:
-+
-+ fixed syntax error in GET_LL4 for Borland C++ 5.02
-+ let bzBuffToBuffDecompress return BZ_DATA_ERROR{_MAGIC}
-+ fix overshoot of mode-string end in bzopen_or_bzdopen
-+ wrapped bzlib.h in #ifdef __cplusplus ... extern "C" { ... }
-+ close file handles under all error conditions
-+ added minor mods so it compiles with DJGPP out of the box
-+ fixed Makefile so it doesn't give problems with BSD make
-+ fix uninitialised memory reads in dlltest.c
-+
-+0.9.5b
-+~~~~~~
<<Diff was trimmed, longer than 597 lines>>
---- CVS-web:
http://cvs.pld-linux.org/SOURCES/bzip2-libtoolizeautoconf.patch?r1=1.7&r2=1.8&f=u
_______________________________________________
pld-cvs-commit mailing list
pld-cvs-commit@lists.pld-linux.org
http://lists.pld-linux.org/mailman/listinfo/pld-cvs-commit
