friend asked me about the options for a risc-v dev kit that worked with YP, and i'm aware of the meta-riscv layer, but wherever i looked, it seems like risc-v dev kits have a very short life span,

bump lexical-core to 0.6.8 Signed-off-by: Armin Kuster <akuster808@...> --- recipes-ids/suricata/{libhtp_0.5.38.bb => libhtp_0.5.39.bb} | 2 +- recipes-ids/suricata/{suricata_6.0.3.bb =>

Hi team, I get this error… ERROR:Task do_build in /home/dwatkins/workspace/mgos/apollo17/upstream/yocto/poky/meta/recipes-core/images/core-image-minimal.bb depends upon non-existent task

Alexander Kanavin <alex.kanavin@...> writes: https://english.stackexchange.com/questions/535153/what-is-the-difference-between-cancel-and-abort | Cancel implies the action is rescinded before

Cancel is the same as abort: a request to immediately stop the operation (or not even start it) without reaching the originally requested outcome. Halt implies the operation is not going to continue

Bryan Evenson <bevenson@...> writes: mmmh.... for me as a developer (and non-native english speaker), "cancel" means some ordered ending of an operation. But the condition above causes an

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

Enrico,

Alexander Kanavin <alex.kanavin@...> writes: Yes; these are terms. But it should be possible to understand the meaning of these terms without using a special "inclusivenaming" dictionary.

I'm not taking a stand here, but just providing the context for where the push for avoidance of 'abort' comes from: https://inclusivenaming.org/word-lists/tier-1/ Keep in mind that for non-native

"Jon Mason" <jdmason@...> writes: I am not an native english speaker, but for "HALT" I will have to think twice whether it will pause the operation or abort it. I would stay at "ABORT" because

Remove unneeded go-binary-native recipe, as the 1.17 version of it is used to bootstrap go instead. Signed-off-by: Alexander Kanavin <alex@...> --- .../{go-1.16.10.inc => go-1.16.13.inc}

(copy from external source: git: https://git.yoctoproject.org/poky/ archive: 472a99447fe0f89bbdb959c1d9b7f67f8a122935 copy: meta/recipes-devtools/go -->

Hello Khem, Please excuse that my question was so unspecific. Does it make a functional difference from which library the TLS support comes from? Best regards, Matthias

This looks to be in good shape. Thank you to the reviewers for some excellent variable names.

This is a follow up to the Inclusive Language email I sent out on January 24 (see https://lore.kernel.org/yocto/CAPoiz9wL16OTzxNHdw_5-L72GOHkhhM0--WZF7An071cx6sr_A@.../). I'm adding a

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

Hello together, I can "fix" the bug by switching from gnutls to openssl: PACKAGECONFIG:remove = "gnutls" PACKAGECONFIG:append = " openssl" Can anyone explain this? What exactly does the change to

Wiki: https://wiki.yoctoproject.org/wiki/Bug_Triage Attendees: Alejandro, Alexandre, Andrei, Armin, Bruce, Daiane, Michael, Pavel, Randy, Richard, Saul, Stephen, Steve, Tim,

Is there a CPP conflict due to : ./tmp/work/corei7-64-poky-linux/intel-graphics-compiler/1.0.11-r0/git/inc/common/UFO/portable_compiler.h Is this a name space issue ?