Date   

Re: How to install rrdtool-per package?

ingemar0720@...
 

ok. I've found the cause. 

rrdtool-perl is empty so yocto doesn't generate rpm package for it. 

I create another .bbappend file and add `ALLOW_EMPTY_${PN}-perl = "1"` and it works.
Thanks for all the helps. 


Generating SDK and postinstall intercepts failure #sdk #yocto #toolchain

ppayeur01@...
 

Hi, 
 
I am having trouble generating the SDK for my image after upgrading from sumo to zeus. Here is an extract of my log.do_populate_sdk :

NOTE: Running intercept scripts:
NOTE: > Executing update_gio_module_cache-nativesdk intercept ...
NOTE: + '[' True = False -a nativesdk-qemuwrapper-cross '!=' nativesdk-qemuwrapper-cross ']'
+ qemu-x86_64 -r 3.2.0 -E LD_LIBRARY_PATH=/home/ops/next/poky/build/tmp/work/k700-poky-linux/dev-image-ops/1.0-r0/sdk/image/opt/ops-dist/1.1.0a/sysroots/x86_64-pokysdk-linux/usr/lib:/home/ops/next/poky/build/tmp/work/k700-poky-linux/dev-image-ops/1.0-r0/sdk/image/opt/ops-dist/1.1.0a/sysroots/x86_64-pokysdk-linux/lib -L /home/ops/next/poky/build/tmp/work/k700-poky-linux/dev-image-ops/1.0-r0/sdk/image /home/ops/next/poky/build/tmp/work/k700-poky-linux/dev-image-ops/1.0-r0/sdk/image/opt/ops-dist/1.1.0a/sysroots/x86_64-pokysdk-linux/usr/libexec/nativesdk-gio-querymodules /home/ops/next/poky/build/tmp/work/k700-poky-linux/dev-image-ops/1.0-r0/sdk/image/opt/ops-dist/1.1.0a/sysroots/x86_64-pokysdk-linux/usr/lib/gio/modules/
NOTE: > Executing update_pixbuf_cache intercept ...
NOTE: Exit code 1. Output:
/home/ops/next/poky/build/tmp/work/k700-poky-linux/dev-image-ops/1.0-r0/intercept_scripts-b57cc07ebc7fd06264e08c306ab25a797a944ba96238037685bb1148afe1842d/update_pixbuf_cache: line 11: /home/ops/next/poky/build/tmp/work/k700-poky-linux/dev-image-ops/1.0-r0/sdk/image/usr/lib/gdk-pixbuf-2.0/2.10.0/loaders/../loaders.cache: No such file or directory
 
ERROR: The postinstall intercept hook 'update_pixbuf_cache' failed, details in /home/ops/next/poky/build/tmp/work/k700-poky-linux/dev-image-ops/1.0-r0/temp/log.do_populate_sdk
DEBUG: Python function do_populate_sdk finished
 
Seems like update_pixbuf_cache cannot find the required loaders files. I am not sure why it looks in /sdk/image directly instead of the target or host rootfs in /sdk/image/opt/.../sysroots. In fact I am not sure why this postinstall intercept needs to run at all when generating the SDK.

As a bit of added info, when building my image prior to the SDK I had to manually add gdk-pixbuf to the rootfs via IMAGE_INSTALL for this intercept to work since the loaders files were missing. Also I noticed that some postinst intercepts were already failing before upgrading to zeus (including the update_pixbuf_cache one) but were only generating warnings.
 
Is it possible to disable this intercept as a quick (dirty) way to be able to build the SDK? In the long term I'd like to find out what causes this intercept to run and why the required tools are not added automatically to my image.

Any troubleshooting advice is appreciated.
 
Thank you,
 
Patrick
 


Re: #yocto #yocto

Tim Orling
 

The key error is this:
ERROR: Nothing PROVIDES 'core-image-sato'
core-image-sato was skipped: 'package-managementtools-debug' in IMAGE_FEATURES is not a valid image feature. 
So you need to figure out what is happening there.


On Wed, Jul 1, 2020 at 9:05 AM Pankaj Vinadrao Joshi <pankaj.vj@...> wrote:
Hi Quentin,
Thanks for response
I didnt got solution yet as previously u suggested to remove
hwcodecstools-debug but i after i faced one more issue with other features from core-image-sato.bb file but simply removing from there is ok,i did not got like why i am getting like so error which i didnt got earlier with the same image.Also kindly suggest why after logging trough ssh its asking for password though i have not set any password,where could be the problem??


