you perhaps need this kbd patch https://git.kernel.org/pub/scm/linux/kernel/git/legion/kbd.git/commit/?id=50eae66fc21ef8e01c69a9d3c1ff3fcb0b2644a0

<matthias.klein@...> wrote: ideally it should not. It really should be that app is using right port to talk to the one you choose.

<matthias.klein@...> wrote: this means you are choosing openSSL to provide TLS protocol implementation instead of gnuTLS

you need something like this https://patchwork.openembedded.org/patch/172282/

yeah something like that works, we use it for yoe which always uses container to build see https://github.com/YoeDistro/yoe-distro/blob/master/envsetup.sh#L528-L541

#bitbake

How would one use new version of both go and say kernel in a project

<alex.kanavin@...> wrote: this could be an independent layer too.

<bluelightning@...> wrote: That is good testimony, it will be good to know how this option impacts performance and does it work across architectures and libc's supported in OE.

<rudolf.streif@...> wrote: seems an oversight.

perhaps gdb-cross-${TARGET_ARCH} would be more generic.

take a look at following link, it will help solve this hopefully https://wiki.gentoo.org/wiki/Project:Toolchain/Binutils_2.34_porting_notes/undefined_reference_to_bfd_get_section_* <michael.opdenacker

if you are using latest release then py2 is more or less not needed unless you use perhaps packages like chromium ( which is also now fixed in meta-browser ) but this is for oe-core and meta-oe layers

#python

Yes it’s supported although it’s not default for qemumips so the simple trick you can do is change the DEFAULTTUNE setting in the qemumips.conf away from mips32r2

We have dropped uclibc support long time ago so any effort to support uClibc based system will be a bit of work and we have also dropped stale patches from metadata so even if you are able to get exte

lgtm. Thanks

<quentin.schulz@...> wrote: sounds good.

just adding layer is not enough, you have to add it to your image as well via IMAGE_INSTALL or some other way as indirect dependency

<quentin.schulz@...> wrote: perhaps applying the sed expression via do_configure:prepend() is simple ? and maybe make it rk3399 specific with do_configure:prepend:rk3399

I think using qemux86-64 might be your best bet, its fairly automated with runqemu script all you would need to do is package up the gtests as ptest package with a runner

I agree with you that broken is not good as it was for sometime, but now with the latest supported release in 3.4 series ( which is 3.4.1) things should be good.