Re: [OE-core] [PATCH 2/2] Revert "kernel: Modify kernel modules installation path."

2017-02-02 Thread Amarnath Valluri
Hi, I am very sorry, i couldn't respond earlier than this, somehow i missed this thread :( The motivation of these patches was achieving merged '/usr' in oe-core, which demands no package installs anything into root(/bin, /sbin, /lib) folders, and i see no exception for kernel

Re: [OE-core] [PATCH 2/2] Revert "kernel: Modify kernel modules installation path."

2017-01-20 Thread Jason Wessel
On 01/20/2017 07:52 AM, Burton, Ross wrote: On 20 January 2017 at 13:48, Jason Wessel > wrote: WARNING: linux-yocto-4.8.12+gitAUTOINC+3edb4de355_9bcb4ea3fa-r0 do_package: QA Issue: linux-yocto: Files/directories were

Re: [OE-core] [PATCH 2/2] Revert "kernel: Modify kernel modules installation path."

2017-01-20 Thread Burton, Ross
On 20 January 2017 at 13:48, Jason Wessel wrote: > WARNING: linux-yocto-4.8.12+gitAUTOINC+3edb4de355_9bcb4ea3fa-r0 > do_package: QA Issue: linux-yocto: Files/directories were installed but not > shipped in any package: > /lib64 >

Re: [OE-core] [PATCH 2/2] Revert "kernel: Modify kernel modules installation path."

2017-01-20 Thread Jason Wessel
On 01/20/2017 07:30 AM, Burton, Ross wrote: On 20 January 2017 at 13:29, Maxin B. John > 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

Re: [OE-core] [PATCH 2/2] Revert "kernel: Modify kernel modules installation path."

2017-01-20 Thread Burton, Ross
On 20 January 2017 at 13:29, Maxin B. John 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 >

Re: [OE-core] [PATCH 2/2] Revert "kernel: Modify kernel modules installation path."

2017-01-20 Thread Maxin B. John
Hi Jason, On Thu, Jan 19, 2017 at 03:24:00PM -0600, Jason Wessel 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

Re: [OE-core] [PATCH 2/2] Revert "kernel: Modify kernel modules installation path."

2017-01-19 Thread Burton, Ross
On 19 January 2017 at 21:24, Jason Wessel wrote: > It may be fixable by using, ${nonarch_base_libdir}, but it wasn't quite > that simple because it didn't fully work for the firmware loader so for now > it would be best to just revert the two patches and keep oe-core

Re: [OE-core] [PATCH 2/2] Revert "kernel: Modify kernel modules installation path."

2017-01-19 Thread Jason Wessel
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. It may be fixable by using, ${nonarch_base_libdir}, but it wasn't

[OE-core] [PATCH 2/2] Revert "kernel: Modify kernel modules installation path."

2017-01-19 Thread Jason Wessel
This reverts commit 0ccb2efe9837e2915c093341a662dffc1df00866. The OVS fails to function and the kernel modules cannot be found by any of the kernel tools such as depmod because they are installed into the wrong directory in multilib 64bit/32bit bulids. Signed-off-by: Jason Wessel