I tried the FAQ's recipe for : I want to perform the ./configure step myself. Can I?" for emacs, but it failed. The problem is that ebuild.sh's dyn_compile builds a info dir, which the qmerge step relies on. If you do the compile yourself, then this doesn't get created. My workaround was to do the "ebuild compile", then ./configure & make, then "ebuild qmerge". The resulting flag info in the info dir is then incorrect, but at least it works. Maybe the FAQ should recommend that too, or else list instructions of how to perform the missing steps. As an aside, it might be cleaner to split the "ebuild compile" into separate configure/compile steps, such that you can do your own configure and then let ebuild do the compiling, .compiled touching, build-info making etc.
*** This bug has been marked as a duplicate of 1262 ***
1262 says "there needs to be a simpler way of doing your own configure step", which is going to take some while to discuss and implement, especially in light of 6986. This 5898 says "please update the currently broken FAQ", which would take little effort and help people out today. So I don't think it as a duplicate, but a fix that may in future be superceded by new functionality resulting from 1262 or 6986. And if such new functionality appears, then the FAQ will still need updating accordingly.
Is this still a valid bug then? //ZhEN
I guess this is a documentation thing
If this is a duplicate, then I am closing it. //ZhEN