<div dir="ltr"><div class="gmail_extra">On 27 July 2016 at 06:52, Chen Qi <span dir="ltr"><<a href="mailto:Qi.Chen@windriver.com" target="_blank">Qi.Chen@windriver.com</a>></span> wrote:<br><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div id=":4az" class="a3s aXjCH m1562ae92f8ccc7fc">Fix this problem by hardcoding '/usr/bin/env'.<br>
<br>
Usually, we don't like hardcoding. But as far as I can see, /usr/bin/env is<br>
a little special. We skip the 'file-rdeps' QA checking for '/usr/bin/env'<br>
dependency. Besides, scripts in many packages do use '/usr/bin/env'. So we<br>
should assume it's there in our system.<br></div></blockquote></div><br>I think we should be replacing with ${bindir} for target binaries (so the right paths are used, no matter what bindir is set to) and hard-coding /usr/bin for native and nativesdk.</div><div class="gmail_extra"><br></div><div class="gmail_extra">If the sanity test is hardcoding /usr/bin/env then that likely should change to respect ${bindir} too.</div><div class="gmail_extra"><br></div><div class="gmail_extra">Ross</div></div>