I'm using x11-base/xorg-server-0.99.3-r1. Since then, i can't compile kdebase from-3.5 (configure fails on "imake" and "xmkmf". I'm using kde svn (3.5 branch), but i guess the problem still remains with the recent kde 3.5 release. I've got the same problem with tightvnc : configure fails because of missing xmkmf Reproducible: Always Steps to Reproduce: 1.(cd kde-3.5/kdebase;./configure) 2.or "emerge tightvnc" 3.
1/ Try with latest kde ebuilds *in portage*, not svn snapshots. 2/ If it still fails, then post come actual error messsages and *attach* config log here and reopen. 3/ x11-base/xorg-server is package.masked and adjusting ebuilds for modular X is non-trivial task. 4/ Don't file summary bugs about different ebuilds.
> 1/ Try with latest kde ebuilds *in portage*, not svn snapshots. Ok. The pb is not here anymore with the gentoo ebuild thanks to the kdebase-3.5.0_beta2-noimake.patch > 2/ If it still fails, then post come actual error messsages and *attach* config log here and reopen. * Applying x86.patch ... [ ok ] * Applying tightvnc-1.3_alpha7-darwin.patch ... [ ok ] >>> Source unpacked. /usr/portage/net-misc/tightvnc/tightvnc-1.3_alpha7.ebuild: line 49: xmkmf: command not found !!! ERROR: net-misc/tightvnc-1.3_alpha7 failed. !!! Function src_compile, Line 49, Exitcode 127 !!! xmkmf failed !!! If you need support, post the topmost build error, NOT this status message. > 3/ x11-base/xorg-server is package.masked and adjusting ebuilds for modular X is non-trivial task. I understand that perfectly. Though, my understanding was that we could/should still reports bugs. > 4/ Don't file summary bugs about different ebuilds. As i stated in title, I think this bug is about modular xorg-x11. tightvnc and kdebase are only two examples to explain the problem. Now that the pb is only with tightvnc, i chaneg the bug report accordingly. Hope it's ok.
(In reply to comment #2) > > 4/ Don't file summary bugs about different ebuilds. > > As i stated in title, I think this bug is about modular xorg-x11. tightvnc and > kdebase are only two examples to explain the problem. Uhm, we really need to track each such bug separately (there are already some examples), no summary bugs for modular X, please.
the tightvnc ebuild just needs updating i didnt try the server side use flag i might later tho but for just client i had to merge app-text/rman x11-misc/xmkmf x11-misc/gccmakedep the last needing ~amd64 keywords also
(In reply to comment #4) > x11-misc/gccmakedep > > the last needing ~amd64 keywords also Please file a new bug to the amd64 team requesting this. Fixed.
