On 20 January 2017 at 13:29, Maxin B. John <maxin.j...@intel.com> wrote:

> > 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.
> >
>
> I would expect the kernel to be ok with this change if we provide the
> kernel command
> line parameter: "firmware_class.path=${base_libdir}" or similar.
>

I believe that using nonarch_base_libdir is the proper fix here, we need to
understand why this didn't just work.

Ross
-- 
_______________________________________________
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

Reply via email to