On 03 Dec 2007, at 05:59, Koen van der Drift wrote:
>
> On Dec 2, 2007, at 11:49 PM, Jean-François Mertens wrote:
>
>> But I see that Peter will give you a quicker fix - at least for
>> this specific problem - the principle is the same, and if
>> you want to be thorough you go through the check I
>> suggested _ it doesn't take that long .. :)
>
> Actually there are dozes of binaries in emboss (it's a suite of
> programs). Only three of them have the word 'emboss' in them. If I
> change the test to:
>
> dpkg -L emboss | grep bin | xargs file | fgrep 'Mach-O' | cut -f1 -d:
>
> I still get a long list, assuming that I didn't make an error. So
> it would take some more time to go through all of them one by one :)
No .. That's why the file in question was labeled "$f" in :
> dpkg -S emboss | xargs file | fgrep 'Mach-O' | cut -f1 -d:
> will give you the list of all binaries in your pkg
>
> Then, for each of those in turn, say $f, run
>
> nm -mgu $f | fgrep -v ' (from '
to do in fact :
for f in `dpkg -S emboss | xargs file | fgrep 'Mach-O' | cut -f1 -d:` \
do echo $f;
nm -mgu $f | fgrep -v ' (from '
done
Cheers,
JF
-------------------------------------------------------------------------
SF.Net email is sponsored by: The Future of Linux Business White Paper
from Novell. From the desktop to the data center, Linux is going
mainstream. Let it simplify your IT future.
http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4
_______________________________________________
Fink-devel mailing list
Fink-devel@lists.sourceforge.net
http://news.gmane.org/gmane.os.apple.fink.devel
