On Sunday 18 April 2010 17:38:19 Tanstaafl wrote: > I must be missing something obvious... > > When updating gcc, and thus emerging -e both system and world
Why are you doing that? Have you verified that you have in fact updated gcc from one version to another with an incompatible ABI? There is a false idea floating about that gcc updates require updating -e world. This is not true. > , where are > the info/warn/errors logged? I see a whole bunch of separate/individual > logs ion /var/log/portage/elog, but what I'm looking for is a single, > easily readable log of all of the result info/warn/errors for each package. Configure it in /etc/make.conf, mine looks like so: PORT_LOGDIR=/var/log/portage PORTAGE_ELOG_CLASSES="warn error log qa" PORTAGE_ELOG_SYSTEM="save" Adapt to you own needs. If you don't have this configured, then the logs are not stored. To see them again, read the ebuilds or re-run emrge -- alan dot mckinnon at gmail dot com
