Re: checklib
- To: debian-devel@lists.debian.org
- Subject: Re: checklib
- From: Oleg Verych <olecom@flower.upol.cz>
- Date: Fri, 1 Jun 2007 20:53:10 +0000 (UTC)
- Message-id: <[🔎] slrnf612g6.2k2.olecom@flower.upol.cz>
- References: <4655D8B8.8020903@debian.org> <87sl9epym2.fsf@glaurung.internal.golden-gryphon.com> <20070530145915.GA24720@zulo.hadrons.org> <87ejkythlf.fsf@glaurung.internal.golden-gryphon.com> <20070530162843.GD19765@ouaza.com> <87646atf9a.fsf@glaurung.internal.golden-gryphon.com>
* From: Manoj Srivastava
* Date: Wed, 30 May 2007 12:04:01 -0500
* Organization: The Debian Project
[]
> (I tend not to optimize before determining whether it is needed).
Even trailing whitespace your editor tend not to remove, before X
time ;)
[]
> If someone wants to port my simple shell scripts into gobs
> and gobs of python; they can get it from ./debian/common/checklibs
> files in any of my packages; and they can browse on arch.debian.org for
> easy access.
I've got it from your kernel-package. And want to `release early' my
non working version, mainly due to finding bugs in the binutils's
readelf and comparing it to elfutils'.
Before that, let me publish testcase for surely buggy `readelf':
,---[tst-readelf.sh]
cd /tmp/
exec 2>/dev/null
e=bin.elfs
o=bin.objs
elf() {
readelf -sDW -- $* | sed -n -e '
/LOCAL/d;/UND/{ s_\([^ \t]*\)$_|\1_;s_[^|]*|__;p;}'
}
elf /bin/* | sort -u >$e
objdump -T -- /bin/* | sed -n -e '
/*UND*/{ s_\([^ \t]*\)$_|\1_;s_[^|]*|__;p;}' | sort -u >$o
__diff() {
>$1 diff -u $e $o
ls -l $1
}
__diff elfs_obj.diff # i have non zero diff here and zero one below
echo note size, but [press enter] ; read f
for i in /bin/*
do elf $i
done | sort -u >bin.elfs
__diff 0
echo so, readelf is buggy "?;)"
---'
ftp://flower.upol.cz/checklibs...
here it is anyway.
Notes about original:
- `basename' doesn't work,
- unlink early, rather than that "trap" bloat,
- "progname" isn't used anyway,
- awk, perl overkill, (there could be `python' easyly ;)
- `objdump' can handle one file at time (and not buggy).
+ i would suggest $PATH compatible EXTRA_.... syntax
Anyway it works! My is not yet ;)
Reading this thread, i just don't know what to implement (thus how).
If somebody can summarize, i can more forward a bit faster.
____
Reply to: