Compilation of x11-misc/xkeyboard-config failed with message: ... config.status: executing po/stamp-it commands *********************************************************** xkeyboard-config is configured with the following parameters: XKB base directory: "/usr/share/X11/xkb" Symbolic link(s) to legacy rules: xorg Compatibility rules are included *********************************************************** >>> Source configured. >>> Compiling source in /var/tmp/portage/x11-misc/xkeyboard-config-2.1/work/xkeyboard-config-2.1 ... make -j6 clean make: *** No rule to make target `clean'. Stop. emake failed * ERROR: x11-misc/xkeyboard-config-2.1 failed (compile phase): * (no error message) * * Call stack: * ebuild.sh, line 56: Called src_compile * environment, line 3438: Called die * The specific snippet of code: * emake clean || die; When I manually started 'ebuild /usr/portage/ebuilds/x11-misc/xkeyboard-config/xkeyboard-config-2.0-r1.ebuild compile' it failed with that message too. Apparently ebuild tried start 'emake clean' command in ...work/xkeyboard-config-2.0 dir and not in appropriate ...work/xkeyboard-config-2.0_build dir. When I manually started 'make clean && make' in _build dir everything was OK. There is no difference between 2.0-r1 and newer 2.1. Older 2.0-r1 was succesfully compiled and installed in 24.12.2010 but now it is impossible without manual intervention into ebuild process. Only possible workaround of this situation right now is run manually 'make' in ...build directory, create .compiled file and continue with 'ebuild <package.ebuild.name> install...' It seems like 'emake' has now some problem with ..._build directory at least in case of these ebuilds. Or I'm mislead and real problem reside in completely different place. I have portage-2.2.0_alpha24. Reproducible: Always Actual Results: compilation phase failed on 'make clean' Expected Results: compilation completed without error.
Attach full build log.
Created attachment 262843 [details] requested xkeyboard-config-2.1 build.log
QA Notice: ECLASS 'autotools-utils' inherited illegally in x11-misc/xkeyboard-config-2.1 setup Any chance resync will fix this ? Or perhaps it's a parallel make problem. Post your 'emerge --info'.
(In reply to comment #3) > QA Notice: ECLASS 'autotools-utils' inherited illegally in > x11-misc/xkeyboard-config-2.1 setup > > Any chance resync will fix this ? > Or perhaps it's a parallel make problem. > Post your 'emerge --info'. > You picked up true reason of this problem. In error description I posted only part of whole error message. In removed part was line which was extremely important to solving this problem: * This ebuild used the following eclasses from overlays: * /usr/portage/overlays/layman/x11/eclass/xorg-2.eclass After removing layman overlay from tree everything became smooth. So problem doesn't lie in portage mainline, but in overlay maintaners and inconsistency of their tree with mainline portage. I'm sorry for wasting your time. Every day we learn something new, so next time I will be more carefull about portage warnings. So from my point of view it's time to mark bug report as fixed. Have a nice day.
please reopen bug. I've got the same problem after gcc update version 4.4.4 to 4.4.5 following the official howto. emerge -uav gcc gcc-config .... source /etc/profile emerge --oneshot sys-libs/libstdc++-v3 revdeprebuild ... emerge -eav system emerge -eav world breaks compiling xkeyboard-config with the same problem. I would be very pleased for any ideas!
excuse me. Solved the issue by deleting ebuild and resync portage tree. it was too late for me yesterday.
