Hello Alexander Please find the output of 'env' below

Greetings ! I am working on NXP's i.MX6UL SoC and I have successfully built a Read-only Rootfile system through Yocto. Now I am having a requirement of making only "/etc" as Read & Writable . So , Can

The fixing is often wrapped in target-specific conditionals, and so fixing one does not address the other, until the conditional is expanded with additional or statements, or checks are done from

Ok, let's ask Intel, specifically Anuj :-) Anuj, does Intel still care about x32, and would anyone notice if yocto drops x32 support from master branch? Alex

Does the RISC-V ecosystem care about riscv32? The problem with Intel x32 is that very few people care, so we end up fixing upstream software. If RISC-V cares then we won’t be alone. Also, Intel

From: Michael Opdenacker <michael.opdenacker@...> From: Quentin Schulz <quentin.schulz@...> In order to maintain one less file, let's auto-generate the releases.rst file

<richard.purdie@...> wrote: But then why not replace x32 with riscv32, which as well has 32 bit pointers but 64 bit integers and thus trips over the same type size issues? Alex

That amounts to dropping x32 support because as soon as we remove these tests, it will bitrot. There is still some value in the project being able to support different architectures and different

Note: this update fails on x32 with | configure: error: unrecognized GNU build triplet linux-gnux32 This time I want to put my foot down and suggest that we just drop the whole x32 variant from the

This is not what I asked for (which was output of 'env'). Also, this shows the output of bitbake -c testimage, not of runqemu with nographic parameter. Alex

Hello Alexander, Please find the output file in attachment . Thanks

Hello Khem Raj , After rebooting i am getting same error .

I am using the AM572x evaluation module with the TI SDK, which uses the linaro toolchain. I am trying to enable UTF-8 so that I can use tmux. I am enabling it using the follow method: unset

maybe you should reboot the host machine, sometimes system updates without rebooting the machine can also result in such errors.

Hello everyone, Intel and WR YP QA is planning for QA execution for YP build yocto-4.1_M2.rc1. We are planning to execute following tests for this cycle: OEQA-manual tests for following module: 1.

A build flagged for QA (yocto-4.1_M2.rc1) was completed on the autobuilder and is available at: https://autobuilder.yocto.io/pub/releases/yocto-4.1_M2.rc1 Build hash information: bitbake:

Can I see the output of 'env' please? Alex

We are moving the hash equivalence server to dedicated servers. As part of the change we need to change the domain. Please update any BB_HASHSERVE_UPSTREAM variables from "typhoon.yocto.io:8687" to

Hello Alexander Yes I have tried that already but i am getting same error. If anyone could it would be great. Thanks in advance

You can try adding nographic option to runqemu if you do not need to see graphical output from your image. Alex