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 1O3YnR-0006kC-3H for garchives@archives.gentoo.org; Sun, 18 Apr 2010 18:00:41 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 346B5E0B7D; Sun, 18 Apr 2010 18:00:06 +0000 (UTC) Received: from mail-ww0-f53.google.com (mail-ww0-f53.google.com [74.125.82.53]) by pigeon.gentoo.org (Postfix) with ESMTP id E7CA8E0B7D for ; Sun, 18 Apr 2010 18:00:05 +0000 (UTC) Received: by wwg30 with SMTP id 30so22746wwg.40 for ; Sun, 18 Apr 2010 11:00:05 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:from:to:subject:date :user-agent:cc:references:in-reply-to:mime-version:content-type :content-transfer-encoding:message-id; bh=tHmDRj/zFLCcjnYkvxNRdYdVkFxdpsZib8ewDB80x/Q=; b=KP5DxluAdD1cSKw3DAx06Xpt0yVEJyxO5PpGjHELQZPelP6IQ2dGgZvcvwPcUhqnRW YoycoEhAo0fhaengWH9vqzEBt3XP5OfOrIk8nwxRiLkZfBjwistc4IfnUUrf3vO77W6/ PeKYCfFAkVil0mpwfeJfp1oeDCu+/wMO12GGY= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=from:to:subject:date:user-agent:cc:references:in-reply-to :mime-version:content-type:content-transfer-encoding:message-id; b=qKAA0XKLnWlTMLZPtcGrUVqNdzGPaWdR+7+J6k8yF7m6lHOHcTseZf2wTFQgR9bwd9 +EcIs7ASRblktJQgsxFnov09qcKiQowLjhXsjPA+YhaUk7hfjfWy86kV7qabiHvfeMg0 WH+bidTn+1ffaqMkXsyxW0Ag6IiqVKDwT8n8c= Received: by 10.216.163.67 with SMTP id z45mr305360wek.26.1271613605365; Sun, 18 Apr 2010 11:00:05 -0700 (PDT) Received: from nazgul.localnet (196-210-153-185-rrdg-esr-2.dynamic.isadsl.co.za [196.210.153.185]) by mx.google.com with ESMTPS id z3sm41289750wbs.10.2010.04.18.11.00.03 (version=TLSv1/SSLv3 cipher=RC4-MD5); Sun, 18 Apr 2010 11:00:04 -0700 (PDT) From: Alan McKinnon To: gentoo-user@lists.gentoo.org Subject: Re: [gentoo-user] emerge -e system - output info/errors to log Date: Sun, 18 Apr 2010 19:56:46 +0200 User-Agent: KMail/1.13.2 (Linux/2.6.33-zen1; KDE/4.4.2; x86_64; ; ) Cc: Tanstaafl References: <4BCB276B.30306@libertytrek.org> <201004181905.17893.alan.mckinnon@gmail.com> <4BCB4364.1000402@libertytrek.org> In-Reply-To: <4BCB4364.1000402@libertytrek.org> 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 Content-Type: Text/Plain; charset="utf-8" Content-Transfer-Encoding: 7bit Message-Id: <201004181956.46928.alan.mckinnon@gmail.com> X-Archives-Salt: 59d61492-0b27-4d34-aeae-ff5498014fa4 X-Archives-Hash: fb56aacd4cb0846254b50cbede5d1b56 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