Check the MD5 before prelinking, prelink the binary and then check it again with prelink -y --md5. If both md5 outputs are different, it means that prelink did change the binary. It should not since prelink processes that kind of symbols (called "conflicts" on prelink language), on a special way and won't prelink the binary if it can't handle the "conflict" symbol.
Laurent Bonnaud <[EMAIL PROTECTED]> writes: >> It shouldn't, since the prelinking failed, but maybe it does. Try >> unprelinking just the lxdoom binary. > > It works: > > # prelink -u /usr/games/lxdoom > # prelink -u /usr/games/lxdoom-game-server > $ debsums -s lxdoom > [OK] > > $ lxdoom > LxDoom v1.4.4 (http://lxdoom.linuxgames.com/) > [...] > > So is this a bug in prelink ? > > -- > Laurent Bonnaud. > http://www.lis.inpg.fr/pages_perso/bonnaud/ > > > > > -- > To UNSUBSCRIBE, email to [EMAIL PROTECTED] > with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] > -- Andr�s Rold�n <[EMAIL PROTECTED]> GPG Key-ID: 0xB29396EB http://people.fluidsignal.com/~aroldan
pgp00000.pgp
Description: PGP signature
