[coyotos-dev] Build xenv on Ubuntu

Jonathan S. Shapiro shap at eros-os.com
Thu Mar 1 14:18:54 CST 2007


Chris:

I really don't know what to tell you. Those tarballs are bit-identical
with the ones from FSF. sha1sum output below. The top one is from FSF,
the middle one is the one I got by rsyncing from coyotos.org. The bottom
one is the one that we checked out from OpenCM locally.

At this point I'm suspecting you may have a library bug on your end
somewhere, because we are successfully unpacking and building this on
multiple machines and various OS versions. I'm not sure what else to try
here.

At minimum, might be time to do a forced fsck on your FS (shutdown -F).
Could be a memory error, but that wouldn't tend to be so repeatable.
Could be a bug in bzip2.

shap

5c80fd5657da47efc16a63fdd93ef7395319fbbf  binutils-2.16.1.tar.bz2
5c80fd5657da47efc16a63fdd93ef7395319fbbf  /home/shap/alien/ccs-xenv/SOURCES/binutils-2.16.1.tar.bz2
5c80fd5657da47efc16a63fdd93ef7395319fbbf  /home/shap/WORK/old-schema/coyotos/src/ccs-xenv/SOURCES/binutils-2.16.1.tar.bz2

On Thu, 2007-03-01 at 14:09 -0500, Christopher Nelson wrote:
> How's this for strange:
> 
> christopher at titan:~/coyotos/ccs-xenv/SOURCES$ bzip2 -tvv
> binutils-2.16.1.tar.bz2 
>   binutils-2.16.1.tar.bz2: 
>     [1: huff+mtf rt+rld]
>     [2: huff+mtf rt+rld]
>     [3: huff+mtf rt+rld] 
>     [4: huff+mtf rt+rld]
>     [5: huff+mtf rt+rld]
>     [6: huff+mtf rt+rld]
>     [7: huff+mtf rt+rld]
>     [8: huff+mtf rt+rld]
>     [9: huff+mtf rt+rld]
>     [10: huff+mtf rt+rld]
>     [11: huff+mtf rt+rld] 
>     [12: huff+mtf rt+rld]
>     [13: huff+mtf rt+rld]
>     [14: huff+mtf rt+rld]
>     [15: huff+mtf rt+rld]data integrity (CRC) error in data
> 
> You can use the `bzip2recover' program to attempt to recover 
> data from undamaged sections of corrupted files.
> 
> christopher at titan:~/coyotos/ccs-xenv/SOURCES$ sha1sum -c
> ~/Desktop/SHA1SUMS
> binutils-2.16.1-bfd-hash-tweak.patch: OK
> binutils-2.16.1-callahan.patch: OK
> binutils-2.16.1-cross-gprof.patch: OK
> binutils-2.16.1-psignal.patch: OK
> binutils-2.16.1-skip-comments.patch: OK
> binutils-2.16.1-stabs-tweak.patch: OK
> binutils-2.16.1.tar.bz2: OK
> binutils-2.17-bfd-hash-tweak.patch : OK
> binutils-2.17-cross-gprof.patch: OK
> binutils-2.17-skip-comments.patch: OK
> binutils-2.17.tar.bz2: OK
> capos-binutils-2.16.1.patch: OK
> capos-binutils-2.17.patch: OK
> capos-gcc-3.4.6.patch: OK
> capos-newlib-1.13.0.patch : OK
> coyotos-gcc-4.0.2.patch: OK
> gcc-3.4.6-arm-bigendian.patch: OK
> gcc-3.4.6-arm-lib1asm.patch: OK
> gcc-3.4.6-arm-nolibfloat.patch: OK
> gcc-3.4.6-pr15068-fix.patch: OK
> gcc-core-3.4.6.tar.bz2: OK
> gcc-g++- 3.4.6.tar.bz2: OK
> glibc-2.3.5.tar.bz2: OK
> glibc-coyotos.patch: OK
> newlib-1.13.0.tar.bz2: OK
> newlib-cvs20051119.patch.bz2: OK
> README: OK
> 
> -----------
> 
> The following files are messed up according to bzip2 -tvv: 
> 
> binutils-2.16.1.tar.bz2
> binutils-2.17.tar.bz2
> gcc-core-3.4.6.tar.bz2
> glibc-2.3.5.tar.bz2
> newlib-1.13.0.tar.bz2
> 
> I wiped out the directory and rsynced twice, once including the -c
> flag.  rsync passed, as do the SHA1SUMS you gave me.  I also checked
> the sha1sums and bzip2 -tvv before and after building.  Same
> problems. 
> 
> -={C}=-
> 
> 
> 
-- 
Jonathan S. Shapiro, Ph.D.
Managing Director
The EROS Group, LLC
+1 443 927 1719 x5100



More information about the coyotos-dev mailing list