From: Saul Wold <sgw@linux.intel.com>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] bitbake: compile tar-replacement firstly
Date: Wed, 29 Aug 2012 15:25:14 -0700 [thread overview]
Message-ID: <503E96CA.5070509@linux.intel.com> (raw)
In-Reply-To: <1344390266-11878-1-git-send-email-rongqing.li@windriver.com>
On 08/07/2012 06:44 PM, rongqing.li@windriver.com wrote:
> From: Roy.Li <rongqing.li@windriver.com>
>
> Compiling tar-replacement or not is decided by version of host tar,
> if the host tar version is lower than 1.23, Compiling tar-replacement
> is needed.
>
> When doing popoluate tar-replacement sysroot to write the tar to
> sysroot, but writing is not finished. other packages probably
> use the being written tar to unzip file, which will lead to failure
> and report the below error:
> "bitbake_build/tmp/sysroots/x86_64-linux/usr/bin/tar: Text file busy"
>
> Now we compile tar-replacement firstly to ensure that a being written
> tar command will not be used.
>
> Signed-off-by: Roy.Li <rongqing.li@windriver.com>
> ---
> scripts/bitbake | 7 ++++++-
> 1 files changed, 6 insertions(+), 1 deletions(-)
>
> diff --git a/scripts/bitbake b/scripts/bitbake
> index 09f8a86..79a81ea 100755
> --- a/scripts/bitbake
> +++ b/scripts/bitbake
> @@ -152,7 +152,12 @@ if [ $buildpseudo -gt 0 ]; then
> fi
> done
> done
> - bitbake pseudo-native $TARTARGET $GITTARGET $additionalopts -c populate_sysroot
> +
> + if [ $needtar = "1" ]; then
> + bitbake $TARTARGET -c populate_sysroot
> + fi
> +
> + bitbake pseudo-native $GITTARGET $additionalopts -c populate_sysroot
> ret=$?
> if [ "$ret" != "0" ]; then
> exit 1
>
Merged into OE-Core
Thanks
Sau!
prev parent reply other threads:[~2012-08-29 22:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-08 1:44 [PATCH] bitbake: compile tar-replacement firstly rongqing.li
2012-08-29 22:25 ` 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=503E96CA.5070509@linux.intel.com \
--to=sgw@linux.intel.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