From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: Martin Jansa <martin.jansa@gmail.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [RFC] bitbake.conf: store cooker logs in TMPDIR subdirectory
Date: Thu, 02 Aug 2012 17:27:38 +0100 [thread overview]
Message-ID: <2026871.yolgERni9t@helios> (raw)
In-Reply-To: <1343924683-21970-1-git-send-email-Martin.Jansa@gmail.com>
On Thursday 02 August 2012 18:24:43 Martin Jansa wrote:
> * we should probably wait until
>
> http://git.openembedded.org/bitbake/commit/?id=1e06d8012868ba5a31503dc99cbf
> 18570be629d9 is in next required bitbake version, but error message if the
> directory doesn't exist is quite clear * people with new enough bitbake
> could just change this in their local.conf
>
> Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
> ---
> meta/conf/bitbake.conf | 2 +-
> 1 files changed, 1 insertions(+), 1 deletions(-)
>
> diff --git a/meta/conf/bitbake.conf b/meta/conf/bitbake.conf
> index d5a43e9..ff1cbd6 100644
> --- a/meta/conf/bitbake.conf
> +++ b/meta/conf/bitbake.conf
> @@ -754,7 +754,7 @@ DISTRO[unexport] = "1"
> TRANSLATED_TARGET_ARCH ??= "${@d.getVar('TARGET_ARCH', True).replace("_",
> "-")}"
>
> # Complete output from bitbake, if you're changing it, make sure to use
> existing directory -BB_CONSOLELOG ?= "${TMPDIR}/cooker.log.${DATETIME}"
> +BB_CONSOLELOG ?= "${TMPDIR}/cooker/${MACHINE}/${DATETIME}"
I was thinking about this the other day - shouldn't we be using LOG_DIR for
this?
Cheers,
Paul
--
Paul Eggleton
Intel Open Source Technology Centre
next prev parent reply other threads:[~2012-08-02 16:39 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-02 16:24 [RFC] bitbake.conf: store cooker logs in TMPDIR subdirectory Martin Jansa
2012-08-02 16:27 ` Paul Eggleton [this message]
2012-08-02 16:30 ` Martin Jansa
2012-08-02 16:31 ` [RFCv2] " Martin Jansa
2012-08-02 16:35 ` Chris Larson
2012-08-02 16:45 ` [RFCv3] bitbake.conf: store cooker logs in subdirectory of LOG_DIR Martin Jansa
2012-08-16 17:49 ` Saul Wold
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=2026871.yolgERni9t@helios \
--to=paul.eggleton@linux.intel.com \
--cc=martin.jansa@gmail.com \
--cc=openembedded-core@lists.openembedded.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox