Hi, I am coming across the following issue when cross compiling: The install log indicates that host include and/or library paths were used A closer look at the log shows the following: Making

Hi Armin, that sounds good. Please keep me in the loop. BTW did you/the project create any kind of roadmap, just out of interest? BR Konrad

After a closer look I realised that there isnt a difference between the stock libmspack and the internal clamav libmspack so 1 can be ignored. I have submitted a patch for 3. I have also tested

Recipe provides INSTALL_CLAMAV_CVD flag to bypass clamav cvd db creation. During do_install this flag should be used to conditionally skip install of cvd db if needed. Signed-off-by: Charlie Davies

On 8/2/20 2:47 AM, Konrad Weihmann wrote: There are plans to broaden it. Some of this was came from another layer I have which did not belong. That would be awesome

Hi, is this just a demo, or are there plans to broaden the scope of this layer? To me it would make perfectly sense to have more of these features (besides sudo, openssh and root-pwd) and I'm willing

Ah, right, I see! Yes, I think I'll stick with that suggestion. Thanks for the explanation.

"I am trying to build SDK for raspberry While i am trying to build the SDK I got these errors, and now I am trying to solve this error can you please help me ~bobby Thank you soo much

<sumit.garg=linaro.org@...> wrote: It's using GCC 9.3 from OE core. If you wish to use Arm toolchain then you need to override the default OE core GCC version with Arm toolchain GCC

Arm GCC 9.3 toolchain isn't released yet (see here [1]). [1] https://developer.arm.com/tools-and-software/open-source-software/developer-tools/gnu-toolchain/gnu-a/downloads -Sumit

AFAIK, as upstream OE switches to a newer GCC version, it stops supporting older GCC versions. And since we are building here Arm toolchain from source and rely on OE core recipes, so it is

I'm sorry, that's incorrect: local.conf has an over-ride to specify 8.3. I've just removed it and now it's using 9.3. And it's building fine. Sumit, do you know if there's a reason for using 9.2 in

Hi Sumit, I can do that, I have no reason to use 8.3 other than it's the default. Is my problem a known issue with 8.3, or is moving to 9.2 a general suggestion? Thanks for the pointer.

Hi Khem, I assume so. I haven't attempted to change the default.

Hi Ryan, I would suggest you to switch to GCC 9.2 Arm toolchain for Dunfell. RPB does the same [1]. GCCVERSION = "arm-9.2" [1]

I am successfully creating a root file-system for my project (roko version). I am interested in performing modifications to the root file-system after it has been constructed with a recipe. I

is gcc 8.3 the latest for linaro

Rob, On 7/31/20 8:19 AM, Rob Prowel wrote: I believe you are hitting a known bug: https://bugzilla.yoctoproject.org/show_bug.cgi?id=13767 regards, Armin

Hello, I'm migrating from Warrior to Dunfell and I'm getting a curious build failure in gcc-sanitizers. Here's the full gory detail: https://pastebin.ubuntu.com/p/nh4cDKMvgS/ However, the main

Is there some magic to building the PDF versions of the yocto docs? I've tried on multiple machines running debian and differing versions of ubuntu and consistently the PDF docs fail to build. Font