FAQ Search Today's Posts Mark Forums Read
» Video Reviews

» Linux Archive

Linux-archive is a website aiming to archive linux email lists and to make them easily accessible for linux users/developers.


» Sponsor

» Partners

» Sponsor

Go Back   Linux Archive > Gentoo > Gentoo User

 
 
LinkBack Thread Tools
 
Old 04-18-2010, 03:38 PM
Tanstaafl
 
Default emerge -e system - output info/errors to log

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 info/warn/errors for each package.

When emerging system, I saw some warnings when emerging openssl, but
they scrolled on by way too fast, and now I can't find them...

???

--

Charles
 
Old 04-18-2010, 03:41 PM
Tanstaafl
 
Default emerge -e system - output info/errors to log

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 single,
> easily readable log of all of the result info/warn/errors for each package.
>
> When emerging system, I saw some warnings when emerging openssl, but
> they scrolled on by way too fast, and now I can't find them...

Oh - and this is a server, so no X, so no elogviewer...
 
Old 04-18-2010, 05:05 PM
Alan McKinnon
 
Default emerge -e system - output info/errors to log

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
 
Old 04-18-2010, 05:37 PM
Tanstaafl
 
Default emerge -e system - output info/errors to log

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
 
Old 04-18-2010, 05:40 PM
Dale
 
Default emerge -e system - output info/errors to log

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 looking for is a single,
easily readable log of all of the result info/warn/errors for each package.

When emerging system, I saw some warnings when emerging openssl, but
they scrolled on by way too fast, and now I can't find them...


Oh - and this is a server, so no X, so no elogviewer...




Hmmm, no GUI. See if you can use this:

elogv

Which comes from here:

root@smoker ~ # equery belongs elogv
* Searching for elogv ...
app-portage/elogv-0.7.4 (/usr/bin/elogv)
root@smoker ~ #

I use that in a console when my GUI is not working for some reason.
Usually because nvidia needs to be recompiled because of a updated kernel.


It's not the prettiest thing but it should work.

Dale

:-) :-)
 
Old 04-18-2010, 05:56 PM
Alan McKinnon
 
Default emerge -e system - output info/errors to log

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 wasn't a minor bugfix update? I'm going from 4.1.2 to 4.3.4.

So what?

Is there an ABI change between 4.1.2 to 4.3.4 that causes apps built with
4.1.2 to break on 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?

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 sequence of commands to do the
upgrade, because most users don't know how to tell the difference. Here's the
logic:

"If we imply that you should merge -e world with a gcc upgrade, my inbox will
not fill with bugs from users who don't know the inner guts of the toolchain".

The Guide is not the best possible guide that can be. It is the guide that
causes the least support questions from users.

> > 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...

When the gcc devs release a new version, they will announce that there is an
ABI break, and what it applies to. It doesn't happen often, but when it does,
the gentoo maintainer ought to put a note in the ebuild.

They are quite diligent about this, much like the KDE/Qt devs do the same
thing when Nokia breaks Qt compatibility.

> >> 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...

I think that's the default. I have it just to be explicit.

>
> 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...

for I in $(ls -1rt /path/to/emerge/logs/*) ; do cat ${I} >> some_log_file ;
done

--
alan dot mckinnon at gmail dot com
 
Old 04-18-2010, 06:05 PM
Neil Bothwick
 
Default emerge -e system - output info/errors to log

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 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 to check or do.


--
Neil Bothwick

Things are more like they are now than they ever were before
 
Old 04-18-2010, 06:10 PM
Neil Bothwick
 
Default emerge -e system - output info/errors to log

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.

PORT_LOGDIR is where full logfiles are saved and predages ELOG*. If it is
not set, full logfiles are not saved at all. /var/log/portage/elog is the
default for elogs if PORT_LOGDIR isn't given.


--
Neil Bothwick

If I want your opinion, I'll ask you to fill out the necessary form.
 
Old 04-28-2010, 05:38 PM
Tanstaafl
 
Default emerge -e system - output info/errors to log

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 sequence of commands to do the
> upgrade, because most users don't know how to tell the difference. Here's the
> logic:
>
> "If we imply that you should merge -e world with a gcc upgrade, my inbox will
> not fill with bugs from users who don't know the inner guts of the toolchain".
>
> The Guide is not the best possible guide that can be. It is the guide that
> causes the least support questions from users.

This is the second time that someone has said something like this with
respect to the official Gentoo Guides (the other was the kernel upgrade
guide, and its recommendation to use 'make menuconfig instead of 'make
oldconfig')...

It would be nice if there were a formal/official place to find 'Advanced
User Guides'...

--

Charles
 
Old 04-28-2010, 05:47 PM
Tanstaafl
 
Default emerge -e system - output info/errors to log

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 to check or do.

Perfect, thanks Neil...

--

Charles
 

Thread Tools




All times are GMT. The time now is 10:05 PM.

VBulletin, Copyright ©2000 - 2014, Jelsoft Enterprises Ltd.
Content Relevant URLs by vBSEO ©2007, Crawlability, Inc.
Copyright 2007 - 2008, www.linux-archive.org