On Mon, Mar 2, 2009 at 2:43 AM, Allan McRae <[email protected]> wrote: > Thomas Bächler wrote: >> >> Allan McRae schrieb: >>> >>> This is the point of this comment: >>> # Run in minimal chroot to avoid false positives due to dependencies. # >>> Chroot can be built with: >>> # sudo mkarchroot <chrootdir>/root glibc coreutils findutils grep tar >>> gzip >>> >>> So, in your example, if you are testing if libA needs a rebuild due to >>> libC, you only extract libA in your chroot, not libB. The ldd can not chain >>> its way to libC. So ti ends up doing the same thing as readelf. >> >> Now I understand it. >> >> Still, if you use readelf it does not matter what the environment is, you >> could run it on any system which is not even Arch, or is the wrong >> architecture or anything. >> > > Well, if that did not convince me, this does. I just noticed that "readelf > --dynamic" appears to be a lot faster than "ldd". On my /usr/bin/*, readelf > takes ~0.2sec while ldd takes ~12sec. I will test this out with an actual > run of the script tomorrow. > > Allan > > >
Status update on the rebuild?
