Yes, I found that i bit ago. Very helpful, thanks. I have not run them yet (my only BBB is at home) but I am comparing the objdumps.

Hermanus Botha <wkj.id10t@...> writes: I guess this link is broken. In that manual, it's section: "4.2. Cross-Development Toolchain Generation" Manual:

Hi Federico, Ok, if that's not the issue what exactly is not working for you? No, that's actually sample code of a simple ls application that I use for teaching a class on Linux APIs. Cheers, Rudi

So I don't really know much about Yocto. But I would also like to see some more Go-lang action on Yocto. This section of their manual seems promising.

https://bugzilla.yoctoproject.org/show_bug.cgi?id=6165 Link to the two kernels at the end of the first comment. On Apr 16, 2014 6:57 PM, "William Mills" <wmills@...> wrote:

Hello, Can someone point to a 'life cycle statement' for Yocto versions, one that discusses limited bug fixing peroid and ultimate EOL of a version. I am having trouble find it. Regards, Armin

It isn't as simple as that, that just selects between providers but there is nothing to actually make the "mypackagegroup" recipe actually provide anything. The files would need to actually be

On Wed, Apr 16, 2014 at 9:28 AM, Elvis Dowson <elvis.dowson@...> wrote: I just tries a build with poky master, and meta-xilinx master branch, and got the following build error. For some reason the

Hi, I just tries a build with poky master, and meta-xilinx master branch, and got the following build error. For some reason the yocto build process fails is PACKAGE_CLASSES is set to package_ipk.

I see, but I don't want to feed the package from a repo, I just want to include all the files in the package. I'm now trying to set PREFERRED_PROVIDER_each-recipe = "mypackagegroup" hoping that it

opkg and similar package managers simply aren't designed to work like that; it's expected that both devices would have access to the same package feeds and therefore you would just install the

Thanks Paul, yes, it does "inherit packagegroup" and all the packages are installed. What I would like to have is a mypackagegroup.ipk that I can copy to any system to install all the files,

If your packagegroup recipe does "inherit packagegroup" and sets RDEPENDS_${PN} to depend upon the packages within the group, that will ensure that the packages get installed when the packagegroup's

It would be interesting to see if the rodata segment (or segment it contributes to) between working and non-working versions were crossing some magic power of 2 value. Are there two images published

Hi, I have some recipes that generate multiple packages. I also have a package group that groups all the recipes. I would like to use the package created with the packagegroup recipe to install all

But qemux86-64 or genericx86-64 or qemuarm kernel has the same strings, and it boots just fine: $

Thank you Rudolf! I knew that I can add source paths to the debugger. I see in your debug profiles that you have some binaries eg "ls". Did you import that binary from sysrootfs on your build

Adding weston.ini to $ROOT_HOME/.config. With this change user can login to $ROOT_HOME and launch weston with ivi-shell. Signed-off-by: Sujith H <Sujith_Haridasan@...> ---

seemingly there could be rodata segment overflow issue. Can you do the kernel build with say linker from dora build and see if it still fails.

And, as a follow up, all those long paths in vmlinux when built with B != S point to sources. Here are few examples: B != S