Investigating run.do_configure suggests that in the configure stage oe_runconf() is set with what seems to be wrong –host and –target values: --host=armmllib32-linux-gnueabi

Is it documented anywhere on how one might manually load debug info an for image with the binaries stripped ? Thanks, Steve

Hi There, Following the instruction from TI https://software-dl.ti.com/processor-sdk-linux-rt/esd/AM64X/latest/exports/docs/linux/Overview_Building_the_SDK.html I’ve setup a yocto

I mention is as if I didn't someone would ask about it. I did backport the change to the corresponding bitbake branch and it hence made it to the poky branch for gatesgarth but there are no plans for

Hi Richard, Thank you for the clarification. Why do you mention Gatesgarth (3.2) while no update release is in sight? According to https://wiki.yoctoproject.org/wiki/Releases, it's already end of

Signed-off-by: Naveen Saini <naveen.kumar.saini@...> --- recipes-kernel/zephyr-kernel/zephyr-kernel-src.inc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git

It allow to build against latest main branch. User need to have following config locally to use it. PREFERRED_VERSION_zephyr-kernel = "dev" Signed-off-by: Naveen Saini

Hello, We are pleased to announce the Yocto Project 3.1.10 (dunfell-23.0.10) Release is now available for download.

The new syntax will work on the dunfell, gatesgarth, hardknott, master and new  release branches going forward. That applies now and that support will be in the next point releases for dunfell

applied to meta-rockchip, master

Yocto Technical Team Minutes, Engineering Sync, for August 10, 2021 archive: https://docs.google.com/document/d/1ly8nyhO14kDNnFcW2QskANXW3ZT7QwKC5wWVDg9dDH4/edit == disclaimer == Best efforts are

Hi Darcy, If I understood correctly, the old style will continue to be supported in 3.1 and in 3.3, as long as these releases are supported (that's what I'm trying to find out). These versions will

Hi, My apologies. I don't think I made my question clear. I am asking about the compatibility of old style override syntax moving forward (and new style syntax in old versions). So if I continue

I ran across the following under the Yocto Project Profiling and Tracing Manual, and after checking my ipk data files/layout, I was wondering if someone could tell me, if ipk is capable of performing

Hi again Darcy, I haven't managed to get such information yet, so I opened a bug to make sure I get an answer by Thursday, when we have our bug triage meeting. Here's the bug:

Hi Jared, That's not what I understand from the manual. From https://docs.yoctoproject.org/dev-manual/common-tasks.html#post-installation-scripts-and-read-only-root-filesystem, I understand that the

Hi Darcy, IANTM (I Am Not The Maintainers!), but I know that the old override syntax will be supported in the maintained releases as long as they are supported: * Dunfell 3.1, Long Term Support

Hi, Does anyone know how long (or how many releases) that the old override syntax will still be supported? (Like a deprecation EOL cycle). A corollary question: How far back in old releases

https://www.yoctoproject.org/docs/3.1.3/ref-manual/ref-manual.html#migration-2.1-miscellaneous-changes IMAGE_FEATURES="debug-tweaks read-only-rootfs" according to the manual having read-only-rootfs

Current Dev Position: YP 3.4 M3 Next Deadline: 23rd Aug. 2021 YP 3.4 M3 build (Feature Freeze) Next Team Meetings: Bug Triage meeting Thursday Aug. 12th at 7:30am PDT