Published MD5 checksums for GCC 3.3.1 sources

[Jim Fischer]

FYI:

I just downloaded the file 'gcc-3.3.1.tar.bz2' from three different GCC 
mirror sites, and all three copies have the following MD5 checksum:

    $ md5sum gcc-3.3.1.tar.bz2
    1135a104e9fa36fdf7c663598fab5c40  gcc-3.3.1.tar.bz2

This checksum does not match the value shown in the 'md5.sum' file that 
I downloaded from the same directory as the 'gcc-3.3.1.tar.bz2' file:

    $ cat md5.sum
    4015ef36f7aca44780e2e2042bde21ed  gcc-3.3.1.tar.bz2
    46d58197212818b5f7c403267ff24e4e  gcc-3.3.1.tar.gz
    126ca7fd1f08f956a279afce1611d89c  gcc-ada-3.3.1.tar.gz
    d516121fe0016a90b4299afbba3e5b69  gcc-core-3.3.1.tar.gz
    0e0f9c0fe879487beaf3b6029d03e6a9  gcc-g++-3.3.1.tar.gz
    7435533bbe280a50c4589f2f656112e2  gcc-g77-3.3.1.tar.gz
    9c470adc7893a158e09dd6a26df63578  gcc-java-3.3.1.tar.gz
    068708f6b0957230945c98c12e21ab7c  gcc-objc-3.3.1.tar.gz
    b1e75a212fb5119a7824c1d5ceb14590  gcc-testsuite-3.3.1.tar.gz

FWIW, I'm using 'md5sum' version 4.5.3 on a Red Hat 9 Linux box. I've 
used this program many times to calculate the MD5 checksum of a 
downloaded file for the purpose of comparing the calculated checksum 
against the published checksum. So I'm pretty sure my local 'md5sum' 
checksum program is not at fault here.

-- 
Jim Fischer <jfischer_5809@yahoo.com>