Khem: Do I need to re-assign CC/CXX/CPP to point to CLANGCC, etc. in my environment-setup-coreI7-64-poky-linux script ? I thought I read somewhere that gcc was always the default compiler under the

Leon: Thank you for responding, however I am already doing these steps and environment appears to be setting up correctly... my problem seems to when running make after config. I too am using gcc

You should keep list on the copy while responding. It looks like you have some old Yocto revision and pulled in one recipe from master to it? Which Yocto revision is that? You

I changed the vwdial recipy file for what I've found on openembedded. I think now the error is only with wvstreams NOTE: Resolving any missing task queue dependencies ERROR: Nothing PROVIDES

Thank you, Vincent. I was finally able to make a .bbappend file and here is what I have made. FILESEXTRAPATHS_prepend := "${THISDIR}/files:" SRC_URI += "file://mongod \

Hi, Here's an example of mongodb_%.bbappend file: ----------------------------------------------------------------------------- FILESEXTRAPATHS_prepend := "${THISDIR}/files:" SRC_URI +=

From: Jens Rehsack <sno@...> Add recipe for companion of IBM Software TPM 2.0 - IBM's TPM 2.0 TSS. It's a user space TSS for TPM 2.0. Signed-off-by: Jens Rehsack <sno@...> ---

From: Jens Rehsack <sno@...> Update ibmswtpm2 from 1628 to 1637. Build 1637 Includes: * Increase NV memory size to match PC Client RSA 3072 requirements * Add and fix ACT support * Update

Hello Steven, you mention you use CMake with the Yocto (standard) SDK. After you sourced the SDK environment script, what is the output of "which cmake" ? Do you use the cmake toolchain

Yes, you got the recipe name wrong. It's wvdial -- Maciej PijanowskiEmbedded Systems EngineerGPG: 9963C36AAC3B2B46https://3mdeb.com | @3mdeb_com

Hi, First of all, thank you for accepting me to this mailing list. I got a Barix ipam400 OEM board, and now I've found myself in the situation that vwdial would not compile. The error message is this

its looking for tools in sdk dir, which is normal. I wonder if your apps cmake files should be using CC or CLANGCC to do linking. On Wed, Sep 9, 2020 at 8:58 AM Monsees, Steven C (US)

Thanks Bartosz, I sent a v2 series based on your feedback about BeagleBone Black. -Niko

Since dm-verity-image.bbclass effectively injects <DM_VERITY_IMAGE>:do_image_<DM_VERITY_IMAGE_TYPE> dependency for do_image_wic task, we can change verity rootfs artifact reference here from

Since IMAGE_LINGUAS defaults to 'en-us en-gb' and since localization is not needed on this type of purpose-specific initramfs image, reset the variable which helps by shaving off almost 700kB from

This removes following boot-time complaints from udevd regarding missing group declarations: [ 6.624454] udevd[163]: specified group 'tty' unknown [ 6.625340] udevd[163]: specified group

- revise declaration ordering as suggested by oe-stylize.py - sort PACKAGE_INSTALL entries in alphabetic order - split long command line in deploy_verity_hash() Signed-off-by: Niko Mauno

Switch from this layer's initramfs-dm-verity recipe to poky-provided initramfs-framework suite to manage veritysetup et al. This commit also removes initramfs-dm-verity recipe which is not referred

Introduce new STAGING_VERITY_DIR variable specific to this bbclass which defines the directory where the verity.env file is stored during <DM_VERITY_IMAGE>:do_image_<DM_VERITY_IMAGE_TYPE> task and

Add checks that include dm-verity specific kernel config fragment when dm-verity-img.bbclass is used. Signed-off-by: Niko Mauno <niko.mauno@...> ---