From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Robert Yang <liezhi.yang@windriver.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 1/1] sstate.bbclass: remove previous version's stamp
Date: Fri, 17 Jan 2014 10:36:18 +0000 [thread overview]
Message-ID: <1389954978.14987.106.camel@ted> (raw)
In-Reply-To: <981567c4dfef59be08373f124b36739449a546a1.1389940146.git.liezhi.yang@windriver.com>
On Fri, 2014-01-17 at 14:43 +0800, Robert Yang wrote:
> There is a potential problem if we don't remove the previous version's
> stamp, for example:
>
> The depend chain is:
> libtool-native -> autoconf-native -> m4-native
> We have two m4-native: 1.4.9 and 1.4.7
>
> 1) Clean all of them to make a fresh build so that we can reproduce the
> problem
> $ bitbake m4-native autoconf-native libtool-native -ccleansstate
>
> 2) Build libtool-native so that the m4-native_1.4.17 will be built
> $ bitbake libtool-native
>
> 3) Set PREFERRED_VERSION_m4-native = "1.4.9" and build again
> $ bitbake libtool-native
>
> 4) Set PREFERRED_VERSION_m4-native = "1.4.17" and build again
> $ bitbake libtool-native -ccleansstate && bitbake libtool-native
>
> Then the build will fail:
> [snip]
> | m4: unrecognized option '--gnu'
> | Try `m4 --help' for more information.
> | autom4te: m4 failed with exit status: 1
> [snip]
>
> The is because when we change m4-native to 1.4.17 and build
> libtool-native again:
> 5) libtool-native depends on autoconf-native, and autoconf-native's
> version isn't change, so it can remove the current stamp and mirror
> the sstate (the one depends on m4-native_1.4.9) from the SSTATE_DIR
> correctly.
>
> 6) The mirrored autoconf-native depends on m4-native_1.4.17's
> do_populate_sysroot, and the stamp is already there (which is made
> by step 2), so it would do nothing, but this is incorrect, since
> the one that really in the sysroot is m4-native_1.4.9, then the
> error happens.
>
> Remove previous version's stamp in sstate_clean() will fix the problem.
>
> [YOCTO #5422]
>
> Signed-off-by: Robert Yang <liezhi.yang@windriver.com>
> ---
> meta/classes/sstate.bbclass | 22 +++++++++++++---------
> 1 file changed, 13 insertions(+), 9 deletions(-)
>
> diff --git a/meta/classes/sstate.bbclass b/meta/classes/sstate.bbclass
> index 35c3f85..bad8b78 100644
> --- a/meta/classes/sstate.bbclass
> +++ b/meta/classes/sstate.bbclass
> @@ -331,11 +331,18 @@ def sstate_clean_manifest(manifest, d):
>
> def sstate_clean(ss, d):
> import oe.path
> + import glob
> + import re
>
> d2 = d.createCopy()
> + stamp_clean = d.getVar("STAMPCLEAN", True)
> extrainf = d.getVarFlag("do_" + ss['task'], 'stamp-extra-info', True)
> if extrainf:
> d2.setVar("SSTATE_MANMACH", extrainf)
> + wildcard_stfile = "%s.do_%s*.%s" % (stamp_clean, ss['task'], extrainf)
> + else:
> + wildcard_stfile = "%s.do_%s*" % (stamp_clean, ss['task'])
> +
> manifest = d2.expand("${SSTATE_MANFILEPREFIX}.%s" % ss['name'])
>
> if os.path.exists(manifest):
> @@ -350,15 +357,12 @@ def sstate_clean(ss, d):
> for lock in locks:
> bb.utils.unlockfile(lock)
>
> - stfile = d.getVar("STAMP", True) + ".do_" + ss['task']
> - oe.path.remove(stfile)
> - oe.path.remove(stfile + "_setscene")
> - if extrainf:
> - oe.path.remove(stfile + ".*" + extrainf)
> - oe.path.remove(stfile + "_setscene" + ".*" + extrainf)
> - else:
> - oe.path.remove(stfile + ".*")
> - oe.path.remove(stfile + "_setscene" + ".*")
> + # Remove the current and previous stamps, but keep the sigdata
> + re_sigdata = ".*\.do_%s\.sigdata\." % ss['task']
> + for stfile in glob.glob(wildcard_stfile):
> + # Keep the sigdata
> + if not re.match(re_sigdata, stfile):
> + oe.path.remove(stfile)
I'm not sure its worth the overhead of using regexps here. Can we not do
something simple like:
if ".sigdata." not in stfile:
Cheers,
Richard
next prev parent reply other threads:[~2014-01-17 10:36 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-17 6:43 [PATCH 0/1 V2] sstate.bbclass: remove previous version's stamp Robert Yang
2014-01-17 6:43 ` [PATCH 1/1] " Robert Yang
2014-01-17 10:36 ` Richard Purdie [this message]
2014-01-17 11:01 ` Robert Yang
2014-01-17 12:17 ` Richard Purdie
2014-01-20 9:28 ` Robert Yang
-- strict thread matches above, loose matches on Subject: below --
2014-01-20 11:42 [PATCH 0/1 V3] " Robert Yang
2014-01-20 11:42 ` [PATCH 1/1] " Robert Yang
2014-01-15 7:09 [PATCH 0/1] " Robert Yang
2014-01-15 7:09 ` [PATCH 1/1] " Robert Yang
2014-01-15 9:40 ` Richard Purdie
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=1389954978.14987.106.camel@ted \
--to=richard.purdie@linuxfoundation.org \
--cc=liezhi.yang@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