From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga09.intel.com (mga09.intel.com [134.134.136.24]) by yocto-www.yoctoproject.org (Postfix) with ESMTP id 9AB7DE0059F for ; Thu, 17 Nov 2011 13:40:40 -0800 (PST) Received: from orsmga002.jf.intel.com ([10.7.209.21]) by orsmga102.jf.intel.com with ESMTP; 17 Nov 2011 13:40:40 -0800 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="4.67,351,1309762800"; d="scan'208";a="76917412" Received: from amabrams-mobl.amr.corp.intel.com (HELO envy.home) ([10.7.199.53]) by orsmga002.jf.intel.com with ESMTP; 17 Nov 2011 13:40:40 -0800 Message-ID: <4EC57F58.7020301@linux.intel.com> Date: Thu, 17 Nov 2011 13:40:40 -0800 From: Darren Hart User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:7.0) Gecko/20110927 Thunderbird/7.0 MIME-Version: 1.0 To: Joshua Lock References: <4EB1E5F1.3050106@linux.intel.com> <4EB222D0.6050301@linux.intel.com> <4EB224EB.4040804@linux.intel.com> <4EB26098.20204@communistcode.co.uk> <4EB2E1D1.5030505@linux.intel.com> In-Reply-To: <4EB2E1D1.5030505@linux.intel.com> X-Enigmail-Version: 1.3.3 Cc: yocto@yoctoproject.org Subject: Re: Help diagnosing a build failure involving ncurses, gettext, and eglibc X-BeenThere: yocto@yoctoproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Discussion of all things Yocto List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 17 Nov 2011 21:40:40 -0000 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit On 11/03/2011 11:47 AM, Joshua Lock wrote: > On 03/11/11 02:36, Jack Mitchell wrote: >> On 03/11/2011 05:21, Darren Hart wrote: >>> >>> On 11/02/2011 10:16 PM, McClintock Matthew-B29882 wrote: >>>> On Thu, Nov 3, 2011 at 12:12 AM, Darren Hart >>>> wrote: >>>>> I came up with the following to ensure I have a log of every bitbake >>>>> command I run along with some useful stats. Feel free to use it or >>>>> flame it: >>>>> >>>>> >>>>> #!/bin/bash >>>>> TIMESTAMP=$(date -u "+%Y%m%d%H%M%S") >>>>> LOG=$(mktemp --suffix=".log" bb-$TIMESTAMP-XXX) >>>>> if [ -z "$LOG" ]; then >>>>> echo "ERROR: failed to create log file" >>>>> exit 1 >>>>> fi >>>>> >>>>> ( >>>>> echo "Start: $TIMESTAMP" >>>>> echo "========================================" >>>>> /usr/bin/time 2>&1 -v bitbake $@ >>>>> echo "========================================" >>>>> echo "End: $(date -u '+%Y%m%d%H%M%S')" >>>>> ) | tee $LOG >>>>> >>>>> echo "Logfile: $LOG" >>>> It would be nice if we had this as a selectable option in the bitbake >>>> wrapper somehow and it saved off logs to tmp/bitbake/logs/ or >>>> something appropriate. >>> I was having similar thoughts just after having pressed send :) >>> >>> Given how annoying it is to not have the log when you forget to capture >>> it, I think this might actually make a reasonable default. The important >>> bits are of course already recorded in >>> tmp/blah/blah/blah/temp/log.blah.PID... but the above serves almost like >>> an index into the individual files. I'm all for logging it by default - >>> as well as collecting summary stats. I don't know if the above is the >>> best way to go about it - but a functional equivalent would be nice. >>> >>> For all I know something like this already exists and I just haven't >>> stumbled upon it yet. >>> >> >> I agree, something which actually logs what you are doing and how it was >> done rather than just the output/error logging we have at the moment >> would be a great addition. It would make it much easier to track errors >> and help pin down bugs - especially if you have taken a long winded >> route to get to a particular point. > > Sounds like people would find this feature useful, can someone please > file a bug report? > http://bugzilla.yoctoproject.org/show_bug.cgi?id=1771 -- Darren Hart Intel Open Source Technology Center Yocto Project - Linux Kernel