Re: [yocto] dnf fail in do_rootfs cannot find shared library

This is a longshot but I am currently investigating an issue we have with a packagegroup. I get a similar error but I can fix it by moving the package in my RDEPENDS in the packagegroup. If you move your libx_media up or down in the packagegroup, does it help? For me i got: Error:

Re: [yocto] dnf fail in do_rootfs cannot find shared library

I'm not sure this is your problem but if you don't version your so-libs you could get this since the .so (without version) is not shipped by default I think. Try putting this in your recipe: SOLIBS = ".so*" FILES_SOLIBSDEV = "" ERROR_QA_remove = "dev-so" If that works I think the proper solution

[yocto] Parsing bug in packagegroup

Hi, I'm having some problems with a packagegroup of ours. It basically looks like this: inherit packagegroup RDEPENDS_${PN} = "\ libdomain-somelib \ libsomeotherlib \ served-util \ " Where served-util also is a lib. Now depending on what I put in my

Re: [yocto] Python3 and pathlib/ntpath

or pathlib in the python3-manifest file but I'm not sure how that thing is supposed to work. // Einar On Fri, Dec 21, 2018 at 5:48 PM Einar Vading wrote: > > Adding python3-misc did not seem to make a difference. > > // Einar > > Den fre 21 dec. 2018 15:16 skrev Einar Vading

Re: [yocto] Python3 and pathlib/ntpath

Adding python3-misc did not seem to make a difference. // Einar Den fre 21 dec. 2018 15:16 skrev Einar Vading : > I'm installing using the recipe. > > Running Sumo and the meson recipe has: > RDEPENDS_${PN} = "ninja python3-core python3-modules" > > I'll try to

Re: [yocto] Python3 and pathlib/ntpath

nside the image, > instead of using the recipe? In that case ensure that you have all of > Python installed, easiest way is to add python3 to IMAGE_INSTALL. > > Ross > > On Fri, 21 Dec 2018 at 13:17, Einar Vading wrote: > > > > Hi, > > > > I was trying to

[yocto] Python3 and pathlib/ntpath

Hi, I was trying to install meson on target for a machine that creates a docker image for us. When I try to start meson however I get an error message that pathlib can't be found. With the patch below I got it to work but my question is if there is another way? Or if the patch would be acceptable

[yocto] Python3 and pathlib/ntpath

Hi, I was trying to install meson on target for a machine that creates a docker image for us. When I try to start meson however I get an error message that pathlib can't be found. With the patch below I got it to work but my question is if there is another way? Or if the patch would be acceptable

[yocto] Best practices when for script recipes.

Hi, I was just wondering if there is some best practice advice on how to handle adding a single script from a recipe. If I have one or a few shell scripts with their own recipe. Do I make a git and use the git from the recipe or do I just add the scripts to a files directory and install from

[yocto] Fwd: Best practices when for script recipes.

Hi, I was just wondering if there is some best practice advice on how to handle adding a single script from a recipe. If I have one or a few shell scripts with their own recipe. Do I make a git and use the git from the recipe or do I just add the scripts to a files directory and install from

Re: [yocto] [PATCH] Added missing CPPFLAGS/CFLAGS/LDFLAGS in sample recipe for morty branch

On Mon, Jul 17, 2017 at 4:48 PM, Leonardo Sandoval < leonardo.sandoval.gonza...@linux.intel.com> wrote: > On Mon, 2017-07-17 at 15:30 +0100, Burton, Ross wrote: > > > > On 17 July 2017 at 15:04, Leonardo Sandoval > > wrote: > > master has the

[yocto] linux-yocto-dev stagnated at 4.11-rc6

Hello everyone, I was just wondering if there is a reason for linux-yocto-dev staying at 4.11-rc6? I was under the impression that it would basically follow kernel.org which is now at 4.12 since a few days. Thank you, Einar -- ___ yocto mailing list