The following packages have unmet dependencies: packagegroup-core-x11-base : Depends: packagegroup-core-x11-xserver but it is not going to be installed #yocto

Pankaj Vinadrao Joshi
 

Hi,
i am trying to build core-image-sato and i am using PACKAGE_CLASSES = "package_deb" but while building i am getting following error
pankaj@exaleap-Inspiron-3584:~/Oe-Raspberrypi4$ bitbake core-image-sato
Parsing recipes: 100% |######################################################################################################################################################################| Time: 0:01:56
Parsing of 2279 .bb files complete (0 cached, 2279 parsed). 3439 targets, 195 skipped, 0 masked, 0 errors.
NOTE: Resolving any missing task queue dependencies
 
Build Configuration:
BB_VERSION           = "1.46.0"
BUILD_SYS            = "x86_64-linux"
NATIVELSBSTRING      = "ubuntu-18.04"
TARGET_SYS           = "aarch64-oe-linux"
MACHINE              = "raspberrypi4-64"
DISTRO               = "Exaleap-arm-linux"
DISTRO_VERSION       = "Exaleap-arm-linux-r1.0.0"
TUNE_FEATURES        = "aarch64 cortexa72 crc crypto"
TARGET_FPU           = ""
meta                 = "master:982b7f98b8423236cc986346379b1bde3694f131"
meta-oe              
meta-python          
meta-networking      
meta-multimedia      
meta-perl            = "dunfell:e413c1ef621688e69bb7830bb3151ed23b30b73e"
meta-raspberrypi     = "master:5ac6f013339b0b1ab2d71f9f6af48a186e126c19"
meta-pankaj          = "<unknown>:<unknown>"
 
Initialising tasks: 100% |###################################################################################################################################################################| Time: 0:00:05
Sstate summary: Wanted 270 Found 0 Missed 270 Current 1913 (0% match, 87% complete)
NOTE: Executing Tasks
ERROR: core-image-sato-1.0-r0 do_rootfs: Unable to install packages. Command '/home/pankaj/Oe-Raspberrypi4/tmp-glibc/work/raspberrypi4_64-oe-linux/core-image-sato/1.0-r0/recipe-sysroot-native/usr/bin/apt-get  install --force-yes --allow-unauthenticated --no-remove apt bash bsdtar cmake dhcp-client dhcp-server dosfstools dpkg e2fsprogs git glibc-utils kernel-modules localedef lsb-release mtd-utils-ubifs mtools openssh os-release packagegroup-base-extended packagegroup-core-boot packagegroup-core-sdk packagegroup-core-ssh-openssh packagegroup-core-standalone-sdk-target packagegroup-core-tools-debug packagegroup-core-x11-base packagegroup-core-x11-sato parted pseudo psplash-raspberrypi python3-pip ruby run-postinsts unicode-ucd' returned 100:
Reading package lists...
Building dependency tree...
Reading state information...
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:
 
The following packages have unmet dependencies:
 packagegroup-core-x11-base : Depends: packagegroup-core-x11-xserver but it is not going to be installed
E: Unable to correct problems, you have held broken packages.
 
ERROR: Logfile of failure stored in: /home/pankaj/Oe-Raspberrypi4/tmp-glibc/work/raspberrypi4_64-oe-linux/core-image-sato/1.0-r0/temp/log.do_rootfs.12854
ERROR: Task (/home/pankaj/openembedded-core/meta/recipes-sato/images/core-image-sato.bb:do_rootfs) failed with exit code '1'
NOTE: Tasks Summary: Attempted 5894 tasks of which 5893 didn't need to be rerun and 1 failed.
 
Summary: 1 task failed:
  /home/pankaj/openembedded-core/meta/recipes-sato/images/core-image-sato.bb:do_rootfs
Summary: There was 1 ERROR message shown, returning a non-zero exit code.
 
when i am trying to build image without PACKAGE_CLASSES = "package_deb" i am able to buld i really dont have much knowledge about this can someone help??
 


Re: #yocto #yocto

Pankaj Vinadrao Joshi
 

