Emerge (when asked the -v option) could show also a typical compilation time (for a tipical processor, adding this info in the description of the package). This would help greatly and is simple to implement Reproducible: Always Steps to Reproduce: 1. 2. 3.
This is not simple. It'd be a 'dumb' field that would require a fair amount of thought to have marginally correct times in it. It's also _VERY_ unlikely be be within 20% accurate ever. Too many factors contribute. Here's a short list: compiler, version of compiler, flags used to compile the compiler, flags, memory usage, available memory, disk speed, bandwidth, CPU speed, number of CPUs, system availability, induced latency (FBs), enable/running system features (prelink, caching, PIC, PIE, GRSEC, etc...), dynamic vs. static supporting binaries, sandbox, architecture, and useflags.
*** Bug 45441 has been marked as a duplicate of this bug. ***
Related to bug 10365?
*** This bug has been marked as a duplicate of 10365 ***
