Hi, openssl is tricky to update and requires backporting fixes for many, many recipes to get builds passing etc. Depending on project size, it may be possible to update only those components which you

#yocto #apt #raspberrypi

Any kind of patch if available to directly apply? I am getting error in gobject-introspection native that sha1 sha256 etc not found in usr/lib/python2 7/hashlib.py Sent from my Huawei phone

#yocto #apt #raspberrypi

Thanks for your prompt reply. But is not there any way similar to add support for TLS1.3 instead of moving to new yocto releases Sent from my Huawei phone

#yocto #apt #raspberrypi

Backporting core pieces across many yocto releases is basically impossible. You more or less end up having to move and integrate half of the stack, which is a herculean task. The correct way to approa

#yocto #apt #raspberrypi

I am using currently krogoth yocto for my current Arm based board. I am having currently openssl 1.0.2h and related recipes from current version but when I want to add TLs 1.3 that is openssl 1.1.1a/b

#yocto #apt #raspberrypi

Hi! I am having problems with my raspberry pi3 a+ yocto thud build when connecting a LTE E3372 modem. Sometimes it works but most of the times the startup of the LTE device interfere with services tha

#raspberrypi #yocto

error packaging nativesdk-glibc-locale when building at head in master today: Exception: KeyError: 'getpwuid(): uid not found: 1000' ERROR: Logfile of failure stored in: /home/parallels/poky/build/tmp

#yocto #raspberrypi

This would be a serious problem can you dive into it and see if we missed some Symlink

#raspberrypi

Hi Khem Replacing IMAGE_INSTALL += "i2c-tools vim" with IMAGE_INSTALL_append = " i2c-tools vim" in my local.conf solve the problem. More than half of the sources were rebuild. Thanks a lot. Now I foun

#raspberrypi

Hi Khem, Wojciech, Strange enough, I had the same behaviour a couple of days ago but I thought it was something on my setup. I built core-iage-full-cmdline on TOT, and systemd as init manager. The iss

#raspberrypi

Can you turn this into IMAGE_INSTALL_append = " i2c-tools vim"

#raspberrypi

Hi I am building simple image for my raspbery pi 3 A+ and connect to the pi via USB-UART converter and see the following in the console ... [ 2.071459] Run /bin/init as init process [ 2.076507] Run /b

#raspberrypi

Hey Ross, Thank you for your help. The problem was I wasn't adding nghttp2 in PACKAGECONFIG??=. Once I did it solved the http2 issue. Regards, Uzair

#yocto #raspberrypi

Yes! I have. I am going to try "PACKAGECONFIG[nghttp2] = "--with-nghttp2,--without-nghttp2,nghttp2"" thing with the help of documentation and will get back to you with my findings. Thanks, Uzair

#yocto #raspberrypi

Did you add meta-networking to bblayers.conf? Probably because the dependency ended up on a package you didn't actually instally. Also RDEPENDS are not in the sysroot, so the curl build wouldn't have

#yocto #raspberrypi

As I mentioned That I Cloned warrior branch of poky, meta-raspberrypi and meta-openembedded. nghttp2 recipe is already in my repository under "meta-openembedded/meta-networking/recipes-support/nghttp2

#yocto #raspberrypi

As Paul said: "You may need to find or write a recipe for that library." layers.openembedded.org is your friend here: https://layers.openembedded.org/layerindex/recipe/86423/ There's a recipe for this

#yocto #raspberrypi

I added nghttp2 into depends but it gave dependency chain error about nghttp2-native. "ERROR: Nothing PROVIDES 'nghttp2-native' (but virtual:native:/mnt/sdb1/yocto_exp/poky-warrior/meta/recipes-suppor

#yocto #raspberrypi

Looking at the link you gave [1], you probably need to use "--with-nghttp2=<PATH>" and add nghttp2 to DEPENDS. You may need to find or write a recipe for that library. [1]: https://serversforhackers.c

#yocto #raspberrypi

Hi All, While testing my image on raspberry pi3b, I found that curl doesn’t have http2 support. $ curl --http2 -I https://nghttp2.org/ # Unsupported protocol I tried to search for the solution and one

#yocto #raspberrypi