Hi Quentin,
Thanks for response
I didnt got solution yet as previously u suggested to remove
hwcodecstools-debug but i after i faced one more issue with other features from core-image-sato.bb file but simply removing from there is ok,i did not got like why i am getting like so error which i didnt got earlier with the same image.Also kindly suggest why after logging trough ssh its asking for password though i have not set any password,where could be the problem??


Re: #yocto #yocto

Quentin Schulz
 

Hi Pankaj,

On Wed, Jul 01, 2020 at 08:36:50AM -0700, Pankaj Vinadrao Joshi wrote:
[...]
2) I have built the image without these configuration but after booting the image its asking for password for connecting from ssh thought i have not set any packages
i have included following features in local.conf file of build dir

EXTRA_IMAGE_FEATURES ?= "debug-tweaks"
ENABLE_UART = "1"
#EXTRA_IMAGE_FEATURES ?= "allow-empty-password allow-root-login"
CORE_IMAGE_EXTRA_INSTALL += "git ruby bsdtar pseudo os-release lsb-release cmake"
DISTRO_FEATURES_append = "opengl python3-pip"
DISTRO_FEATURES_append = " opengl python3-pip"
^ missing space

EXTRA_IMAGE_FEATURES_append += "src-pkgs package-management ssh-server-dropbear ssh-server-openssh stateless-rootfs "
PACKAGE_CLASSES = "package_deb"
IMAGE_INSTALL_append = " glibc-utils localedef unicode-ucd "
IMAGE_FEATURES_append = "tools-debug tools-sdk dev-pkgs"
IMAGE_FEATURES_append = " tools-debug tools-sdk dev-pkgs"
^ missing space

CORE_IMAGE_EXTRA_INSTALL += " kernel-modules bash e2fsprogs mtools parted dosfstools mtd-utils-ubifs openssh"
IMAGE_INSTALL_append += " dhcp-client dhcp-server python3-pip "
DISTRO ?= "Exaleap-arm-linux"
DISTRO ?= "exaleap-arm-linux"
^ avoid uppercase letter like the plague

can someone help me to ressolve this issue???
Please read when I answer your mails before asking the same question
again :)

Quentin


Re: ERROR: Nothing PROVIDES 'core-image-sato' #raspberrypi #yocto

Pankaj Vinadrao Joshi
 

Sorry this message was posted by mistake. 


#yocto #yocto

Pankaj Vinadrao Joshi
 

Hi,
i am building an image for RPI4 but while building core-image-sato i am getting the following error
pankaj@exaleap-Inspiron-3584:~/Oe-Raspberrypi4$ bitbake core-image-sato
Parsing recipes: 100% |######################################################################################################################################################################| Time: 0:01:56
Parsing of 2279 .bb files complete (0 cached, 2279 parsed). 3439 targets, 196 skipped, 0 masked, 0 errors.
ERROR: Nothing PROVIDES 'core-image-sato'
core-image-sato was skipped: 'hwcodecstools-debug' in IMAGE_FEATURES is not a valid image feature. Valid features: allow-empty-password allow-root-login bash-completion-pkgs dbg-pkgs debug-tweaks dev-pkgs doc doc-pkgs eclipse-debug empty-root-password hwcodecs nfs-client nfs-server package-management post-install-logging ptest-pkgs read-only-rootfs splash src-pkgs ssh-server-dropbear ssh-server-openssh stateless-rootfs staticdev-pkgs tools-debug tools-profile tools-sdk tools-testapps x11 x11-base x11-sato

later i have removed the hwcodecstools-debug feature from core-image-sato.bb then i got same above error for  ssh-server-dropbeartools-debug' likewise for all features (# IMAGE_FEATURES += "splash package-management x11-base x11-sato ssh-server-dropbear hwcodecs") from  core-image-sato.bb 

i am attaching detailed error message

ERROR: Nothing PROVIDES 'core-image-sato'
core-image-sato was skipped: 'hwcodecstools-debug' in IMAGE_FEATURES is not a valid image feature. Valid features: allow-empty-password allow-root-login bash-completion-pkgs dbg-pkgs debug-tweaks dev-pkgs doc doc-pkgs eclipse-debug empty-root-password hwcodecs nfs-client nfs-server package-management post-install-logging ptest-pkgs read-only-rootfs splash src-pkgs ssh-server-dropbear ssh-server-openssh stateless-rootfs staticdev-pkgs tools-debug tools-profile tools-sdk tools-testapps x11 x11-base x11-sato

