Opa! Great command for the future, tnx. Strange that it isn't listed here and is greppable in bitbake -e u-boot-fw-utils-senic... Here it is: u-boot-fw-utils-senic-v2017.03+git999-r0 do_listtasks:

Whhhaaaaat. Can your paste the output of this please: $ bitbake u-boot-fw-utils-senic -c listtasks Ross

Found what I was asking for with: bitbake -e <package> going through the output, there are mentions of patch_do_patch(). I've traced it to meta/classes/patch.bbclass. However, trying to execute just

That I can't see the changes for that particular patch in the source (by manually checking the source for the changes). Other patches are applied correctly, I can trace them in the sources. I have no

Hi , I am using yocto pyro and for creating users via recipe using inherit useradd, followed

What do you mean by patches not being applied correctly? temp/log.do_patch has the output from patch so that might show that you've a patch that applies with lots of fuzz and is applied

I see, so I can't use the devshell to debug why the patch hasn't been correctly applied. The answer you gave help for debugging actual build and configure problems. Debugging patching seems to be

The patching is done by a bbclass (patch.bbclass) and helper modules (meta/oe/lib/patch.py), so you can't execute it like a shell task (such as do_compile). Ross

Thanks for the suggestions Am currently implementing both of them and am trying to understand how the patching is done. In the temp directory I can see all the tasks. For some reasons the patch

Rootfs changes I can certainly do with different image recipes. Am I right though in thinking that - because they'll have different variants of u-boot - I'll need to use separate build directories for

Alexander Kanavin wrote: Sorry, I made a mistake. I had a bbappend for linux-firmware in my layer, which retrieved an older revision from a year ago (at the time I wrote the bbappend, it was to

Ah, meta-arago sets PACCKAGECONFIG_pn-weston without xwayland. PACKAGECONFIG_pn-weston = "egl kms launch clients"

Hi Raj, These are my DISTRO_FEATURES: DISTRO_FEATURES="alsa argp bluetooth ext2 irda largefile pcmcia usbgadget usbhost wifi xattr nfs zeroconf pci 3g nfc x11 ipv4 ipv6 libc-backtrace libc-big-macros

you need opengl in DISTRO_FEATURES as well. additionally weston-xwayland would need wayland and x11 in DISTRO_FEATURES

I believe something is incorrect in my distro level configuration. Apart from including x11 and wayland in DISTRO_FEATURES, what else can I check to build

Guessing... apply this in your recipe: http://git.yoctoproject.org/cgit/cgit.cgi/poky/tree/meta/recipes-bsp/u-boot/files/default-gcc.patch?h=pyro -- Alex Kiernan Senior Engineering

$ bitbake <recipe> -c devshell This drops you in a new terminal with the same environment that bitbake sets up, and in ../temp/ you'll find run.do_compile and so on, which are the scripts that bitbake

I'm just upgrading to pyro and have some issues with u-boot-fw-utils. The error fails at do_compile stage which looks like this: do_compile () { oe_runmake ${UBOOT_MACHINE}

Image, certainly. Put the common bits into an include, and specific bits into image-production|development.bb files. Poky has plenty of examples for this. Alex

Are you refering to DISTRO_FEATURES? That just controls what is *available*, not what goes into a particular image. As Fabien said, core-image-weston is the classic example of an image that has