When builds fail, I get the mesage: Please post the topmost build error However, I'm running it on VT1 and I can't scroll up. It would be very nice if the error was saved to a file and then a message came up: There was an error building the package: dev-java/package/... would you like to submit this error to Gentoo developers <YES|no>? Reproducible: Always Steps to Reproduce:
It's not possible to know via code where it is that an ebuild fails. It is possible to log all of each build's output though. Have a look at PORT_LOGDIR in make.conf(5).
Maybe it would be more prectical to have an extra emerge option: emerge --bug-report dev-libs/perl... In normal use, if an emerge fails, it would tell you specifically to run the command above. Then running this command creates a bug reopts with all output saved to a file. It then offers to save the bug report to a file or to mail it directly. This avoids the slowdown and bloat of saving all output to a file while also allowing for useful and automated bug reports. What do you think?
Putting a hold on feature requests for portage as they are drowning out the bugs. Most of these features should be available in the next major version of portage. But for the time being, they are just drowning out the major bugs and delaying the next version's progress. Any bugs that contain patches and any bugs for etc-update or dispatch-conf can be reopened. Sorry, I'm just not good enough with bugzilla. ;)
Reopening for consideration
For bug #111436 we now log every build to PORT_LOGDIR or ${T}/build.log if PORT_LOGDIR is unset. In any case, the path of the build log is now always available via $PORTAGE_LOG_FILE. We can easily modify diefunc to print that path for the user's convenience.
In svn r5590 I've added the path of the build log to the die message.
This has been released in 2.1.2_rc4-r9.
