<div dir="ltr"><div class="gmail_extra"><br><div class="gmail_quote">On 22 September 2015 at 09:10, Richard Purdie <span dir="ltr"><<a href="mailto:richard.purdie@linuxfoundation.org" target="_blank">richard.purdie@linuxfoundation.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div id=":14z" class="a3s" style="overflow:hidden">The longer stack trace is actually really helpful. I believe the code<br>
here should inherit the working directory of the current task rather<br>
than rely on the default of ${B} which bitbake assigns if there is<br>
nothing else.<br>
<br>
The trouble is that if the function does specify a dirs flag, it should<br>
really use that instead of a supplied parameter and if we use the<br>
parameter to exec_func(), it won't do that.<br>
<br>
There aren't that many uses of SSTATEPOSTINSTFUNCS in our metadata so<br>
the easiest way to fix this short term is probably to go through them<br>
and add specific [dirs] options to the functions.</div></blockquote></div><br>There's enough instances of SSTATEPOSTINSTFUNCS dotted around even just oe-core, but they're all going to be using SSTATE_INSTDIR as the working directory. Whilst you have a valid point that the functions should respect [dirs] if set, for the case of sstate post-install hooks I think we should just force the right path so the recipe creators don't have to worry about this.</div><div class="gmail_extra"><br></div><div class="gmail_extra">Ross</div></div>