This is error message when i removed  hwcodecstools-debug from 'core-image-sato
pankaj@exaleap-Inspiron-3584:~/Oe-Raspberrypi4$ bitbake core-image-sato
Loading cache: 100% |########################################################################################################################################################################| Time: 0:00:00
Loaded 3439 entries from dependency cache.
Parsing recipes: 100% |######################################################################################################################################################################| Time: 0:00:00
Parsing of 2279 .bb files complete (2274 cached, 5 parsed). 3439 targets, 196 skipped, 0 masked, 0 errors.
ERROR: Nothing PROVIDES 'core-image-sato'
core-image-sato was skipped: 'package-managementtools-debug' in IMAGE_FEATURES is not a valid image feature. Valid features: allow-empty-password allow-root-login bash-completion-pkgs dbg-pkgs debug-tweaks dev-pkgs doc doc-pkgs eclipse-debug empty-root-password hwcodecs nfs-client nfs-server package-management post-install-logging ptest-pkgs read-only-rootfs splash src-pkgs ssh-server-dropbear ssh-server-openssh stateless-rootfs staticdev-pkgs tools-debug tools-profile tools-sdk tools-testapps x11 x11-base x11-sato
 
Summary: There was 1 ERROR message shown, returning a non-zero exit code.

This is error message when i removed  package-managementtools-debug' and  x11-base x11-sato ssh-server-dropbear from 'core-image-sato
pankaj@exaleap-Inspiron-3584:~/Oe-Raspberrypi4$ bitbake core-image-sato
Loading cache: 100% |########################################################################################################################################################################| Time: 0:00:00
Loaded 3439 entries from dependency cache.
Parsing recipes: 100% |######################################################################################################################################################################| Time: 0:00:00
Parsing of 2279 .bb files complete (2274 cached, 5 parsed). 3439 targets, 196 skipped, 0 mask 0 errors.
ERROR: Nothing PROVIDES 'core-image-sato'
core-image-sato was skipped: 'splashtools-debug' in IMAGE_FEATURES is not a valid image feature. Valid features: allow-empty-password allow-root-login bash-completion-pkgs dbg-pkgs debug-tweaks dev-pkgs doc doc-pkgs eclipse-debug empty-root-password hwcodecs nfs-client nfs-server package-management post-install-logging ptest-pkgs read-only-rootfs splash src-pkgs ssh-server-dropbear ssh-server-openssh stateless-rootfs staticdev-pkgs tools-debug tools-profile tools-sdk tools-testapps x11 x11-base x11-sato

1) Now i have removed all the features from that .bb file why i am getting these errors??

2) I have built the image without these configuration but after booting the image its asking for password for connecting from ssh thought i have not set any packages
i have included following features in local.conf file of build dir

EXTRA_IMAGE_FEATURES ?= "debug-tweaks"
ENABLE_UART = "1"
#EXTRA_IMAGE_FEATURES ?= "allow-empty-password allow-root-login"
CORE_IMAGE_EXTRA_INSTALL += "git ruby bsdtar pseudo os-release lsb-release cmake"
DISTRO_FEATURES_append = "opengl python3-pip"
EXTRA_IMAGE_FEATURES_append += "src-pkgs package-management ssh-server-dropbear ssh-server-openssh stateless-rootfs "
PACKAGE_CLASSES = "package_deb"
IMAGE_INSTALL_append = " glibc-utils localedef unicode-ucd "
IMAGE_FEATURES_append = "tools-debug tools-sdk dev-pkgs"
CORE_IMAGE_EXTRA_INSTALL += " kernel-modules bash e2fsprogs mtools parted dosfstools mtd-utils-ubifs openssh"
IMAGE_INSTALL_append += " dhcp-client dhcp-server python3-pip "
DISTRO ?= "Exaleap-arm-linux"
 
can someone help me to ressolve this issue???


Re: How to install rrdtool-per package?

ingemar0720@...
 

Hi Quentin
I've execute command "bitbake rrdtool -e" to checked the result and find it's been set as I expected.

This rrdtool-perl is actually required by "rpimonitor", if I execute command "bitbake rpimonitor" and it would success.
But when I execute command "bitbake mydistro", it always say "nothing provides rrdtool-perl" at "do_rootfs" stage. 

