OK, this has been happening for awhile, across multiple kdelibs versions. Because I haven't seen anyone else mention it, I'm guessing it could be multi-job specific (I run dual Opterons), and possibly amd64 specific as well. Somewhere during the compile (during kabc compile in the error copied below), make fails due to no rule to make kresources/libkresources.la. Diving into the temp working dir, if I cd to kresources and invoke make manually there, I can then resume the emerge using ebuild <package> compile (thus keeping the current workdir and work already completed), and then complete the install, package, and emerge -k steps to merge the package I just created. Thus, the problem appears to be with the compile ordering and an incomplete make dependency tree. The kresources stuff needs to be moved earlier in the process. Again, this has been happening thru several versions. I'm currently attempting to merge the kde-3.4.0-beta2 stuff (yes, I know it's not all ~amd64 yet), so the following error is on that, but the same general no kresources target error has occurred since kde-3.2.x, perhaps earlier, here, with the same manual solution, manually make the kresources stuff and then continue with the ebuild. make[3]: *** No rule to make target `../kresources/libkresources.la', needed by `libkabc.la'. Stop. make[3]: *** Waiting for unfinished jobs.... make[3]: Leaving directory `/tmp/portage/kdelibs-3.4.0_beta2/work/kdelibs-3.3.92/kabc' make[2]: *** [all-recursive] Error 1 make[2]: Leaving directory `/tmp/portage/kdelibs-3.4.0_beta2/work/kdelibs-3.3.92/kabc' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/tmp/portage/kdelibs-3.4.0_beta2/work/kdelibs-3.3.92' make: *** [all] Error 2 !!! ERROR: kde-base/kdelibs-3.4.0_beta2 failed. !!! Function kde_src_compile, Line 166, Exitcode 2 !!! died running emake, kde_src_compile:make Reproducible: Always Steps to Reproduce: emerge kdelibs Actual Results: Failed as explained above, due to kresources being needed but no target to make it. Making it manually and continuing the ebuild process works. Expected Results: kresources, or at least the missing *.la file, should have already been made earlier in the process, or the target made available so it can be made where needed. emerge should have proceeded uneventfully. Current emerge info to be attached. However, again, note that this has been occurring for some time, so it's not a simple current config issue.
Created attachment 51532 [details] emerge info output
are you using unsermake?
I am not using unsermake now, no. I had been for awhile, but commented that line out in make.conf when it wouldn't compile some KDE addon or another. (BTW, I've wondered about it... I was using an older version, 0.3.0.4254.0, because the two since then, 0.3.1.4280.0 & 0.3.1.4319.0, didn't seem to work even on the KDE core stuff, at least as of 2004.12.09, according to my note on 4319 in my package.mask. Is that a known issue on AMD64, or do they work for others, amd64 or not? I just figured why bother since I can't seem to get the last couple versions to work at all, and the version that does work for the main KDE stuff I had to keep turning off when compiling stuff like k3b, krename, and the like.)
Note that newer versions of kde (ala 3.4) will use unsermake whether or not you have the UNSERMAKE variable set. If it can find it, it will use it, which is what I'm guessing is happening here.
OK, egg on my face! The problem was of my own making. I had been using DO_NOT_COMPILE to manage what portions of the big KDE packages got compiled, and had turned off kresources for kdepim, so the kresources section of kdelibs wasn't compiling either! Marking resolved/invalid.
