我有一个基于Yocto的Gumstix板的Linux映像。该图像包括Bluez5蓝牙堆栈。
的local.conf：
... DISTRO_FEATURES_append = " bluetooth bluez5" ...
这成功构建了一个图像，我可以在CLI中使用蓝牙模块。 我想在Python中使用蓝牙模块，所以我添加了pybluez支持 -
myimage.bb：
... PYTHON_INSTALL_append = "python-pybluez \" ...
python_pybluez.bb：
DESCRIPTION = "Python bindings for the Linux Bluetooth stack"
SECTION = "devel/python"
DEPENDS = "bluez5"
LICENSE = "GPL"
SRC_URI = "https://github.com/karulis/pybluez/archive/master.zip"
SRC_URI[md5sum] = "37733f35ad5a0522b86fe39467481fd1"
SRC_URI[sha256sum] = "8e7e5e4e343da7e0ec2cd37b6dc12ee77da8e4c0863dd8a2d03ab06f9b657238"
S = "${WORKDIR}/PyBluez-${PV}"
inherit distutils
当bitbaked和构建失败时，这会导致大量冲突：
NOTE: Preparing RunQueue
ERROR: Multiple .bb files are due to be built which each provide bluez-hcidump (/home/parallels/yocto/poky/meta/recipes-connectivity/bluez5/bluez5_5.28.bb /home/parallels/yocto/poky/meta/recipes-connectivity/bluez/bluez-hcidump_2.5.bb).
This usually means one provides something the other doesn't and should.
NOTE: Executing SetScene Tasks
ERROR: The recipe bluez5 is trying to install files into a shared area when those files already exist. Those files and their manifest location are:
/media/parallels/build/tmp/sysroots/overo/pkgdata/runtime-reverse/libasound-module-bluez
Matched in manifest-overo-bluez4.packagedata
/media/parallels/build/tmp/sysroots/overo/pkgdata/runtime/libasound-module-bluez.packaged
Matched in manifest-overo-bluez4.packagedata
/media/parallels/build/tmp/sysroots/overo/pkgdata/runtime/libasound-module-bluez
Matched in manifest-overo-bluez4.packagedata
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 build 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.
WARNING: Logfile for failed setscene task is /media/parallels/build/tmp/work/cortexa8hf-vfp-neon-poky-linux-gnueabi/bluez5/5.28-r0/temp/log.do_packagedata_setscene.16687
WARNING: Setscene task 803 (/home/parallels/yocto/poky/meta/recipes-connectivity/bluez5/bluez5_5.28.bb, do_packagedata_setscene) failed with exit code '1' - real task will be run instead
ERROR: The recipe bluez5 is trying to install files into a shared area when those files already exist. Those files and their manifest location are:
/media/parallels/build/tmp/sysroots/overo/usr/lib/libbluetooth.so
Matched in manifest-overo-bluez4.populate_sysroot
/media/parallels/build/tmp/sysroots/overo/usr/lib/libbluetooth.la
Matched in manifest-overo-bluez4.populate_sysroot
/media/parallels/build/tmp/sysroots/overo/usr/lib/libbluetooth.so.3
Matched in manifest-overo-bluez4.populate_sysroot
/media/parallels/build/tmp/sysroots/overo/usr/lib/pkgconfig/bluez.pc
Matched in manifest-overo-bluez4.populate_sysroot
/media/parallels/build/tmp/sysroots/overo/usr/include/bluetooth/sdp.h
Matched in manifest-overo-bluez4.populate_sysroot
/media/parallels/build/tmp/sysroots/overo/usr/include/bluetooth/bnep.h
Matched in manifest-overo-bluez4.populate_sysroot
/media/parallels/build/tmp/sysroots/overo/usr/include/bluetooth/cmtp.h
Matched in manifest-overo-bluez4.populate_sysroot
/media/parallels/build/tmp/sysroots/overo/usr/include/bluetooth/hci.h
Matched in manifest-overo-bluez4.populate_sysroot
/media/parallels/build/tmp/sysroots/overo/usr/include/bluetooth/rfcomm.h
Matched in manifest-overo-bluez4.populate_sysroot
/media/parallels/build/tmp/sysroots/overo/usr/include/bluetooth/bluetooth.h
Matched in manifest-overo-bluez4.populate_sysroot
/media/parallels/build/tmp/sysroots/overo/usr/include/bluetooth/hci_lib.h
Matched in manifest-overo-bluez4.populate_sysroot
/media/parallels/build/tmp/sysroots/overo/usr/include/bluetooth/l2cap.h
Matched in manifest-overo-bluez4.populate_sysroot
/media/parallels/build/tmp/sysroots/overo/usr/include/bluetooth/sco.h
Matched in manifest-overo-bluez4.populate_sysroot
/media/parallels/build/tmp/sysroots/overo/usr/include/bluetooth/hidp.h
Matched in manifest-overo-bluez4.populate_sysroot
/media/parallels/build/tmp/sysroots/overo/usr/include/bluetooth/sdp_lib.h
Matched in manifest-overo-bluez4.populate_sysroot
/media/parallels/build/tmp/sysroots/overo/sysroot-providers/bluez-hcidump
Matched in manifest-overo-bluez-hcidump.populate_sysroot
/media/parallels/build/tmp/sysroots/overo/lib/udev/hid2hci
Matched in manifest-overo-bluez4.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 build 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.
看起来pybluez依赖于整个Bluez4食谱堆＆amp;图书馆与Bluez5同行发生冲突。通过强制pybluez使用Bluez5版本解决这个问题是否正确 - 如果是这样，如何以及在何处将其指定给Bitbake - 如果没有，是否可以在Yocto Linux系统中使用pybluez和Bluez5？
答案 0 :(得分：1)
看起来pybluez依赖于整个Bluez4食谱堆＆amp;库
根据您显示的内容，这是不正确的。你的python-pybluez配方只依赖于bluez5（和distutils带来的python东西）。 Yocto可能会根据链接神奇地将运行时依赖项添加到您的包中，但在这种情况下，您会收到有关可能缺少构建时DEPENDS的警告。
我认为你使用的图像更有可能包含bluez4包（也许它已经老了或者它们只是没有更新）和python-pybluez拖动bluez5会破坏它。
哦，忘了牛肉：你注意到消息的结束：你被建议消灭tmp并重建（重用sstate很好） - 单独构建python-pybluez食谱应该如果您只是擦拭TMPDIR并再次构建，请继续。如果您的图像确实包含bluez4
，您仍需要在创建图像之前处理冲突