Nikos Chantziaras <realnc@arcor.de> wrote:
> Arthur Hagen wrote:
>> [...]
>> What seems to make the most difference for KDE speed is to install
>> prelink, and then prelink all libraries and binaries on the system,
>> and then set the flag that tells KDE that the system is prelinked. This
>> is especially true on systems with relatively slow CPUs.
>
> Does this have any ill effects with emerge? RPM-based distros are
> hash-checking the executables, modifying them can have strange
> effects. Is emerge immune to that?

It has no adverse effects on emerge or gentoo tools. It can have an effect
on some tripwire type tools which erroneously make the assumption that
binaries should be unchanged. prelink is a somewhat simplified cousin of
IRIX' "rqs" (requickstart) system. Since IRIX by default requickstarts
after installation, most tripwire type tools had to start doing the right
thing, and checksum an unlinked temporary copy, not the
quickstarted/prelinked code. Else they would be rather useless on IRIX
systems (and later, linux systems with prelink).

One caveat: You need to have "pic" enabled as a USE flag, system wide. But
having position independent code is usually a good idea anyhow.

Regards,
--
*Art