YUP! Thank you for the fix (I totally forgot about scripts directory). Command: make scripts prepare solved it all! Here is all captured (in order of

I did some reading into the sources in other architectures. The closest match, arch_i386.c, makes the write conditional as you say. So do other arches, including arch_arm.c, arch_sh.c, arch-mips.c,

Is there no way to simply force bitbake to only build the packages I want, ignoring dependencies? We used to build the image like this before, using PTXDist. Everything else seems to be a dirty

Hi guys, The warnings were definitely not on when I started using Yocto more than two years ago. I have not been using debian packages, and didn't notice. I thought I was still not using debian and

I can confirm that after wget'ing the files from your github, that I can build the module just by using kernel-devsrc (on the core-image-kernel-dev image). I only had my qemux86-64 build handy, so I

Could you, please, point to me which YOCTO bugzilla this is? I would like to capture these in the https://github.com/ZoranStojsavljevic/bbb-yocto/tree/master/Issues, just to have them as

Hi all, i am working on one open source project,for this i have to add some debian packages as yocto recipies. i am trying to add "audit" recipe,so iam trying to understand the audit debian package

I'll try some test builds and see what I can find. Some new issues may have crept in. Cheers, Bruce -- - Thou shalt not follow the NULL pointer, for chaos and madness await thee at its end - "Use

That's exactly what the kernel-devsrc package is. It is about 90 Megs (unpacked) and is the headers + config required to build out of tree modules against the kernel. I'm going to create two new

As I said, I am a man of experimental try-outs. And here is the try! Now, after setting sources, I tried to compile the example (from my

In fact the OS is just a minimal rescue OS. On a second partition we run our main OS, which is ‘properly’ installed. So, I’m afraid using a ‘proper’ file system wouldn’t fit our use case.

This is all covered in the documentation, online tutorials and several excellent books. I'd recommend you set aside some time for learning here as it sounds like you're not familiar with the basic

Hi Paul, I understood what you are trying to say but from where does the Yocto pick up the contents for a directory in final rootfs image. Is there any recipe file in which I can find

In a Yocto Project build, the rootfs is built from packages and the packages are in turn built from recipes. The supported process for adding new software to the image is to write a recipe which

Would you consider switching to a proper filesystem? The peril of using a cpio.gz is that every file you add slows the boot down: using a proper filesystem solves this. Ross

The meta-intel BSP is the recommend BSP for all Intel platfoms. Ross

Hello, I searched for ATOM N450 recipe, but only found very old one: https://old.yoctoproject.org/downloads/bsps/edison11/atom-pc The problem is that we need newer gcc (above 4.8.2). Should it be

Kindly help me out in locating the source for /usr/bin of rootfs image in yocto. I did a find but I do not see the /usr/bin and its exact contents as in the rootfs image. I need to locate this badly

Ok, thanks.

<coolveer07@...> wrote: At a guess, because the libgcrypt recipe is: LICENSE = "GPLv2+ & LGPLv2.1+ & GPLv3+" Whereas libgcrypt itself is: LICENSE_${PN} = "LGPLv2.1+" That's a bit of a