On Thu, Sep 28, 2017 at 05:13:03PM +0300, Ed Bartosh wrote: > On Wed, Sep 27, 2017 at 01:00:09PM -0400, Tom Rini wrote: > > With RSS we need to ensure that when making a bmap image that the > > python3 that we created is found via /usr/bin/env rather than the host > > python3. Otherwise we're relying on the build host to have bmaptool > > support installed. > > > > Can you suggest how to reproduce the issue you're trying to fix with > this patch? > > Here is what I did: > > 1. Checked if bmaptools are available for host python3: > > $ python3 -c 'import bmaptools' > Traceback (most recent call last): > File "<string>", line 1, in <module> > ImportError: No module named 'bmaptools' > > 2. Added cpio.bmap to my build configuration: > > $ grep ^IMAGE_FSTYPES ./conf/local.conf > IMAGE_FSTYPES = "cpio.bmap" > > 3. Built core-image-minimal: > [build (master)]$ rm -rf tmp/ > [build (master)]$ bitbake core-image-minimal > ... > NOTE: Tasks Summary: Attempted 2395 tasks of which 2186 didn't need to > be rerun and all succeeded. > > 4. Checked if bmap file has been generated: > [build (master)]$ ls ./tmp/deploy/images/qemux86-64/ |grep cpio > core-image-minimal-qemux86-64-20170928135949.rootfs.cpio.bmap > core-image-minimal-qemux86-64.cpio.bmap > > Hm, cpio image got removed for some reason. Looks like a bug, but not > related to bmaptool. (I remember you're fixing that code some time ago). > > Should I use another MACHINE or anything else that can trigger build > failure? > > PS. I used latest poky master. commit id: > fcdfe09d9cc4e2977bd602dfd18f729cd9f6d73d
I'm on oe-core only, abf2e9526a11bcb51b71b90a7b76bd33af656494 and just replicated the problem again. I'm doing ext4.bmap, but that shouldn't matter. -- Tom
signature.asc
Description: Digital signature
-- _______________________________________________ Openembedded-core mailing list Openembedded-core@lists.openembedded.org http://lists.openembedded.org/mailman/listinfo/openembedded-core
