<div dir="ltr">On 11 December 2017 at 13:57, Stefan Agner <span dir="ltr"><<a href="mailto:stefan@agner.ch" target="_blank">stefan@agner.ch</a>></span> wrote:<br><div class="gmail_extra"><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">From: Stefan Agner <<a href="mailto:stefan.agner@toradex.com">stefan.agner@toradex.com</a>><br>
<br>
On some build hosts distros (e.g. Fedora 26) waf tries to be<br>
smart about libdir detection and defaults to [EXEC_PREFIX/lib64].<br>
This obviously is not what we want for 32-bit targets and usually<br>
fails in the do_package phase:<br>
WARNING: gstreamer1.0-plugins-imx-0.13.<wbr>0-r0 do_package: QA Issue: gstreamer1.0-plugins-imx: Files/directories were installed but not shipped in any package:<br>
/usr/lib64/libgstimxcommon.so.<wbr>0<br>
<br>
Explicitly pass libdir to waf reliably resolves the issue.<br></blockquote><div><br></div><div>What happens if the wscript doesn't recognise --libdir, does it silently ignore it or throw an error?</div><div><br></div><div>If waf supports prefix and libdir and doesn't error on unknown options, does it also support datadir/sysconfdir and so on? We should pass as much as possible. The gnu_dirs module suggests yes, so you could copy what autotools passes.</div><div><br></div><div>Ross </div></div></div></div>