|
Re: dunfell gcc-sanitizers-arm-8.3 fails to build
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]
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]
|
By
Sumit Garg
·
#50156
·
|
|
Extracting files and creating directory tar.gz's from yocto created root filesystem
#yocto
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
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
|
By
steve@...
·
#50155
·
|
|
Re: dunfell gcc-sanitizers-arm-8.3 fails to build
is gcc 8.3 the latest for linaro
is gcc 8.3 the latest for linaro
|
By
Khem Raj
·
#50154
·
|
|
Re: cannot build PDF docs
Rob,
I believe you are hitting a known bug: https://bugzilla.yoctoproject.org/show_bug.cgi?id=13767
regards,
Armin
Rob,
I believe you are hitting a known bug: https://bugzilla.yoctoproject.org/show_bug.cgi?id=13767
regards,
Armin
|
By
Armin Kuster
·
#50153
·
|
|
dunfell gcc-sanitizers-arm-8.3 fails to build
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
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
|
By
Ryan Harkin <ryan.harkin@...>
·
#50152
·
|
|
cannot build PDF docs
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
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
|
By
Rob Prowel
·
#50151
·
|
|
Re: one way hash analogy of yocto
Thanks for the prompt followup. Yeah, the two comments above are related in my nightmare so I'll address both of them together.
vendor has layers that I am NOT modifying, and unfortunately I'm not
Thanks for the prompt followup. Yeah, the two comments above are related in my nightmare so I'll address both of them together.
vendor has layers that I am NOT modifying, and unfortunately I'm not
|
By
Rob Prowel
·
#50150
·
|
|
Re: one way hash analogy of yocto
bitbake -e my-recipe ?
Maybe grep for the variable of interest?
When adding layers, only way to be sure is to actually review the layers
and their bbappends. I tend to BBMASK everything out which I
bitbake -e my-recipe ?
Maybe grep for the variable of interest?
When adding layers, only way to be sure is to actually review the layers
and their bbappends. I tend to BBMASK everything out which I
|
By
Mikko Rapeli
·
#50149
·
|
|
Re: one way hash analogy of yocto
Hi Robm
For location of bbappends and recipes, etc.:
bitbake-layers show-appends
bitbake-layers show-recipes
For variables:
bitbake <recipe> -e | more
and find the line starting with the variable
Hi Robm
For location of bbappends and recipes, etc.:
bitbake-layers show-appends
bitbake-layers show-recipes
For variables:
bitbake <recipe> -e | more
and find the line starting with the variable
|
By
Quentin Schulz
·
#50148
·
|
|
one way hash analogy of yocto
What I really need is information about introspection or the ability to query an existing yocto distro to return data about features included and more to the point, to understand EXACTLY where recipes
What I really need is information about introspection or the ability to query an existing yocto distro to return data about features included and more to the point, to understand EXACTLY where recipes
|
By
Rob Prowel
·
#50147
·
|
|
Re: [meta-security] Clamav libclammspack.so missing from image
Hi Armin,
So I found libmspack where you said it would be. I have done some more digging and talked to the Clamav developers.
This line in the recipe (--with-system-libmspack=${CLAMAV_USR_DIR})
Hi Armin,
So I found libmspack where you said it would be. I have done some more digging and talked to the Clamav developers.
This line in the recipe (--with-system-libmspack=${CLAMAV_USR_DIR})
|
By
yoc
·
#50146
·
|
|
Re: [bitbake-devel] [yocto] Stable Warrior branch
Hi Armin,
yes.
cu
Adrian
By
Adrian Bunk
·
#50145
·
|
|
Re: [swupdate] [meta-swupdate][PATCH] mtd-utils: Remove patchs
Hi Richard,
Yes, they are. My question was related to mtd recipe in OE-Core.
Agree both are correct, but as you said, it can be more messy to maintain in external layers if it is not possible to
Hi Richard,
Yes, they are. My question was related to mtd recipe in OE-Core.
Agree both are correct, but as you said, it can be more messy to maintain in external layers if it is not possible to
|
By
Stefano Babic
·
#50144
·
|
|
Re: [swupdate] [meta-swupdate][PATCH] mtd-utils: Remove patchs
Adding patches in bbappends is always going to be high maintenance. Are
these patches swupdate specific?
The recipes use "git" in the filename and then set a sepcific SRCREV
and set PV correctly.
Adding patches in bbappends is always going to be high maintenance. Are
these patches swupdate specific?
The recipes use "git" in the filename and then set a sepcific SRCREV
and set PV correctly.
|
By
Richard Purdie
·
#50143
·
|
|
Re: [swupdate] [meta-swupdate][PATCH] mtd-utils: Remove patchs
Hi Zheng,
I do not discuss abot the correctness of these patches (that I will
aplly to meta-swupdate, -master), but about mtd-utils version (for this
I pick up Richard in CC). There were in last
Hi Zheng,
I do not discuss abot the correctness of these patches (that I will
aplly to meta-swupdate, -master), but about mtd-utils version (for this
I pick up Richard in CC). There were in last
|
By
Stefano Babic
·
#50142
·
|
|
Re: [meta-virtualization][zeus][PATCH] kubernetes: CVE-2019-11254
Hi Bruce,
Sorry for late response. Due to something wrong of the mail server, I
just see your email.
I believe it can be applied successfully now. I find the
file://CVE-2020-8551.patch
Hi Bruce,
Sorry for late response. Due to something wrong of the mail server, I
just see your email.
I believe it can be applied successfully now. I find the
file://CVE-2020-8551.patch
|
By
Zhixiong Chi
·
#50141
·
|
|
[meta-selinux][PATCH] selinux-*.service: install to sysinit.target
The selinux-init/autorelabel/labeldev services have a constraint of
Before=sysinit.arget. So it is better to install them to sysinit.target
rather than multi-user.target.
Signed-off-by: Yi Zhao
The selinux-init/autorelabel/labeldev services have a constraint of
Before=sysinit.arget. So it is better to install them to sysinit.target
rather than multi-user.target.
Signed-off-by: Yi Zhao
|
By
Yi Zhao
·
#50140
·
|
|
Re: Building extensible SDK
Thanks Khem
I guess the eSDK is quite new then.
I have to ask my BSP supplier, about what version of Yocto they are using.
"The extensible SDK can currently only be built for the same architecture
Thanks Khem
I guess the eSDK is quite new then.
I have to ask my BSP supplier, about what version of Yocto they are using.
"The extensible SDK can currently only be built for the same architecture
|
By
Kjeld Flarup
·
#50139
·
|
|
Re: Remove connman package from yocto sdk.
try to find where its being added. Perhaps bitbake -g <image> should give you dependency file where you can check where it appear on right hand side of -> and equate to which package is bringing it in
try to find where its being added. Perhaps bitbake -g <image> should give you dependency file where you can check where it appear on right hand side of -> and equate to which package is bringing it in
|
By
Khem Raj
·
#50138
·
|
|
Re: How to enable preempt-rt in Yocto Zeus or Warrior?
These are custom options perhaps you have from your SDK provider, since variscite SOMs are based on IMX perhaps you also need to see if they are using linux-imx kernel and ensure that they have
These are custom options perhaps you have from your SDK provider, since variscite SOMs are based on IMX perhaps you also need to see if they are using linux-imx kernel and ensure that they have
|
By
Khem Raj
·
#50137
·
|