[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.builtin.modinfo Please set FILES such that these items are packaged. Alternatively if they are unneeded, avoid installing them or delete them within do_install. linux-mainline: 1 installed and not shipped files. [installed-vs-shipped] I can simply drop it but would like to see if anything was updated from actual linux-yocto (which is 5.0.3). Ideas? Thanks. BR, marek -- as simple and primitive as possible - Marek Belisko - OPEN-NANDRA Freelance Developer Ruska Nova Ves 219 | Presov, 08005 Slovak Republic Tel: +421 915 052 184 skype: marekwhite twitter: #opennandra web: http://open-nandra.com -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
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 state of the tasks.
The remove values need to be accounted for so we fixed that.
The reason you now see the hash mismatch is because its correctly
accounting for "remove" expressions.
> Also, what about running bitbake-dumpsig on the task sigdata and
> finding a line containing
>
> "_remove of" (and nothing else)
Its showing its accounting for the remove.
Its empty due to the code in uninative.bbclass which sets a
vardepvalueexclude for SSTATEPOSTUNPACKFUNCS.
You're seeing the hash change because uninative is a little odd due to
the point in parsing where it gets added. Its not meant to change the
hash but the way you're altering things means it now does.
What may work is doing something like:
python uninative_changeinterp () {
return
}
Cheers,
Richard
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
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 but not shipped in any package: > /lib/modules/5.2.0-rc2/modules.builtin.modinfo > Please set FILES such that these items are packaged. Alternatively if > they are unneeded, avoid installing them or delete them within > do_install. > linux-mainline: 1 installed and not shipped files. [installed-vs-shipped] > > I can simply drop it but would like to see if anything was updated > from actual linux-yocto (which is 5.0.3). Ideas? Thanks. I have a change to kernel.bbclass that packages that new file, and explains where it comes from. Stay tuned, it'll arrive in about 5 minutes :D Bruce > > BR, > > marek > > -- > as simple and primitive as possible > - > Marek Belisko - OPEN-NANDRA > Freelance Developer > > Ruska Nova Ves 219 | Presov, 08005 Slovak Republic > Tel: +421 915 052 184 > skype: marekwhite > twitter: #opennandra > web: http://open-nandra.com > -- > ___ > yocto mailing list > yocto@yoctoproject.org > https://lists.yoctoproject.org/listinfo/yocto -- - Thou shalt not follow the NULL pointer, for chaos and madness await thee at its end - "Use the force Harry" - Gandalf, Star Trek II -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
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_package: QA Issue: linux-mainline: > > Files/directories were installed but not shipped in any package: > > /lib/modules/5.2.0-rc2/modules.builtin.modinfo > > Please set FILES such that these items are packaged. Alternatively if > > they are unneeded, avoid installing them or delete them within > > do_install. > > linux-mainline: 1 installed and not shipped files. [installed-vs-shipped] > > > > I can simply drop it but would like to see if anything was updated > > from actual linux-yocto (which is 5.0.3). Ideas? Thanks. > > I have a change to kernel.bbclass that packages that new file, and > explains where it comes from. > > Stay tuned, it'll arrive in about 5 minutes :D Awesome, thanks! > > Bruce > > > > > BR, > > > > marek > > > > -- > > as simple and primitive as possible > > - > > Marek Belisko - OPEN-NANDRA > > Freelance Developer > > > > Ruska Nova Ves 219 | Presov, 08005 Slovak Republic > > Tel: +421 915 052 184 > > skype: marekwhite > > twitter: #opennandra > > web: http://open-nandra.com > > -- > > ___ > > yocto mailing list > > yocto@yoctoproject.org > > https://lists.yoctoproject.org/listinfo/yocto > > > > -- > - Thou shalt not follow the NULL pointer, for chaos and madness await > thee at its end > - "Use the force Harry" - Gandalf, Star Trek II BR, marek -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
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 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.builtin.modinfo > > > Please set FILES such that these items are packaged. Alternatively if > > > they are unneeded, avoid installing them or delete them within > > > do_install. > > > linux-mainline: 1 installed and not shipped files. [installed-vs-shipped] > > > > > > I can simply drop it but would like to see if anything was updated > > > from actual linux-yocto (which is 5.0.3). Ideas? Thanks. > > > > I have a change to kernel.bbclass that packages that new file, and > > explains where it comes from. > > > > Stay tuned, it'll arrive in about 5 minutes :D > Awesome, thanks! The patch is out on the oe-core mailing list, make sure to look for it there. Bruce > > > > Bruce > > > > > > > > BR, > > > > > > marek > > > > > > -- > > > as simple and primitive as possible > > > - > > > Marek Belisko - OPEN-NANDRA > > > Freelance Developer > > > > > > Ruska Nova Ves 219 | Presov, 08005 Slovak Republic > > > Tel: +421 915 052 184 > > > skype: marekwhite > > > twitter: #opennandra > > > web: http://open-nandra.com > > > -- > > > ___ > > > yocto mailing list > > > yocto@yoctoproject.org > > > https://lists.yoctoproject.org/listinfo/yocto > > > > > > > > -- > > - Thou shalt not follow the NULL pointer, for chaos and madness await > > thee at its end > > - "Use the force Harry" - Gandalf, Star Trek II > > BR, > > marek -- - Thou shalt not follow the NULL pointer, for chaos and madness await thee at its end - "Use the force Harry" - Gandalf, Star Trek II -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
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 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/Makefile b/Makefile
> index 69a1c5a..817a8c1 100644
> --- a/Makefile
> +++ b/Makefile
> @@ -23,7 +23,7 @@ install: all
> for m in $(MANPAGES); \
> do \
> install -d $(DESTDIR)$(mandir)/man$${m##*.}; \
> - install -m 644 $(MANPAGES) $(DESTDIR)$(mandir)/man$${m##*.}; \
> + install -m 644 "$$m" $(DESTDIR)$(mandir)/man$${m##*.}; \
> done
>
> .PHONY: install all
> --
> 2.7.4
>
>
>
> This email has been scanned for email related threats and delivered
> safely by Mimecast.
> For more information please visit http://www.mimecast.com
>
>
>
>
>
> --
> You received this message because you are subscribed to the Google
> Groups "opkg-devel" group.
> To unsubscribe from this group and stop receiving emails from it, send
> an email to opkg-devel+unsubscr...@googlegroups.com
> .
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/opkg-devel/1559156195-16281-1-git-send-email-jdeweese%40hennypenny.com
>
> .
> For more options, visit https://groups.google.com/d/optout
> .
--
Cheers,
Alejandro
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
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
the module file in the target sysroot.
Also, do not use python 2.7. All upstream support for it ends in 6 months.
Alex
On Thu, 30 May 2019 at 04:37, Serkan Türker
wrote:
> Hi all,
>
> I am trying to write a bitbake file for a project. The project uses
> autotools for configuring the project before building it.
> While configuring it, it searches for several python modules, where some
> of them are custom modules I wrote the bitbake recipe for.
> Even though the python module builds and installs correctly to the sysroot
> directory, it is not found in the configure step.
>
>
> python-soundcloud_0.5.0.bb
>
> *---*
>
>
>
>
>
>
>
>
> *LICENSE = "MIT"LIC_FILES_CHKSUM =
> "file://LICENSE;md5=31fa3a9dc818e0087893d63583d2d21a"SRC_URI[md5sum] =
> "40c1d32afd019ed11ec1fbee3e84e31f"SRC_URI[sha256sum] =
> "aad2003592cec945f835f158f7b41ba8bf805c5738a2fcc5629668ea1df653d5"DEPENDS_${PN}
> = "${PYTHON_PN}-modules"PYPI_PACKAGE = "soundcloud"*
>
>
>
> *inherit setuptools pypiRDEPENDS_${PN} = "${PYTHON_PN}-modules"*
>
> ---
>
> *python-soundcloud is succesfully installed to
> "BUILD/sysroots/raspberrypi3/usr/lib/python2.7/site-packages/soundcloud"*
>
>
> tizonia.bb
>
> ---
>
>
>
>
>
>
>
>
>
>
> *SUMMARY = "Tizonia Library"DESCRIPTION = "Tizonia"LICENSE =
> "LGPL-3.0"LIC_FILES_CHKSUM =
> "file://COPYING.LESSER;md5=e6a600fd5e1d9cbde2d983680233ad02"SRC_URI =
> "git://github.com/tizonia/tizonia-openmax-il.git;protocol=https
> "SRCREV =
> "9004bc40b89eeafb04b28fbb2b772e47dd62fdc9"S = "${WORKDIR}/git"DEPENDS =
> "mediainfo log4c python-pip python-soundcloud"*
>
>
>
>
>
> *inherit autotools ccache pkgconfig pythonnativeRDEPENDS_${PN} =
> "libstdc++ mediainfo log4c python-soundcloud"EXTRA_OECONF += "-C"*
>
> ---
>
> *The error message I get from bitbake:*
>
>
>
>
>
>
>
>
>
>
>
>
> *| checking for python2.7... (cached)
> /home/developer/build-webos-ose/BUILD/sysroots/x86_64-linux/usr/bin/python-native/python|
> checking for a version of Python >= '2.1.0'... yes| checking for a version
> of Python >= '2.7'... yes| checking for the distutils Python package...
> yes| checking for Python include path...
> -I/home/developer/build-webos-ose/BUILD/sysroots/raspberrypi3/usr/include/python2.7|
> checking for Python library path...
> -L/home/developer/build-webos-ose/BUILD/sysroots/raspberrypi3/usr/lib
> -lpython2.7| checking for Python site-packages path...
> /home/developer/build-webos-ose/BUILD/sysroots/x86_64-linux/usr/lib/python2.7/site-packages|
> checking python extra libraries... -lpthread -ldl -lpthread -lutil -lm|
> checking python extra linking flags... -Xlinker -export-dynamic| checking
> consistency of all components of python development environment... yes|
> checking python module: soundcloud... no| configure: error: failed to find
> required module soundcloud*
>
> Does somebody know what I am doing wrong? I cannot figure it out, any help
> is appreciated!
>
> Cheers,
> Serkan
> --
> ___
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
>
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
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 I have to do
to make it work.
Cheers,
Serkan
On Thu, May 30, 2019 at 11:46 AM Alexander Kanavin
wrote:
> 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 the module file in the target sysroot.
>
> Also, do not use python 2.7. All upstream support for it ends in 6 months.
>
> Alex
>
> On Thu, 30 May 2019 at 04:37, Serkan Türker
> wrote:
>
>> Hi all,
>>
>> I am trying to write a bitbake file for a project. The project uses
>> autotools for configuring the project before building it.
>> While configuring it, it searches for several python modules, where some
>> of them are custom modules I wrote the bitbake recipe for.
>> Even though the python module builds and installs correctly to the
>> sysroot directory, it is not found in the configure step.
>>
>>
>> python-soundcloud_0.5.0.bb
>>
>> *---*
>>
>>
>>
>>
>>
>>
>>
>>
>> *LICENSE = "MIT"LIC_FILES_CHKSUM =
>> "file://LICENSE;md5=31fa3a9dc818e0087893d63583d2d21a"SRC_URI[md5sum] =
>> "40c1d32afd019ed11ec1fbee3e84e31f"SRC_URI[sha256sum] =
>> "aad2003592cec945f835f158f7b41ba8bf805c5738a2fcc5629668ea1df653d5"DEPENDS_${PN}
>> = "${PYTHON_PN}-modules"PYPI_PACKAGE = "soundcloud"*
>>
>>
>>
>> *inherit setuptools pypiRDEPENDS_${PN} = "${PYTHON_PN}-modules"*
>>
>> ---
>>
>> *python-soundcloud is succesfully installed to
>> "BUILD/sysroots/raspberrypi3/usr/lib/python2.7/site-packages/soundcloud"*
>>
>>
>> tizonia.bb
>>
>> ---
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>> *SUMMARY = "Tizonia Library"DESCRIPTION = "Tizonia"LICENSE =
>> "LGPL-3.0"LIC_FILES_CHKSUM =
>> "file://COPYING.LESSER;md5=e6a600fd5e1d9cbde2d983680233ad02"SRC_URI =
>> "git://github.com/tizonia/tizonia-openmax-il.git;protocol=https
>> "SRCREV =
>> "9004bc40b89eeafb04b28fbb2b772e47dd62fdc9"S = "${WORKDIR}/git"DEPENDS =
>> "mediainfo log4c python-pip python-soundcloud"*
>>
>>
>>
>>
>>
>> *inherit autotools ccache pkgconfig pythonnativeRDEPENDS_${PN} =
>> "libstdc++ mediainfo log4c python-soundcloud"EXTRA_OECONF += "-C"*
>>
>> ---
>>
>> *The error message I get from bitbake:*
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>> *| checking for python2.7... (cached)
>> /home/developer/build-webos-ose/BUILD/sysroots/x86_64-linux/usr/bin/python-native/python|
>> checking for a version of Python >= '2.1.0'... yes| checking for a version
>> of Python >= '2.7'... yes| checking for the distutils Python package...
>> yes| checking for Python include path...
>> -I/home/developer/build-webos-ose/BUILD/sysroots/raspberrypi3/usr/include/python2.7|
>> checking for Python library path...
>> -L/home/developer/build-webos-ose/BUILD/sysroots/raspberrypi3/usr/lib
>> -lpython2.7| checking for Python site-packages path...
>> /home/developer/build-webos-ose/BUILD/sysroots/x86_64-linux/usr/lib/python2.7/site-packages|
>> checking python extra libraries... -lpthread -ldl -lpthread -lutil -lm|
>> checking python extra linking flags... -Xlinker -export-dynamic| checking
>> consistency of all components of python development environment... yes|
>> checking python module: soundcloud... no| configure: error: failed to find
>> required module soundcloud*
>>
>> Does somebody know what I am doing wrong? I cannot figure it out, any
>> help is appreciated!
>>
>> Cheers,
>> Serkan
>> --
>> ___
>> yocto mailing list
>> yocto@yoctoproject.org
>> https://lists.yoctoproject.org/listinfo/yocto
>>
>
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto
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 base to debug a build failure - is typical when working
with Yocto, and is pretty much a required skill.
Alex
On Thu, 30 May 2019 at 21:08, Serkan Türker
wrote:
> 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 I have to do
> to make it work.
>
> Cheers,
> Serkan
>
> On Thu, May 30, 2019 at 11:46 AM Alexander Kanavin
> wrote:
>
>> 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 the module file in the target sysroot.
>>
>> Also, do not use python 2.7. All upstream support for it ends in 6 months.
>>
>> Alex
>>
>> On Thu, 30 May 2019 at 04:37, Serkan Türker
>> wrote:
>>
>>> Hi all,
>>>
>>> I am trying to write a bitbake file for a project. The project uses
>>> autotools for configuring the project before building it.
>>> While configuring it, it searches for several python modules, where some
>>> of them are custom modules I wrote the bitbake recipe for.
>>> Even though the python module builds and installs correctly to the
>>> sysroot directory, it is not found in the configure step.
>>>
>>>
>>> python-soundcloud_0.5.0.bb
>>>
>>> *---*
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>> *LICENSE = "MIT"LIC_FILES_CHKSUM =
>>> "file://LICENSE;md5=31fa3a9dc818e0087893d63583d2d21a"SRC_URI[md5sum] =
>>> "40c1d32afd019ed11ec1fbee3e84e31f"SRC_URI[sha256sum] =
>>> "aad2003592cec945f835f158f7b41ba8bf805c5738a2fcc5629668ea1df653d5"DEPENDS_${PN}
>>> = "${PYTHON_PN}-modules"PYPI_PACKAGE = "soundcloud"*
>>>
>>>
>>>
>>> *inherit setuptools pypiRDEPENDS_${PN} = "${PYTHON_PN}-modules"*
>>>
>>> ---
>>>
>>> *python-soundcloud is succesfully installed to
>>> "BUILD/sysroots/raspberrypi3/usr/lib/python2.7/site-packages/soundcloud"*
>>>
>>>
>>> tizonia.bb
>>>
>>> ---
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>> *SUMMARY = "Tizonia Library"DESCRIPTION = "Tizonia"LICENSE =
>>> "LGPL-3.0"LIC_FILES_CHKSUM =
>>> "file://COPYING.LESSER;md5=e6a600fd5e1d9cbde2d983680233ad02"SRC_URI =
>>> "git://github.com/tizonia/tizonia-openmax-il.git;protocol=https
>>> "SRCREV =
>>> "9004bc40b89eeafb04b28fbb2b772e47dd62fdc9"S = "${WORKDIR}/git"DEPENDS =
>>> "mediainfo log4c python-pip python-soundcloud"*
>>>
>>>
>>>
>>>
>>>
>>> *inherit autotools ccache pkgconfig pythonnativeRDEPENDS_${PN} =
>>> "libstdc++ mediainfo log4c python-soundcloud"EXTRA_OECONF += "-C"*
>>>
>>> ---
>>>
>>> *The error message I get from bitbake:*
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>> *| checking for python2.7... (cached)
>>> /home/developer/build-webos-ose/BUILD/sysroots/x86_64-linux/usr/bin/python-native/python|
>>> checking for a version of Python >= '2.1.0'... yes| checking for a version
>>> of Python >= '2.7'... yes| checking for the distutils Python package...
>>> yes| checking for Python include path...
>>> -I/home/developer/build-webos-ose/BUILD/sysroots/raspberrypi3/usr/include/python2.7|
>>> checking for Python library path...
>>> -L/home/developer/build-webos-ose/BUILD/sysroots/raspberrypi3/usr/lib
>>> -lpython2.7| checking for Python site-packages path...
>>> /home/developer/build-webos-ose/BUILD/sysroots/x86_64-linux/usr/lib/python2.7/site-packages|
>>> checking python extra libraries... -lpthread -ldl -lpthread -lutil -lm|
>>> checking python extra linking flags... -Xlinker -export-dynamic| checking
>>> consistency of all components of python development environment... yes|
>>> checking python module: soundcloud... no| configure: error: failed to find
>>> required module soundcloud*
>>>
>>> Does somebody know what I am doing wrong? I cannot figure it out, any
>>> help is appreciated!
>>>
>>> Cheer
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 path's, which are necessary for the
build.
It is also not only my fault not being able to fix this, it is also largely
related to the fact, that there is not much documentation around how to
start developing with Yocto in general.
I am gonna continue banging my head.
Cheers.
On Thu, May 30, 2019 at 12:21 PM Alexander Kanavin
wrote:
> 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 base to debug a build failure - is typical when working
> with Yocto, and is pretty much a required skill.
>
> Alex
>
> On Thu, 30 May 2019 at 21:08, Serkan Türker
> wrote:
>
>> 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 I have to do
>> to make it work.
>>
>> Cheers,
>> Serkan
>>
>> On Thu, May 30, 2019 at 11:46 AM Alexander Kanavin <
>> alex.kana...@gmail.com> wrote:
>>
>>> 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 the module file in the target sysroot.
>>>
>>> Also, do not use python 2.7. All upstream support for it ends in 6
>>> months.
>>>
>>> Alex
>>>
>>> On Thu, 30 May 2019 at 04:37, Serkan Türker
>>> wrote:
>>>
Hi all,
I am trying to write a bitbake file for a project. The project uses
autotools for configuring the project before building it.
While configuring it, it searches for several python modules, where
some of them are custom modules I wrote the bitbake recipe for.
Even though the python module builds and installs correctly to the
sysroot directory, it is not found in the configure step.
python-soundcloud_0.5.0.bb
*---*
*LICENSE = "MIT"LIC_FILES_CHKSUM =
"file://LICENSE;md5=31fa3a9dc818e0087893d63583d2d21a"SRC_URI[md5sum] =
"40c1d32afd019ed11ec1fbee3e84e31f"SRC_URI[sha256sum] =
"aad2003592cec945f835f158f7b41ba8bf805c5738a2fcc5629668ea1df653d5"DEPENDS_${PN}
= "${PYTHON_PN}-modules"PYPI_PACKAGE = "soundcloud"*
*inherit setuptools pypiRDEPENDS_${PN} = "${PYTHON_PN}-modules"*
---
*python-soundcloud is succesfully installed to
"BUILD/sysroots/raspberrypi3/usr/lib/python2.7/site-packages/soundcloud"*
tizonia.bb
---
*SUMMARY = "Tizonia Library"DESCRIPTION = "Tizonia"LICENSE =
"LGPL-3.0"LIC_FILES_CHKSUM =
"file://COPYING.LESSER;md5=e6a600fd5e1d9cbde2d983680233ad02"SRC_URI =
"git://github.com/tizonia/tizonia-openmax-il.git;protocol=https
"SRCREV =
"9004bc40b89eeafb04b28fbb2b772e47dd62fdc9"S = "${WORKDIR}/git"DEPENDS =
"mediainfo log4c python-pip python-soundcloud"*
*inherit autotools ccache pkgconfig pythonnativeRDEPENDS_${PN} =
"libstdc++ mediainfo log4c python-soundcloud"EXTRA_OECONF += "-C"*
---
*The error message I get from bitbake:*
*| checking for python2.7... (cached)
/home/developer/build-webos-ose/BUILD/sysroots/x86_64-linux/usr/bin/python-native/python|
checking for a version of Python >= '2.1.0'... yes| checking for a version
of Python >= '2.7'... yes| checking for the distutils Python package...
yes| checking for Python include path...
-I/home/
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 experiment > >> and add support for Mali. I didn't finished because I've tried to do this > >> by myself from the scratch and soon I've hit a wall. Nevertheless, I've > >> done the same for the rk3399 for nanopi-neo4 and during this process I've > >> learned a lot on how to do it with some help from other people from the > >> open source scene. The graphics stack was too complicated for me in the > >> beginning. > > You can maybe look to meta-sunxi there is sunxi-mali driver + > > libraries which will add support for that. When I've set that package > > to PREFERRED_PROVIDER_virtual/gles2 I get issues with compilation > > gtk3+ and others. I've spend 2 hours looking and trying yesterday but > > without any success. Also pls look at this communication: > > https://github.com/linux-sunxi/meta-sunxi/issues/144 (looks like we > > can use opensource drivers + libs later). Thanks. > What are you trying to achieve? Which kernel version are you using? > Isn't the mali recipe in meta-sunxi quite dated already? Can it work > with mainline kernel correctly? > > I would suggest to try the recent blobs as described in this post: > https://bootlin.com/blog/mali-opengl-support-on-allwinner-platforms-with-mainline-linux/ > > As I've written previously, I have been using the Wayland / Qt with > good performance on H3 using the mainline kernel. Is it something you > are looking for? > You can take a look at my dirty branch - maybe this will be any help: > https://github.com/3mdeb/meta-sunxi/tree/weston-with-kms/recipes-graphics/mali I've took some patches and now core-image-sato can be build. I have just one question for mali kernel module. Does it need some dts changes or it will work out of the box (I didn't see any dts changes in your branch thus I'm asking). Thanks. > > Unfortunately, I had stopped working on that and presently do not have much > time to clean up / get back to it. I can provide some support and / or get > back to it if it seems valuable and there is some interest. > >> Therefore now that I feel much more confident with it I'm going to re-try > >> and finish with my branch. Armbian does have support, so I'll try to stick > >> to the Armbian backend for maintenance reasons. > >> > >> I hope that this will be rather easy, because the dri driver should > >> already be there, so the only thing I believe is needed is the blobs and > >> to create symlinks for the various so libs to that blob. > >> > >> Anyway, I'll try to do that also. In the meantime I will also wait a bit > >> to see if that merge between those two layers is possible and doable, > >> which will help to short the time and effort to do that. > >> > >> Regards, > >> Dimitris > > BR, > > > > marek > >> Belisko Marek schrieb am Mi., 29. Mai 2019, > >> 08:37: > >>> Hi Dimitris, > >>> > >>> On Tue, May 28, 2019 at 1:07 PM Dimitris Tassopoulos > >>> wrote: > Hi Enrico, > > I'm totally positive to any possibility for such integration. > Personally, that was the first thing I've tried to do before I start > this layer, but I've failed as it got really complex and the overhead > was too much after some point (at least for me). If you have look it's > actually a mix of meta-sunxi and armbian, but I had to remove or change > many stuff to fit the armbian in the layer. > > If you have time to have a look to my layer and you think that such kind > of integration is possible and can be done in a more easy way, then from > my side I'm all in. > I believe that re-using the armbian patches is easier as it makes > maintenance much easier, there are more supported SBCs and also there is > much more testing involved in armbian and frequent updates fix those > bugs. > >>> I did check your layer and it seems that you're not using sunxi-mali > >>> for opengl HW acceleration only mesa so SW rendering? Thanks. > Please consider it and I can help as much as I can and my time allows > for that integration. > > Regards, > Dimitris > > > >>> Marek > On Tue, May 28, 2019 at 12:56 PM Enrico > wrote: > > On Tue, May 28, 2019 at 12:06 PM Dimitris Tassopoulos > > wrote: > >>> I was thinking about this also, too. The only reason is that in > >>> meta-sunxi they do a great job and they keep their layer clean, which > >>> is great I think. The other layers are just based on the armbian > >>> distro, which is a lot different, but for me it was much easier to > >>> integrate their patches, patching scripts and bootloader scripts to a > >>> Yocto layer. That way the only thing I do is that from time to t
