On 2010-04-18 2:05 PM, Neil Bothwick wrote:
On Sun, 18 Apr 2010 13:37:40 -0400, Tanstaafl wrote:
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...
My preferred approach is to add mail to
On 2010-04-18 1:56 PM, Alan McKinnon wrote:
Understand what the gcc upgrade guide is:
a quick simple guide for user who don't know tool chains inside out, that
give
the minimal sequence of commands that is GUARANTEED to NOT leave the user in
the lurch. It's not the minimum possible
On 2010-04-18 2:05 PM, Neil Bothwick wrote:
My preferred approach is to add mail to PORTAGE_ELOG_SYSTEM to get
each elog message mailed to me. That's still separate message, but I
think that's better as I can mark each one read as I've actioned it,
leaving me with a clear list of what's left
Tanstaafl wrote:
On 2010-04-18 1:56 PM, Alan McKinnon wrote:
Understand what the gcc upgrade guide is:
a quick simple guide for user who don't know tool chains inside out, that give
the minimal sequence of commands that is GUARANTEED to NOT leave the user in
the lurch. It's not the minimum
I must be missing something obvious...
When updating gcc, and thus emerging -e both system and world, 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
On 2010-04-18 11:38 AM, Tanstaafl wrote:
I must be missing something obvious...
When updating gcc, and thus emerging -e both system and world, 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
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
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.
Tanstaafl wrote:
On 2010-04-18 11:38 AM, Tanstaafl wrote:
I must be missing something obvious...
When updating gcc, and thus emerging -e both system and world, 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
On Sunday 18 April 2010 19:37:40 Tanstaafl wrote:
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
On Sun, 18 Apr 2010 13:37:40 -0400, Tanstaafl wrote:
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...
My preferred approach is to add mail to PORTAGE_ELOG_SYSTEM to get each
elog message
On Sun, 18 Apr 2010 19:56:46 +0200, Alan McKinnon wrote:
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...
I think that's the default. I have it just to be explicit.
12 matches
Mail list logo
