Alexander Kanavin:
> You can use bbappend to instead replace the standard files with the ones
> that you want installed. Or you can add PROVIDES = "initscripts" to your
> recipe with the 'custom' initscripts, and set
> PREFERRED_PROVIDER_initscripts = "my-custom-initscripts" to have that
> installed.

If I try that, I get a different error:

ERROR: The recipe base-files-emperor is trying to install files into a shared 
area when those files already exist. Those files and their manifest location 
are:
   
/home/jdi/develop/yocto/build/tmp/sysroots/emperor/sysroot-providers/initscripts
 Matched in manifest-emperor-initscripts.populate_sysroot
Please verify which recipe should provide the above files.
The build has stopped as continuing in this scenario WILL break things, if not 
now, possibly in the future (we've seen builds fail several months later). If 
the system knew how to recover from this automatically it would however there 
are several different scenarios which can result in this and we don't know 
which one this is. It may be you have switched providers of something like 
virtual/kernel (e.g. from linux-yocto to linux-yocto-dev), in that case you 
need to execute the clean task for both recipes and it will resolve this error. 
It may be you changed DISTRO_FEATURES from systemd to udev or vice versa. 
Cleaning those recipes should again resolve this error however switching 
DISTRO_FEATURES on an existing build directory is not supported, you should 
really clean out tmp and rebuild (reusing sstate should be safe). It could be 
the overlapping files detected are harmless in which case adding them to 
SSTATE_DUPWHITELIST may be the correct solution. It could also be your buil
 d is including two different conflicting versions of things (e.g. bluez 4 and 
bluez 5 and the correct solution for that would be to resolve the conflict. If 
in doubt, please ask on the mailing list, sharing the error and filelist above.
ERROR: If the above message is too much, the simpler version is you're advised 
to wipe out tmp and rebuild (reusing sstate is fine). That will likely fix 
things in most (but not all) cases.
ERROR: Function failed: sstate_task_postfunc
ERROR: Logfile of failure stored in: 
/home/jdi/develop/yocto/build/tmp/work/armv7a-vfp-neon-poky-linux-gnueabi/base-files-emperor/1.0-r0/temp/log.do_populate_sysroot.8244
ERROR: Task 676 
(/home/jdi/develop/yocto/meta-fifthplay-bsp/recipes-fifthplay-bsp/base-files-emperor/base-files-emperor.bb,
 do_populate_sysroot) failed with exit code '1'

Note: base-files-emperor is the package with the custom init scripts. I added:

PROVIDES = "initscripts"

And in conf/machine/emperor.conf, I added:

PREFERRED_PROVIDER_initscripts = "base-files-emperor"

Jef
Disclaimer

This e-mail and its attachments is intended only for the person(s) or entity to 
which it is addressed. If you receive this e-mail by mistake, please delete 
this e-mail from your system and destroy all copies of it. It may contain 
confidential and/or privileged information. You should not copy it or use it 
for any purpose nor disclose its contents to any person unless allowed by a 
written document between the sender and the addressee.
-- 
_______________________________________________
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

Reply via email to