If I include /usr/bin or /usr/kde/3.1/bin in /etc/prelink.conf, prelink successfully assigns memory addresses, but it segfaults while actually prelinking target files. Same behaviour using the -n flag. I followed the official howto, recompiled ebuils like ORBit, tcp-wrappers, gimp-1.3, lesstif and openmotif, which caused some warning (before the assignement of addresses) but nothing changed (well, of course every warning disappeared). I'm running 1.4rc1 with the ~x86 keyword enabled and just completely updated. I've got just a few ebuilds unmasked: kde3.1pre5, evolution-1.2.1, gtkhtml, gimp-1.3, gnumeric, and foser's unofficial gnome-2.1.5 packages. Also, I did an emerge -e world less than a month ago, just after upgrading to glibc-2.3.1 Attached is the complete prelink output. prelink-usr-bin.log -> just "-l /usr/bin" in /etc/prelink.conf prelink-usr-kde-31-bin -> just "-h /usr/kde/3.1/bin" in /etc/prelink.conf prelink.log -> every other non problematic directiry in /etc/prelink.conf
Created attachment 7063 [details] /usr/kde/3.1/lib
Created attachment 7064 [details] log with "-h /usr/kde/3.1/bin"
Created attachment 7065 [details] successful prelink -afmRvn
Ops ... the attachment with id=7063 is the log with "-l /usr/bin" ... sorry :(
If you can could you run strace and gdb on the prelink application to backtrace the error, ie. "strace prelink -afmRv" and gdb prelink gdb>set args -afmRv gdb>run <segfault> gdb>bt <backtrace, report this> gdb>quit I have no idea Stefan
Well, -n is the same as no prelinking... so that's no the solution... See man pages: -n --dry-run Don't actually prelink anything, just collect the bina- ries/libraries, assign them addresses and with -v print what would be prelinked.
Try the new version, closing the bug as nothing has been reported for a while.
