public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Dale <rdalek1967@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] emerge -e system - output info/errors to log
Date: Sun, 18 Apr 2010 12:40:22 -0500	[thread overview]
Message-ID: <4BCB4406.3020907@gmail.com> (raw)
In-Reply-To: <4BCB282E.6090808@libertytrek.org>

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

:-)  :-)



  reply	other threads:[~2010-04-18 17:40 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-18 15:38 [gentoo-user] emerge -e system - output info/errors to log Tanstaafl
2010-04-18 15:41 ` Tanstaafl
2010-04-18 17:40   ` Dale [this message]
2010-04-18 17:05 ` Alan McKinnon
2010-04-18 17:37   ` Tanstaafl
2010-04-18 17:56     ` Alan McKinnon
2010-04-18 18:10       ` Neil Bothwick
2010-04-28 17:38       ` Tanstaafl
2010-04-28 21:02         ` Dale
2010-04-18 18:05     ` Neil Bothwick
2010-04-28 17:47       ` Tanstaafl
2010-05-06 13:04       ` Tanstaafl

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4BCB4406.3020907@gmail.com \
    --to=rdalek1967@gmail.com \
    --cc=gentoo-user@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox