Andy Green wrote:
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 :-)
It is not at all unlikely that I unintentionally ommited some of these
important details. :-/
In any event I cannot reproduce your problem just by bringing over
sha512sum from the rootfs tarball:
2) untar, scp rootfs-f12/usr/bin/sha512sum <mybox>:/tmp
3) On mybox,
[root@ivmon ~]# /tmp/sha512sum /tmp/z
ie, the same result as
[root@ivmon ~]# sha512sum /tmp/z
OK, that IS weird, because I can!
[root@sheeva /usr/src/arm/rootfs-f12]# usr/bin/sha512sum /bin/bash
[root@sheeva /usr/src/arm/rootfs-f12]# sha512sum /bin/bash
The results are definitely different when using the sha512sum from the
(/usr/src/arm/rootfs-f12 is a fresh, pristine tarball extract)
Where are our methods diverging?