Is there any other suggestion?

 


Re: Dunfell 3.1.1 gcc-sanitizers build failure

Joshua Watt
 

On Wed, Jul 1, 2020 at 9:47 AM MikeB <mabnhdev@gmail.com> wrote:

The rumors of my success were exaggerated. If performing a fresh build from scratch, the image build succeeds, but the populate_sdk still fails as in the original post. If I then do a 'bitbake -ccleansstate on gcc-source-9.3.0', the populate_sdk succeeds.
Ok. Are you using archiver.bbclass?


Mike

On Wed, Jul 1, 2020 at 6:45 AM MikeB <mabnhdev@gmail.com> wrote:

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!

On Tue, Jun 30, 2020 at 11:10 PM Steve Sakoman <steve@sakoman.com> wrote:

On Tue, Jun 30, 2020 at 5:08 PM Steve Sakoman via
lists.yoctoproject.org <steve=sakoman.com@lists.yoctoproject.org>
wrote:

On Tue, Jun 30, 2020 at 4:53 PM Joshua Watt <JPEWhacker@gmail.com> wrote:

On Tue, Jun 30, 2020 at 8:08 PM Joshua Watt <jpewhacker@gmail.com> wrote:

On Tue, Jun 30, 2020 at 4:56 PM MikeB <mabnhdev@gmail.com> wrote:

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 trying to build the SDK.

| cat: /data/mabnhdev/exos-yocto-dunfell/build/exos-arm64/tmp/work-shared/gcc-9.3.0-r0/gcc-9.3.0/gcc/defaults.h: No such file or directory
| WARNING: /data/mabnhdev/exos-yocto-dunfell/build/exos-arm64/tmp/work/aarch64-poky-linux/gcc-sanitizers/9.3.0-r0/temp/run.do_configure.31505:1 exit 1 from 'grep -v "\#endif.*GCC_DEFAULTS_H" > /data/mabnhdev/exos-yocto-dunfell/build/exos-arm64/tmp/work/aarch64-poky-linux/gcc-sanitizers/9.3.0-r0/gcc-9.3.0/build.aarch64-poky-linux.aarch64-poky-linux/gcc/defaults.h.new'
| ERROR: Execution of '/data/mabnhdev/exos-yocto-dunfell/build/exos-arm64/tmp/work/aarch64-poky-linux/gcc-sanitizers/9.3.0-r0/temp/run.do_configure.31505' failed with exit code 1:
| cat: /data/mabnhdev/exos-yocto-dunfell/build/exos-arm64/tmp/work-shared/gcc-9.3.0-r0/gcc-9.3.0/gcc/defaults.h: No such file or directory
| WARNING: /data/mabnhdev/exos-yocto-dunfell/build/exos-arm64/tmp/work/aarch64-poky-linux/gcc-sanitizers/9.3.0-r0/temp/run.do_configure.31505:1 exit 1 from 'grep -v "\#endif.*GCC_DEFAULTS_H" > /data/mabnhdev/exos-yocto-dunfell/build/exos-arm64/tmp/work/aarch64-poky-linux/gcc-sanitizers/9.3.0-r0/gcc-9.3.0/build.aarch64-poky-linux.aarch64-poky-linux/gcc/defaults.h.new'

At first, I thought this may be a dependency issue because I inherit "rm_work" to tidy up; but I tried a build without it - i.e. keeping all work around - and got the same failure.
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 archive.bbclass
(7a57e777597d7f66d065582cfb83cd8f9468f4af) where the archiving of
gcc-source raced with do_preconfigure and I'm wondering if it's
related
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.
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
Doh, I'm getting ahead of myself! I was thinking of another
classes/archiver patch that Joshua sent :-)

Steve


Re: Dunfell 3.1.1 gcc-sanitizers build failure

MikeB
 

The rumors of my success were exaggerated.  If performing a fresh build from scratch, the image build succeeds, but the populate_sdk still fails as in the original post.  If I then do a 'bitbake -ccleansstate on gcc-source-9.3.0', the populate_sdk succeeds.

Mike

On Wed, Jul 1, 2020 at 6:45 AM MikeB <mabnhdev@...> wrote:
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!

