[yocto] warrior: QA issue when bump kernel to 5.2-rc2

Hi, I'm trying to add support for latest possible released kernel in meta-sunxi by using poky warrior and hit this QA issue: ERROR: linux-mainline-5.2-rc2-r0 do_package: QA Issue: linux-mainline: Files/directories were installed but not shipped in any package: /lib/modules/5.2.0-rc2/modules.buil

Re: [yocto] Yocto 2.7: SSTATEPOSTUNPACKFUNCS_remove not working

On Wed, 2019-05-29 at 22:37 +, Wolfgang Tolkien wrote: > Thanks, > > not sure I follow: 'SSTATEPOSTUNPACKFUNCS_remove' is not valid any > more and previously only worked because there was a bug? Previously the value of the expression wasn't accounted for in the hashes which represent the stat

Re: [yocto] warrior: QA issue when bump kernel to 5.2-rc2

On Thu, May 30, 2019 at 4:14 AM Belisko Marek wrote: > > Hi, > > I'm trying to add support for latest possible released kernel in > meta-sunxi by using poky warrior and hit this QA issue: > ERROR: linux-mainline-5.2-rc2-r0 do_package: QA Issue: linux-mainline: > Files/directories were installed bu

Re: [yocto] warrior: QA issue when bump kernel to 5.2-rc2

On Thu, May 30, 2019 at 2:35 PM Bruce Ashfield wrote: > > On Thu, May 30, 2019 at 4:14 AM Belisko Marek wrote: > > > > Hi, > > > > I'm trying to add support for latest possible released kernel in > > meta-sunxi by using poky warrior and hit this QA issue: > > ERROR: linux-mainline-5.2-rc2-r0 do_p

Re: [yocto] warrior: QA issue when bump kernel to 5.2-rc2

On Thu, May 30, 2019 at 8:37 AM Belisko Marek wrote: > > On Thu, May 30, 2019 at 2:35 PM Bruce Ashfield > wrote: > > > > On Thu, May 30, 2019 at 4:14 AM Belisko Marek > > wrote: > > > > > > Hi, > > > > > > I'm trying to add support for latest possible released kernel in > > > meta-sunxi by usi

Re: [yocto] [opkg-devel] [opkg-utils PATCH] Makefile: fixed for-loop in install receipe

indeed, thanks for the fix! merged On 5/29/19 1:57 PM, Josh Deweese wrote: > The install receipe would have copied all the manpages to each of the > section folders. This change will do what I believe the original > author had intended. > > Signed-off-by: Joshua DeWeese > --- > Makefile | 2 +-

Re: [yocto] Python module not found when using autotools

This is really an autotools question, not a yocto question. Specifically, what happens at this point? *| checking python module: soundcloud... no* Quite likely, the autotools script runs native python and asks it to import soundcloud, which fails. You need a different approach, maybe checking for

Re: [yocto] Python module not found when using autotools

Hi Alexander, thank you for the quick reply. Doing the ./configure part on the host machine for host (basically, compiling tizonia on Ubuntu) works fine, there it can find the soundcloud module. I just don't understand where autotools (during bitbake) is looking for the soundcloud module and what

Re: [yocto] Python module not found when using autotools

I guess you could start by looking at configure.ac in the failing component's source code and specifically which m4 macro it is using to find the python module, then look at the definition of that macro and what it does. Sadly, this kind of thing - working your way through large, unfamiliar code ba

Re: [yocto] Python module not found when using autotools

I understand the process of debugging build failures. I am just confused why my approach doesn't work. "python-soundcloud.bb" has the same format like other python module recipes in meta-oe. In tizonia.bb, I have added "python-soundcloud" to DEPENDS, so I assumed bitbake would resolve the necessary

Re: [yocto] meta-sunxi maintained?

Hi Maciej, On Wed, May 29, 2019 at 1:08 PM Maciej Pijanowski wrote: > > > On 29.05.2019 09:39, Belisko Marek wrote: > > Hi Dimitris, > > > > On Wed, May 29, 2019 at 9:03 AM Dimitris Tassopoulos > > wrote: > >> Hi Marek, > >> > >> that's correct. I have a branch though which I've started to expe