[OE-core] [PATCH v1] postinst-intercepts: check tool presence in intercept hooks

[richard.purdie at linuxfoundation.org]

On Sun, 2019-06-30 at 12:56 -0400, Sinan Kaya wrote:
> On 6/27/2019 4:46 AM, Alexander Kanavin wrote:
> >     This issue showed up in thud using core-image-minimal. It was
> > not there
> >     on sumo.
> > 
> > 
> > If you can provide steps to reproduce, it could help. Please start
> > with
> > a git checkout of poky thud branch.
> > 
> 
> Issue in only happening on the build machine with docker using ubuntu
> 16.04 as a baseline.
> 
> I'm having hard-time reproducing on my development machine.
> 
> My cursory web search says that I'm not the only one hitting this
> issue
> and people have mysteriously solved this issue.
> 
> https://github.com/riscv/meta-riscv/issues/26
> 
> The following matches what I see on the build machine.
> 
> "/update_pixbuf_cache: 8:
> /home/riscv-yocto/build/tmp-glibc/work/qemuriscv64-oe-linux/core-
> image-full-cmdline/1.0-r0/intercept_scripts-
> 2c03b46bc7941049a88b6c1719c35aade81b0ce5490421e7cca768bf8beb0d01
> 
> /update_pixbuf_cache: cannot create
> /home//riscv-yocto/build/tmp-glibc/work/qemuriscv64-oe-linux/core-
> image-full-cmdline/1.0-r0/rootfs/usr/lib/gdk-pixbuf-
> 2.0/2.10.0/loaders/../loaders.cache:
> Directory nonexistent"

Knowing which branches (sumo vs. thud) and which layers does help put a
different perspective on this issue and helps us help you!

Is this a difference in dash shell vs bash shell (e.g. for /bin/sh) on
these machines? (if I had to guess that is where I'd start)

Cheers,

Richard

>