On Tue, Jun 30, 2020 at 11:10 PM Steve Sakoman <steve@...> wrote:
On Tue, Jun 30, 2020 at 5:08 PM Steve Sakoman via
lists.yoctoproject.org <steve=sakoman.com@...>
wrote:
>
> On Tue, Jun 30, 2020 at 4:53 PM Joshua Watt <JPEWhacker@...> wrote:
> >
> > On Tue, Jun 30, 2020 at 8:08 PM Joshua Watt <jpewhacker@...> wrote:
> > >
> > > On Tue, Jun 30, 2020 at 4:56 PM MikeB <mabnhdev@...> wrote:
> > > >
> > > > 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 trying to build the SDK.
> > > >
> > > > | cat: /data/mabnhdev/exos-yocto-dunfell/build/exos-arm64/tmp/work-shared/gcc-9.3.0-r0/gcc-9.3.0/gcc/defaults.h: No such file or directory
> > > > | WARNING: /data/mabnhdev/exos-yocto-dunfell/build/exos-arm64/tmp/work/aarch64-poky-linux/gcc-sanitizers/9.3.0-r0/temp/run.do_configure.31505:1 exit 1 from 'grep -v "\#endif.*GCC_DEFAULTS_H" > /data/mabnhdev/exos-yocto-dunfell/build/exos-arm64/tmp/work/aarch64-poky-linux/gcc-sanitizers/9.3.0-r0/gcc-9.3.0/build.aarch64-poky-linux.aarch64-poky-linux/gcc/defaults.h.new'
> > > > | ERROR: Execution of '/data/mabnhdev/exos-yocto-dunfell/build/exos-arm64/tmp/work/aarch64-poky-linux/gcc-sanitizers/9.3.0-r0/temp/run.do_configure.31505' failed with exit code 1:
> > > > | cat: /data/mabnhdev/exos-yocto-dunfell/build/exos-arm64/tmp/work-shared/gcc-9.3.0-r0/gcc-9.3.0/gcc/defaults.h: No such file or directory
> > > > | WARNING: /data/mabnhdev/exos-yocto-dunfell/build/exos-arm64/tmp/work/aarch64-poky-linux/gcc-sanitizers/9.3.0-r0/temp/run.do_configure.31505:1 exit 1 from 'grep -v "\#endif.*GCC_DEFAULTS_H" > /data/mabnhdev/exos-yocto-dunfell/build/exos-arm64/tmp/work/aarch64-poky-linux/gcc-sanitizers/9.3.0-r0/gcc-9.3.0/build.aarch64-poky-linux.aarch64-poky-linux/gcc/defaults.h.new'
> > > >
> > > > At first, I thought this may be a dependency issue because I inherit "rm_work" to tidy up; but I tried a build without it - i.e. keeping all work around - and got the same failure.
> > >
> > > 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 archive.bbclass
> > > (7a57e777597d7f66d065582cfb83cd8f9468f4af) where the archiving of
> > > gcc-source raced with do_preconfigure and I'm wondering if it's
> > > related
> >
> > 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.
>
> 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

Doh, I'm getting ahead of myself! I was thinking of another
classes/archiver patch that Joshua sent :-)

Steve


Re: How to install rrdtool-per package?

Quentin Schulz
 

On Wed, Jul 01, 2020 at 07:26:00AM -0700, ingemar0720@gmail.com wrote:
On Wed, Jul 1, 2020 at 05:27 AM, "Josef Holzmayr" <holzmayr@rsi-elektrotechnik.de> wrote:


Howdy!

Am 01.07.2020 um 14:05 schrieb ingemar0720@gmail.com:

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"
Please see

https://www.yoctoproject.org/docs/3.1/ref-manual/ref-manual.html#var-PACKAGECONFIG


Section "configuration file"

I've added "PACKAGECONFIG_pn-rrdtool" into my distro conf file but still get same result.

I also tried adding .bbappend but it doesn't help.

My distro conf file is in below, could you see any issue in it?

*include conf/distro/poky.conf*
*DISTRO = "rpi"*
*DISTRO_NAME = "rpi"*
*DISTRO_VERSION = "1.0"*

*PACKAGECONFIG_pn-rrdtool = "perl systemd"*

