c_rehash implemented in perl is back (in history was moved to shell forsome time), so handle it inside the -misc package so just that one will carry the heavy runtime dependency on perl and not the wh

Sorry, new to the process, adding the pull URL here: https://git.yoctoproject.org/cgit/cgit.cgi/poky-contrib/log/?h=fedepell/bug14083 Cheers, F.

Hi, I think it would be interesting information to know "how" you change the value inside "u-boot-at91/sama5d3_xplained_nandflash_config". As every time you rebuild it may be redownloaded, you should

Hi David, If you change it directly, changes may not be taken into account for the rebuild. And if the package build gets retriggered, then the whole repository is deleted (including your local change

Add possibility, via PACKAGECONFIG variable, to enable cryptodev (hardware crypto acceleration) for gnutls in a very similar way as it is already present for openssl. Signed-off-by: Federico Pellegrin

Signed-off-by: Federico Pellegrin <fede@...> --- .../{aircrack-ng_1.3.bb => aircrack-ng_1.6.bb} | 8 +++++--- 1 file changed, 5 insertions(+), 3 deletions(-) rename recipes-security/aircrack-n

Hi, To skip the QA you can use: INSANE_SKIP_${PN} += "dev-elf" (or any QA part you'd like to skip, ie. dev-elf or dev-so ...) Cheers, Federico

Hi, Regarding the INSANE_SKIP: as that files get packed in the "-dev" package, you should probably then accordingly have: INSANE_SKIP_${PN}-dev += "dev-elf" Cheers, Federico

Hi Jupiter, /etc/profile and similar are interactive shell (/bash) concepts, not really system startup ones. So indeed: just on a login (be it local, ssh and so on) they are executed. If you want to e

Hi Jupiter, To centralize, agreed that you are using systemd, one way I could see is setting the variables in systemd-system.conf using the DefaultEnvironment directive, see: https://freedesktop.org/s

Hello, Running on a quite recent kernel (5.14.10 from Fedora 34) I've came across a problem when building util-linux (2.35.2) native, namely in the configure phase: configure: error: raw selected, but

Thanks Khem! Indeed I checked on master but got cheated by the web git interface and I was looking at an older commit :-/ Glad it is the right way to go and already solved on master! Cheers, Federico

Hello, Some more details would be needed (ie. you have systemd?), but this could be a good point to start: https://wiki.archlinux.org/title/Systemd-resolved (ie. see a bit down, like: https://wiki.arc

#yocto

Hi Jupiter, I cannot help you on the specific chip you ask, but responding to the second part of your question I have quite good experience with Microchip WILC1000/3000 on SDIO which, after a part sep

Hello, I've been playing around building a Yocto imagine based on kirkstone/master on the just released Fedora 36 beta test image. (just to give a few bits more details: builds a MX8X image, works per

Hello, Thanks for the feedback! Indeed the check is only on the "ldd --version" output which doesn't account for the libstdc++ and that explains it. As compared to Ubuntu 22.04, Fedora 36 actually has

Since ~16 months the base of meta-rust was merged into meta-oe, down to honister as far as I can see, and therefore the indications to use meta-rust are really not needed and may just create extra wor

Hi Armin, Sorry if it was unclear or if I misunderstood something. As far as I could see and tried as I had to build it yesterday, I can now build suricata without adding meta-rust as the rust support

Specific provider (ie. RPM or IPK) does "provide" just itself as a package to the system. This will cause the "-dev" package, which refers to the generic signing-keys and not the provider specific, to