Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Rongqing Li <rongqing.li@windriver.com>
To: Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>,
	"Yang, Liezhi" <Liezhi.Yang@windriver.com>,
	"Hatle, Mark" <mark.hatle@windriver.com>
Subject: Could we build tar-replacement firstly and not parallel if tar-replacement is needed to build
Date: Mon, 6 Aug 2012 20:50:14 +0800	[thread overview]
Message-ID: <501FBD86.3090705@windriver.com> (raw)

Hi:

Building failed several times when building tar-replacement-native is 
needed,
The error log shows 
"bitbake_build/tmp/sysroots/x86_64-linux/usr/bin/tar: Text
file busy". this log proves "an attempt was made to execute a 
pure-procedure
program that is currently open for writing."


Before this error, tar-replacement do_populate_sysroot just starts,
(tar-replacement-native-1.26-r2: task do_populate_sysroot: Started)
After this error, we see tar-replacement do_populate_sysroot just
finish.

So I think the root cause is that do_populate_sysroot sqlite is using
a tar command which being opened to written. in fact, all packages
need tar to do_popolate_sysroot()

I see building tar-replacement-native is started in bitbake file,
could we build tar-replacement firstly, not parallel if needed.



diff --git a/scripts/bitbake b/scripts/bitbake
index 3772d82..1bb8fed 100755
--- a/scripts/bitbake
+++ b/scripts/bitbake
@@ -134,7 +134,10 @@ if [ $buildpseudo -gt 0 ]; then
              fi
          done
      done
-    bitbake pseudo-native $TARTARGET $additionalopts -c populate_sysroot
+
+    if [ $needptar = "1" ]; then
+       sed -i 's/BB_NUMBER_THREADS =/#BB_NUMBER_THREADS =/g' 
conf/local.conf
+       bitbake $TARTARGET
+       sed -i 's/#BB_NUMBER_THREADS =/BB_NUMBER_THREADS =/g' 
conf/local.conf
+    fi
+
+    bitbake pseudo-native $additionalopts -c populate_sysroot
      ret=$?
      if [ "$ret" != "0" ]; then
          exit 1


since building tar-replacement or not depends on host tar version, it is
hard to add a tar dependence to any package, and I did not have a good way
to fix this bug except the upper.

Any advice and suggestion are welcome


-- 
Best Reagrds,
Roy | RongQing Li




             reply	other threads:[~2012-08-06 13:01 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-06 12:50 Rongqing Li [this message]
2012-08-07  5:59 ` Could we build tar-replacement firstly and not parallel if tar-replacement is needed to build Rongqing Li
2012-08-07  7:41   ` Richard Purdie
2012-08-07  8:02     ` Rongqing Li
2012-08-07  8:57       ` Pascal Ouyang
2012-08-07  9:27         ` Rongqing Li
2012-08-07  9:03       ` Richard Purdie
2012-08-07  9:25         ` Rongqing Li

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=501FBD86.3090705@windriver.com \
    --to=rongqing.li@windriver.com \
    --cc=Liezhi.Yang@windriver.com \
    --cc=mark.hatle@windriver.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