*# Use systemd as init manager*
*DISTRO_FEATURES_append = " virtualization systemd bluez5 bluetooth wifi ssh-server-openssl"*
*DISTRO_FEATURES_BACKFILL_CONSIDERED += "sysvinit"*
*VIRTUAL-RUNTIME_init_manager = "systemd"*
*VIRTUAL-RUNTIME_initscripts = "systemd-compat-units"*
bitbake rrdtool -e and look for the line starting with PACKAGECONFIG.
CHeck it's set to what you want, if not, look the lines above to
understand why it's not set "correctly".

Quentin


Re: How to install rrdtool-per package?

ingemar0720@...
 

On Wed, Jul 1, 2020 at 05:27 AM, "Josef Holzmayr" <holzmayr@...> wrote:
Howdy!

Am 01.07.2020 um 14:05 schrieb ingemar0720@...:
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"
Please see

https://www.yoctoproject.org/docs/3.1/ref-manual/ref-manual.html#var-PACKAGECONFIG

Section "configuration file"

I've added "PACKAGECONFIG_pn-rrdtool" into my distro conf file but still get same result.

I also tried adding .bbappend but it doesn't help.

My distro conf file is in below, could you see any issue in it?


include conf/distro/poky.conf
DISTRO = "rpi"
DISTRO_NAME = "rpi"
DISTRO_VERSION = "1.0"
 
PACKAGECONFIG_pn-rrdtool = "perl systemd"
 
# Use systemd as init manager
DISTRO_FEATURES_append = " virtualization systemd bluez5 bluetooth wifi ssh-server-openssl"
DISTRO_FEATURES_BACKFILL_CONSIDERED += "sysvinit"
VIRTUAL-RUNTIME_init_manager = "systemd"
VIRTUAL-RUNTIME_initscripts = "systemd-compat-units"


Greetz

--
_____________________________________________________________
R-S-I Elektrotechnik GmbH & Co. KG
Woelkestrasse 11
D-85301 Schweitenkirchen
Fon: +49 8444 9204-0
Fax: +49 8444 9204-50
www.rsi-elektrotechnik.de

_____________________________________________________________
Amtsgericht Ingolstadt - GmbH: HRB 191328 - KG: HRA 170363
Geschäftsführer: Dr.-Ing. Michael Sorg, Dipl.-Ing. Franz Sorg
USt-IdNr.: DE 128592548


Re: ERROR: Nothing PROVIDES 'core-image-sato' #raspberrypi #yocto

Quentin Schulz
 

Hi,

On Wed, Jul 01, 2020 at 07:10:34AM -0700, Pankaj Vinadrao Joshi wrote:
Hi,
i am building an image for RPI4
You have probably added core-image-sato to DEPENDS which is incorrect.
You can't add an image recipe as a dependency.

Quentin


Re: ERROR: Nothing PROVIDES 'core-image-sato' #raspberrypi #yocto

Rudolf J Streif
 

Pankaj,

On 7/1/20 7:10 AM, Pankaj Vinadrao Joshi wrote:
Hi,
i am building an image for RPI4

Can you please provide the entire error message?

:rjs


    
-- 
-----
Rudolf J Streif
CEO/CTO ibeeto
+1.855.442.3386 x700


Re: How to install rrdtool-per package?

Josef Holzmayr <holzmayr@...>
 

Howdy!

Am 01.07.2020 um 14:05 schrieb ingemar0720@gmail.com:
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"
Please see

https://www.yoctoproject.org/docs/3.1/ref-manual/ref-manual.html#var-PACKAGECONFIG

Section "configuration file"

Greetz

--
_____________________________________________________________
R-S-I Elektrotechnik GmbH & Co. KG
Woelkestrasse 11
D-85301 Schweitenkirchen
Fon: +49 8444 9204-0
Fax: +49 8444 9204-50
www.rsi-elektrotechnik.de

_____________________________________________________________
Amtsgericht Ingolstadt - GmbH: HRB 191328 - KG: HRA 170363
Geschäftsführer: Dr.-Ing. Michael Sorg, Dipl.-Ing. Franz Sorg
USt-IdNr.: DE 128592548


Re: How to install rrdtool-per package?

ingemar0720@...
 

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"

 


Re: How to install rrdtool-per package?

Josef Holzmayr <holzmayr@...>
 

Howdy!

