On 2010-04-18 1:05 PM, Alan McKinnon wrote: > 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? Because it wasn't a minor bugfix update? I'm going from 4.1.2 to 4.3.4. > Have you verified that you have in fact updated gcc from one version > to another with an incompatible ABI? Since the GCC upgrade guide doesn't mention a way to do this, no, I haven't... so how does one verify this, Obi-Wan? ;) > There is a false idea floating about that gcc updates require > updating -e world. > > This is not true. I've heard this before, but could never get a definitive answer on how to know for sure when you do and don't need to... >> 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" I have the last two, but didn't have the first - just added it... So, does adding the first entry provide an overall emerge.log with just all of the messages in it that I can review? > 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 Like I said, I have a bunch of *individual* logs (for individual ebuilds)... I was hoping for something a little easier to manage/read, all in one file... -- Charles
