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 1SboV9-0007Rk-5P for garchives@archives.gentoo.org; Tue, 05 Jun 2012 07:48:27 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 335DDE0A5C; Tue, 5 Jun 2012 07:48:11 +0000 (UTC) Received: from smtp.webfaction.com (mail6.webfaction.com [74.55.86.74]) by pigeon.gentoo.org (Postfix) with ESMTP id B1ABDE09E2 for ; Tue, 5 Jun 2012 07:46:24 +0000 (UTC) Received: from localhost (c-24-18-250-30.hsd1.wa.comcast.net [24.18.250.30]) by smtp.webfaction.com (Postfix) with ESMTP id 221CD2105A4E for ; Tue, 5 Jun 2012 02:46:24 -0500 (CDT) Date: Tue, 5 Jun 2012 00:46:00 -0700 From: Bryan Gardiner To: gentoo-user@lists.gentoo.org Subject: Re: [gentoo-user] Portage telling me what it's doing Message-ID: <20120605004600.3fc5c377@khumba.net> In-Reply-To: <4FC9BB84.8030109@gmail.com> References: <4FC9ADE7.4040806@wht.com.au> <4FC9BB84.8030109@gmail.com> X-Mailer: Claws Mail 3.8.0 (GTK+ 2.24.10; x86_64-pc-linux-gnu) 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=US-ASCII Content-Transfer-Encoding: 7bit X-Archives-Salt: e64e85ab-77aa-45c2-b787-ab1a0f7f7228 X-Archives-Hash: 91a11427e772b5bcb1d8c77a22171b58 On Sat, 02 Jun 2012 02:06:44 -0500 Dale wrote: > I use the command: > > genlop -c > > That tells what is compiling and some general time info too. +1 for genlop. Also, if you're upgrading a number of large packages, it can help to have an estimate of how long you'll be compiling: $ emerge -pNuD world | genlop -p Or you can use "emerge --quiet-build=y" if you'd like to hide all the build output and only have Portage display what the currently compiling package(s) are. You can still tail the build logs in /var/tmp/portage/*/*/build.log to watch what's going on. Cheers, Bryan