Am 01.07.2020 um 13:04 schrieb ingemar0720@gmail.com:
Hello Josef
Thanks for you reply!
From your link, it seems rrdtool recipe already give an alias as `rrdtool-perl`, is it correct?
Exactly. If activated, then the rrdtool recipe already procides the rrdtool-perl package.

Then shall I add PACKAGECONFIG in .bbappend file for rrdtool? Or i shall add in my own recipe?
The correct place to do this is your DISTRO conf file.

Greetz

--
_____________________________________________________________
R-S-I Elektrotechnik GmbH & Co. KG
Woelkestrasse 11
D-85301 Schweitenkirchen
Fon: +49 8444 9204-0
Fax: +49 8444 9204-50
www.rsi-elektrotechnik.de

_____________________________________________________________
Amtsgericht Ingolstadt - GmbH: HRB 191328 - KG: HRA 170363
Geschäftsführer: Dr.-Ing. Michael Sorg, Dipl.-Ing. Franz Sorg
USt-IdNr.: DE 128592548


Re: How to install rrdtool-per package?

ingemar0720@...
 

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 shall add in my own recipe?


Re: Dunfell 3.1.1 gcc-sanitizers build failure

MikeB
 

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!

On Tue, Jun 30, 2020 at 11:10 PM Steve Sakoman <steve@...> wrote:
On Tue, Jun 30, 2020 at 5:08 PM Steve Sakoman via
lists.yoctoproject.org <steve=sakoman.com@...>
wrote:
>
> On Tue, Jun 30, 2020 at 4:53 PM Joshua Watt <JPEWhacker@...> wrote:
> >
> > On Tue, Jun 30, 2020 at 8:08 PM Joshua Watt <jpewhacker@...> wrote:
> > >
> > > On Tue, Jun 30, 2020 at 4:56 PM MikeB <mabnhdev@...> wrote:
> > > >
> > > > 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 trying to build the SDK.
> > > >
> > > > | cat: /data/mabnhdev/exos-yocto-dunfell/build/exos-arm64/tmp/work-shared/gcc-9.3.0-r0/gcc-9.3.0/gcc/defaults.h: No such file or directory
> > > > | WARNING: /data/mabnhdev/exos-yocto-dunfell/build/exos-arm64/tmp/work/aarch64-poky-linux/gcc-sanitizers/9.3.0-r0/temp/run.do_configure.31505:1 exit 1 from 'grep -v "\#endif.*GCC_DEFAULTS_H" > /data/mabnhdev/exos-yocto-dunfell/build/exos-arm64/tmp/work/aarch64-poky-linux/gcc-sanitizers/9.3.0-r0/gcc-9.3.0/build.aarch64-poky-linux.aarch64-poky-linux/gcc/defaults.h.new'
> > > > | ERROR: Execution of '/data/mabnhdev/exos-yocto-dunfell/build/exos-arm64/tmp/work/aarch64-poky-linux/gcc-sanitizers/9.3.0-r0/temp/run.do_configure.31505' failed with exit code 1:
> > > > | cat: /data/mabnhdev/exos-yocto-dunfell/build/exos-arm64/tmp/work-shared/gcc-9.3.0-r0/gcc-9.3.0/gcc/defaults.h: No such file or directory
> > > > | WARNING: /data/mabnhdev/exos-yocto-dunfell/build/exos-arm64/tmp/work/aarch64-poky-linux/gcc-sanitizers/9.3.0-r0/temp/run.do_configure.31505:1 exit 1 from 'grep -v "\#endif.*GCC_DEFAULTS_H" > /data/mabnhdev/exos-yocto-dunfell/build/exos-arm64/tmp/work/aarch64-poky-linux/gcc-sanitizers/9.3.0-r0/gcc-9.3.0/build.aarch64-poky-linux.aarch64-poky-linux/gcc/defaults.h.new'
> > > >
> > > > At first, I thought this may be a dependency issue because I inherit "rm_work" to tidy up; but I tried a build without it - i.e. keeping all work around - and got the same failure.
> > >
> > > 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 archive.bbclass
> > > (7a57e777597d7f66d065582cfb83cd8f9468f4af) where the archiving of
> > > gcc-source raced with do_preconfigure and I'm wondering if it's
> > > related
> >
> > 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.
>
> 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

Doh, I'm getting ahead of myself! I was thinking of another
classes/archiver patch that Joshua sent :-)

Steve

4001 - 4020 of 53814