On 01/07/11 15:29, Somebody in the thread at some point said:
> Maybe it means the stuff in the f12 tarball is broken but I am
not sure
> you proved that yet. You just show that the version in the f12 tarball
> has different size (so naturally different md5sum). The breakage could
> still be in some other library from the tarball environment.
That seems unlikely, because with everything else remaining the same, a
new coreutils package (from F13 repository) fixes it. And coreutils
doesn't bring any libs with it, from what I can see. So since the new,
working coreutils links against all the same libraries it doesn't bring
with it, that indicates that the coreutils in the rootfs tar ball is at
fault here. Or am I missing something?
Correct me if I am wrong but you mention that for the first time now :-)
In any event I cannot reproduce your problem just by bringing over
sha512sum from the rootfs tarball:
1) download
http://ftp.linux.org.uk/pub/linux/arm/fedora/rootfs/rootfs-f12.tar.bz2
2) untar, scp rootfs-f12/usr/bin/sha512sum <mybox>:/tmp
3) On mybox,
[root@ivmon ~]# /tmp/sha512sum /tmp/z
1f1e6f098e99bb0ab52c3142f0fb545b00470d267823d44fd609fdaae1a6f45fb437de931fa16bbb4a702c0cba7abb9954b737ff4edb30f16ae39a2c67ee6bb7
/tmp/z
ie, the same result as
[root@ivmon ~]# sha512sum /tmp/z
1f1e6f098e99bb0ab52c3142f0fb545b00470d267823d44fd609fdaae1a6f45fb437de931fa16bbb4a702c0cba7abb9954b737ff4edb30f16ae39a2c67ee6bb7
/tmp/z
-Andy