From: Richard Purdie <martin.jansa@gmail.com>
To: Martin Jansa <martin.jansa@gmail.com>
Subject: Re: PERLVERSION sometimes changing sstate signature
Date: Wed, 27 Nov 2013 08:58:33 +0000 [thread overview]
Message-ID: <1385542713.11246.21.camel@ted> (raw)
In-Reply-To: <20131127011949.GN2870@jama>
On Wed, 2013-11-27 at 02:19 +0100, Martin Jansa wrote:
> Sometimes it's shown in
> bitbake -S perf (or any other perl using recipes)
>
> NOTE: Reparsing files to collect dependency data
> ERROR: Bitbake's cached basehash does not match the one we just generated
> (/OE/oe-core/meta/recipes-kernel/perf/perf.bb.do_package)!
> ERROR: The mismatched hashes were 074153b639c930f9f3e06170745e2587 and e5b25a12742221b725812945ccd5abfb
> NOTE: Tasks Summary: Attempted 0 tasks of which 0 didn't need to be rerun and all succeeded.
>
> bitbake-diffsigs between such .sigdata files (not exactly the above) shows:
> basehash changed from 992e4ad775701625d03e5ba8b20a016f to 9b5d76a5e33f2d53c20d89923bc553f7
> Variable PERLVERSION value changed from 'None' to '5.14.3'
>
> PERLVERSION is from cpan
> meta/classes/cpan-base.bbclass:PERLVERSION := "${@get_perl_version(d)}"
>
> # Determine the staged version of perl from the perl configuration file
> def get_perl_version(d):
> import re
> cfg = d.expand('${STAGING_LIBDIR}${PERL_OWN_DIR}/perl/config.sh')
> try:
> f = open(cfg, 'r')
> except IOError:
> return None
> l = f.readlines();
> f.close();
> r = re.compile("^version='(\d*\.\d*\.\d*)'")
> for s in l:
> m = r.match(s)
> if m:
> return m.group(1)
> return None
>
> So it looks understandable that bitbake -S executed without populated
> sysroot (only pseudo-native) sees PERLVERSION None, while parsing
> PERLVERSION with sysroot populated returns right version.
>
> What's the proper fix for this?
Probably to give it a specific value for signature purposes e.g.:
get_perl_version[vardepvalue] = "${STAGING_LIBDIR}${PERL_OWN_DIR}"
Cheers,
Richard
parent reply other threads:[~2013-11-29 22:04 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20131127011949.GN2870@jama>]
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=1385542713.11246.21.camel@ted \
--to=martin.jansa@gmail.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.