From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from pigeon.gentoo.org ([208.92.234.80] helo=lists.gentoo.org) by finch.gentoo.org with esmtp (Exim 4.60) (envelope-from ) id 1O3YRR-00042Z-7z for garchives@archives.gentoo.org; Sun, 18 Apr 2010 17:37:59 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 384A8E0B93; Sun, 18 Apr 2010 17:37:42 +0000 (UTC) Received: from blingymail-a1.g.dreamhost.com (caibbdcaaaaf.dreamhost.com [208.113.200.5]) by pigeon.gentoo.org (Postfix) with ESMTP id 1BC0FE0B93 for ; Sun, 18 Apr 2010 17:37:42 +0000 (UTC) Received: from [192.168.1.110] (smtp.media-brokers.com [70.43.81.99]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by blingymail-a1.g.dreamhost.com (Postfix) with ESMTP id 898175C819 for ; Sun, 18 Apr 2010 10:37:41 -0700 (PDT) Message-ID: <4BCB4364.1000402@libertytrek.org> Date: Sun, 18 Apr 2010 13:37:40 -0400 From: Tanstaafl User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.19) Gecko/20081209 Lightning/0.9 Thunderbird/2.0.0.19 Mnenhy/0.7.6.666 Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org MIME-Version: 1.0 To: gentoo-user@lists.gentoo.org Subject: Re: [gentoo-user] emerge -e system - output info/errors to log References: <4BCB276B.30306@libertytrek.org> <201004181905.17893.alan.mckinnon@gmail.com> In-Reply-To: <201004181905.17893.alan.mckinnon@gmail.com> X-Enigmail-Version: 1.0.1 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Archives-Salt: 4737a690-6439-4106-b509-19c1ad3b574b X-Archives-Hash: 90824cacd33298e17903a4659280f8d4 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