From: Saul Wold <sgw@linux.intel.com>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Cc: Paul Eggleton <paul.eggleton@linux.intel.com>
Subject: Re: [PATCH] conf/bitbake.conf: fix reparsing after -p is used
Date: Fri, 22 Jun 2012 10:49:16 -0700 [thread overview]
Message-ID: <4FE4B01C.9000708@linux.intel.com> (raw)
In-Reply-To: <1340042156-25187-1-git-send-email-paul.eggleton@linux.intel.com>
On 06/18/2012 10:55 AM, Paul Eggleton wrote:
> The bitbake wrapper script is set up such that the -p (--parse-only)
> command line option is not executed under pseudo, and it sets the
> PSEUDO_BUILD variable to indicate whether or not pseudo is being used.
> Since PSEUDO_BUILD is allowed through into the environment via
> BB_ENV_EXTRAWHITE it influences the data hash and thus if you run
> "bitbake -p" and then run bitbake again to actually build something, the
> change to PSEUDO_BUILD causes the cache from the -p execution not to be
> used. This is fixed simply by adding PSEUDO_BUILD to
> BB_HASHCONFIG_WHITELIST in bitbake.conf so that it doesn't influence the
> data hash.
>
> Fixes [YOCTO #2600].
>
> Signed-off-by: Paul Eggleton<paul.eggleton@linux.intel.com>
> ---
> meta/conf/bitbake.conf | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/meta/conf/bitbake.conf b/meta/conf/bitbake.conf
> index 97930a7..12598f4 100644
> --- a/meta/conf/bitbake.conf
> +++ b/meta/conf/bitbake.conf
> @@ -746,7 +746,7 @@ BB_CONSOLELOG ?= "${TMPDIR}/cooker.log.${DATETIME}"
> # Setup our default hash policy
> BB_SIGNATURE_HANDLER ?= "OEBasic"
> BB_HASHBASE_WHITELIST ?= "TMPDIR FILE PATH PWD BB_TASKHASH BBPATH DL_DIR SSTATE_DIR THISDIR FILESEXTRAPATHS FILE_DIRNAME HOME LOGNAME SHELL TERM USER FILESPATH STAGING_DIR_HOST STAGING_DIR_TARGET COREBASE PRSERV_HOST PRSERV_PORT PRSERV_DUMPDIR PRSERV_DUMPFILE PRSERV_LOCKDOWN PARALLEL_MAKE CCACHE_DIR EXTERNAL_TOOLCHAIN CCACHE"
> -BB_HASHCONFIG_WHITELIST ?= "${BB_HASHBASE_WHITELIST} DATE TIME SESSION_MANAGER DBUS_SESSION_BUS_ADDRESS SSH_AGENT_PID XDG_SESSION_COOKIE SSH_AUTH_SOCK XAUTHORITY"
> +BB_HASHCONFIG_WHITELIST ?= "${BB_HASHBASE_WHITELIST} DATE TIME SESSION_MANAGER DBUS_SESSION_BUS_ADDRESS SSH_AGENT_PID XDG_SESSION_COOKIE SSH_AUTH_SOCK XAUTHORITY PSEUDO_BUILD"
> BB_SIGNATURE_EXCLUDE_FLAGS ?= "doc defaultval _append _prepend deps depends lockfiles type vardepsexclude \
> vardeps vardepvalue file-checksums python func task export unexport noexec \
> nostamp dirs cleandirs sstate-lockfile-shared prefuncs postfuncs export_func \
Merged into OE-Core
Thanks
Sau!
prev parent reply other threads:[~2012-06-22 18:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-18 17:55 [PATCH] conf/bitbake.conf: fix reparsing after -p is used Paul Eggleton
2012-06-22 17:49 ` Saul Wold [this message]
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=4FE4B01C.9000708@linux.intel.com \
--to=sgw@linux.intel.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=paul.eggleton@linux.intel.com \
/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.