Re: package_ipk.bbclass fails due to a wrong version of a package

[Denys Dmytriyenko <denis@denix.org>]

On Thu, Apr 02, 2009 at 12:11:18PM -0700, Tom Rini wrote:
> On Thu, Apr 02, 2009 at 02:50:06PM -0400, Denys Dmytriyenko wrote:
> 
> > Hi,
> > 
> > I've been debugging this issue for a while now w/o much success.
> > 
> > We have following recipes in play:
> > curl_7.19.0.bb
> > curl-native_7.18.2.bb
> > curl-sdk_7.18.2.bb
> > 
> > None of those set PV explicitly, so they are picked up from the filename.
> 
> Hmm, if you throw in a -v -DDD and log all the output, do you see both
> curl_7.18.2.bb being loaded (for -sdk) and curl_7.19.0.bb (for target)
> being loaded up?

Nope. While trying to build curl-sdk_7.18.2.bb there is no mentioning of 
7.19.0 (grepped the output) until the do_package_write_ipk, where it tried to 
create a lock file, as I mentioned above:

NOTE: package curl-sdk-7.18.2-r0: task do_package_write_ipk: started
DEBUG: mkdirhier(/oe/tmp/work/i686-i686-sdk-angstrom-linux/curl-sdk-7.18.2-r0/image)
DEBUG: mkdirhier(/oe/tmp/work/i686-i686-sdk-angstrom-linux/curl-7.19.0-r1/image)
ERROR: Error, lockfile path does not exist!: /oe/tmp/work/i686-i686-sdk-angstrom-linux/curl-7.19.0-r1/install

The second mkdirhier() is where it fails and it is called from lockfile(), 
which gets called from do_package_ipk()...

BTW, this was a i686-generic build, thus i686-i686-sdk path...

-- 
Denys