as in the description. The problem is that it looks for the plugins in a directory /usr/lib64/ekg2/plugins and they get installed into /usr/lib64. On x86 the directory is proper - /usr/lib/ekg2/plugins so the installation procedure is to blame. Adding a directory /usr/lib64/ekg2 and linking plugins to '..' fixes this problem and ekg2 runs just fine (for a couple of hours now) Reproducible: Always Steps to Reproduce: 1. emerge net-im/ekg2 on amd64 2. 3.
hackish solution in the ebuild added to bug 107741
Please let devs control the severity.
Created attachment 71869 [details] fixed ebuild It turns out that using ./configure --prefix=/usr instead econf solves this behavior - to make the change least invasive the substitution is made for amd64 only, for other archs econf remains, although I suppose there may be other architectures affected. This ebuild (and resulting soft) was tested on amd64, x86 and ppc
This bug can be safely closed - current ebuild does not have this problem
Closing
