checking for xmkmf... not found configure: error: xmkmf/imake not found. Please make sure it's in PATH! !!! ERROR: The ebuild did not complete successfully. !!! Function kde_src_compile, Line -7419, Exitcode 1 !!! died running ./configure, kde_src_compile:configure !!! emerge aborting on /usr/portage/kde-base/kdebase/kdebase-3.0.3.ebuild .
the command i runned was: emerge -u kde all the other software was updated
The old version of openmotif used to provide xmkmf/imake. This probably overwrote the one that came with xfree. The new version of openmotif does not install xmkmf. This means that you could lose xmkmf/imake if you had installed the old openmotif version after installing X. Re-emerging X may be best to get this back. or going back to version before 2.2.2 can make this work.
Nick, openmotif installed xmkmf??
If this openmotif-based explanation is true, it'll solve not just this bug but another one, several months old, about the same thing. I can't find it now, but several people have reported this at one time or another. Nick or someone, please confirm this explanation so I can reassign these to whoever the openmotif guy is! :-)
openmotif-2.1.30 installed xmkmf and imake. I have spent the last three days playing with the openmotif-2.2.2 install. I went from configure to imake and then back to configure for installing it. It appears that the imake based ebuild is not actively maintained anymore and doing things via configure is the supported way now. openmotif-2.2.2-r1 is now in portage and installs things properly back into /usr/X11R6 instead of just /usr. imake and xmkmf are not installed with 2.2.2 or 2.2.2-r1. Anybody who installed 2.1.30 probably overwrote the xmkmf and imake from xfree. These people will need to re-emerge xfree. Please test the openmotif-2.2.2-r1.ebuild and let me know if there are any other problems you are aware of.
Adrian: please confirm - emerge xfree and the new openmotif, then try kdebase again.
I had the same problem (imake/openmotif), newer openmotif and reemerging xfree worked, resolved #5160, I resolve this bug, too.
