This is the mail archive of the gcc@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]

Re: egcs-1.0.1.tar.bz2 damaged?


Tobias Polzin telecommunicated (on 08Jan):
| Did anyone have the same problem?
| 
| bzip2 -tvv egcs-1.0.1.tar.bz2
|   egcs-1.0.1.tar.bz2: 
|     block [1: huff+mtf rt+rld] ok
|     block [2: huff+mtf rt+rld] ok
|     block [3: huff+mtf rt+rld] ok
|     block [4: huff+mtf rt+rld] ok
|     block [5: huff+mtf rt+rld] ok
|     block [6: huff+mtf rt+rld] ok
|     block [7: huff+mtf rt+rld] ok
|     block [8: huff+mtf rt+rld] ok
|     block [9: huff+mtf rt+rld] ok
|     block [10: huff+mtf 
| bzip2: block overrun during decompression,
|         which probably means the compressed file
|         is corrupted.
|         Input file = egcs-1.0.1.tar.bz2, output file = (none)
| 
| (on an x86 with new bzip2, executable downloaded directly from bzip2 home
| page, egcs-1.01.tar.bz2 from german mirror ftp.fu-berlin.de)

No problem here.  See if you get what i get:
	# sum -r egcs-1.01.tar.bz2
	30360  7523

egcs-1.01.tar.bz2 is 7703039 bytes.

Beyond that, this section of the man page might be relevant:

	For files compressed with the default 900k block size, bunzip2 will
        require about 4600 kbytes to decompress.  To support decompression of
        any file on a 4 megabyte machine, bunzip2 has an option to decompress
        using approximately half this amount of memory, about 2300 kbytes.
        Decompression speed is also halved, so you should use this option only
        where necessary.  The relevant flag is -s.

-- 
Jean-Pierre Radley   jpr@jpr.com   XC/XT Custodian   Sysop, CompuServe SCOForum


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]