From: Darren Hart <dvhart@linux.intel.com>
To: Yocto Project <yocto@yoctoproject.org>
Subject: Re: Help diagnosing a build failure involving ncurses, gettext, and eglibc
Date: Wed, 02 Nov 2011 22:12:48 -0700 [thread overview]
Message-ID: <4EB222D0.6050301@linux.intel.com> (raw)
In-Reply-To: <4EB1E5F1.3050106@linux.intel.com>
On 11/02/2011 05:53 PM, Darren Hart wrote:
...
> I tried to capture my complete log, but screen froze on me while trying
> to paste the buffer into a log :( So besides writing a bitbake wrapper
> to ensure I record ALL my bitbake sessions for reference,
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"
--
Darren Hart
Intel Open Source Technology Center
Yocto Project - Linux Kernel
next prev parent reply other threads:[~2011-11-03 5:12 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-03 0:53 Help diagnosing a build failure involving ncurses, gettext, and eglibc Darren Hart
2011-11-03 5:12 ` Darren Hart [this message]
2011-11-03 5:16 ` McClintock Matthew-B29882
2011-11-03 5:21 ` Darren Hart
2011-11-03 9:36 ` Jack Mitchell
2011-11-03 18:47 ` Joshua Lock
2011-11-17 21:40 ` Darren Hart
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=4EB222D0.6050301@linux.intel.com \
--to=dvhart@linux.intel.com \
--cc=yocto@yoctoproject.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.