Ebuild fail to install vnc.so into /usr/X11R6/lib/modules/extensions. The script vncinstall expects <prefix>/usr/X11R6/lib/modules/extensions to exist if X is installed. Naturally this isn't true because this is only our image directory. A simple fix is to check for use/has of X windows and create ${D}/usr/X11R6/lib/modules/extensions as apropriate. Reproducible: Always Steps to Reproduce: 1. emerge vnc-4.0 2. note that /usr/X11R6/lib/modules/extensions/vnc.so is conspiciously lacking 3. profit !
Created attachment 43691 [details, diff] Primitive patch for the bug I don't know if my explanation was clear enough, but hopefully, this patch can make it clearer. Or at least, make it work.
*** Bug 70729 has been marked as a duplicate of this bug. ***
Please use the patch from the other bug. Also, this vnc module bites. xf4vnc has a jpeg, or, tightvnc type encoding available, but is only x86. I've even tried resurrecting the old tightvnc-4.0beta but had compile issues. It looks like I'm SOL for a remote desktop thingy as fast as the old tightvnc-4.0beta X module on amd64.
I've been using vnc.so (built using the patch from Bug 70729) for several weeks now, without any issues. Are there any reasons not to put this into portage?
I second Sebastian's comment. The patch from Bug 70729 works great for me as well.
In CVS, thanks!
