Howdy! Am 01.07.2020 um 14:05 schrieb ingemar0720@...: Please see https://www.yoctoproject.org/docs/3.1/ref-manual/ref-manual.html#var-PACKAGECONFIG Section "configuration file" Greetz --

On Wed, Jul 1, 2020 at 04:46 AM, Josef Holzmayr wrote: The correct place to do this is your DISTRO conf file. Is this the correct way to set up it? PACKAGECONFIG_pn-rrdtool="rrdtool rrdtool-perl"

Howdy! Am 01.07.2020 um 13:04 schrieb ingemar0720@...: Exactly. If activated, then the rrdtool recipe already procides the rrdtool-perl package. The correct place to do this is your DISTRO

Hello Josef Thanks for you reply! From your link, it seems rrdtool recipe already give an alias as `rrdtool-perl`, is it correct? Then shall I add PACKAGECONFIG in .bbappend file for rrdtool? Or i

The combination of the https://lists.openembedded.org/g/openembedded-core/message/140161 and a 'bitbake -ccleansstate on gcc-source-9.3.0' has gotten me back on track. Thank you all for the help!

Howdy! Looks very much like you'll need to set up PACKAGECONFIG of rrdtool, then it should provide rrdtool-perl. See also:

My Yocto build failed and it seems to be looking for "rrdtool-perl" package. I've added package "rrdtool" into my "INSTALL_APPEND" variable but it still fail. The logs is in below. Could someone

Hi Quentin That was indeed the problem. The reason that my code was not working as expected was not in the devtool flow but in my code :-). So now on to debugging my real problem. Thanks a

Hi, My comments are in-line Is your work available somewhere in the public? I would like to give it a try with dunfell 3.1.1 and influxdb.[1] Also it would be interesting what happens if you include

On Tue, Jun 30, 2020 at 5:08 PM Steve Sakoman via lists.yoctoproject.org <steve=sakoman.com@...> wrote: Doh, I'm getting ahead of myself! I was thinking of another classes/archiver

That patch came in after the 3.1.1 release, but it is present in the dunfell branch so it will make it into 3.1.2 Steve

I believe I have fixed this in https://lists.openembedded.org/g/openembedded-core/message/140161, please try it out to make sure it solves your issue as well.

I've encountered a similar error just today when switching SDKMACHINE. Are you using archive.bbclass by any chance (INHERIT += "archive")? I just recently fixed a bug in

Stephen, On 6/30/20 4:28 PM, Stephen Jolley wrote: Thanks for sending this out. Is there any priority to these that may help the community pick off the ones

All, YP M+ or high bugs which moved to a new milestone in WW26 are listed below: Priority Bug ID Short Description Changer Owner Was Became High 13947 buildtools checksum files are named

All, The below were the owners of enhancements or bugs closed during the last

try to do a bitbake -ccleansstate on gcc-source-9.3.0 >

All, The triage team is starting to try and collect up and classify bugs which a newcomer to the project would be able to work on in a way which means people can find them. They're being listed on

All, Below is the list as of top 38 bug owners as of the end of WW26 of who have open medium or higher bugs and enhancements against YP 3.2. There are 86 possible work days left until the final

I recently tried upgrading from 3.1.0 to 3.1.1. I'm not sure if this is a bug or just my problem. I maintain five different architectures and all five have the same failure in gcc-sanitizers as I'm