<div dir="ltr"><div class="gmail_extra"><br><div class="gmail_quote">On 20 January 2017 at 13:29, Maxin B. John <span dir="ltr"><<a href="mailto:maxin.john@intel.com" target="_blank">maxin.john@intel.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">> The issue here is that in a multilib build the ${base_libdir} is resolving to /lib64 which completely breaks some tools that fully expect /lib/modules to be a fixed location regardless if the target is 32/64 or something else.<br>
><br>
<br>
</span>I would expect the kernel to be ok with this change if we provide the kernel command<br>
line parameter: "firmware_class.path=${base_<wbr>libdir}" or similar.<br></blockquote></div><br>I believe that using nonarch_base_libdir is the proper fix here, we need to understand why this didn't just work.</div><div class="gmail_extra"><br></div><div class="gmail_extra">Ross</div></div>