AnsweredAssumed Answered

3.14.28-1.0.0ga : Can't build meta-toolchain-qt5

Question asked by Yannick Calmettes on Apr 14, 2015
Latest reply on Apr 26, 2017 by Alejandro Acosta
Branched to a new discussion

Dear all,

 

On the new BSP release I can't acheive to build a toolchain for qt5. There at least two problems :

1- The git server used by qt recipes is down and replace by git://code.qt.io (already done in meta-qt5 DIZZY HEAD)

2- There is a conflict between bluez4 (layer in poky) and bluez5 (in meta-fsl-bsp-release) and i don't know how to resolve it. It seems that qtsystem use bluez4 but I don't know who needs bluez5.

 

When I build with a clean environment (imx6qsabresd) I have this error :

 

ERROR: Multiple .bb files are due to be built which each provide virtual/bluez (/home/user/Projets/VTX/VTX_BASE/LINUX/BSP_3.14.28-1.0.0-ga/sources/poky/meta/recipes-connectivity/bluez/bluez4_4.101.bb /home/user/Projets/VTX/VTX_BASE/LINUX/BSP_3.14.28-1.0.0-ga/sources/meta-fsl-bsp-release/imx/meta-fsl-bluez/recipes-connectivity/bluez5/bluez5_5.25.bb).

This usually means one provides something the other doesn't and should.

NOTE: Executing SetScene Tasks

NOTE: Executing RunQueue Tasks

ERROR: The recipe bluez4 is trying to install files into a shared area when those files already exist. Those files and their manifest location are:

   /home/user/Projets/VTX/VTX_BASE/LINUX/BSP_3.14.28-1.0.0-ga/build_imx6qsabresd/tmp/sysroots/imx6qsabresd/pkgdata/runtime/libasound-module-bluez

Matched in manifest-imx6qsabresd-bluez5.packagedata

/home/user/Projets/VTX/VTX_BASE/LINUX/BSP_3.14.28-1.0.0-ga/build_imx6qsabresd/tmp/sysroots/imx6qsabresd/pkgdata/runtime/libasound-module-bluez.packaged

Matched in manifest-imx6qsabresd-bluez5.packagedata

/home/user/Projets/VTX/VTX_BASE/LINUX/BSP_3.14.28-1.0.0-ga/build_imx6qsabresd/tmp/sysroots/imx6qsabresd/pkgdata/runtime-reverse/libasound-module-bluez

Matched in manifest-imx6qsabresd-bluez5.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.

ERROR: Function failed: sstate_task_postfunc

ERROR: Logfile of failure stored in: /home/user/Projets/VTX/VTX_BASE/LINUX/BSP_3.14.28-1.0.0-ga/build_imx6qsabresd/tmp/work/cortexa9hf-vfp-neon-poky-linux-gnueabi/bluez4/4.101-r11/temp/log.do_packagedata.15281

ERROR: Task 1738 (/home/user/Projets/VTX/VTX_BASE/LINUX/BSP_3.14.28-1.0.0-ga/sources/poky/meta/recipes-connectivity/bluez/bluez4_4.101.bb, do_packagedata) failed with exit code '1'

ERROR: The recipe bluez4 is trying to install files into a shared area when those files already exist. Those files and their manifest location are:

   /home/user/Projets/VTX/VTX_BASE/LINUX/BSP_3.14.28-1.0.0-ga/build_imx6qsabresd/tmp/sysroots/imx6qsabresd/lib/udev/hid2hci

Matched in manifest-imx6qsabresd-bluez5.populate_sysroot

/home/user/Projets/VTX/VTX_BASE/LINUX/BSP_3.14.28-1.0.0-ga/build_imx6qsabresd/tmp/sysroots/imx6qsabresd/usr/lib/libbluetooth.la

Matched in manifest-imx6qsabresd-bluez5.populate_sysroot

/home/user/Projets/VTX/VTX_BASE/LINUX/BSP_3.14.28-1.0.0-ga/build_imx6qsabresd/tmp/sysroots/imx6qsabresd/usr/lib/libbluetooth.so.3

Matched in manifest-imx6qsabresd-bluez5.populate_sysroot

/home/user/Projets/VTX/VTX_BASE/LINUX/BSP_3.14.28-1.0.0-ga/build_imx6qsabresd/tmp/sysroots/imx6qsabresd/usr/lib/libbluetooth.so

Matched in manifest-imx6qsabresd-bluez5.populate_sysroot

/home/user/Projets/VTX/VTX_BASE/LINUX/BSP_3.14.28-1.0.0-ga/build_imx6qsabresd/tmp/sysroots/imx6qsabresd/usr/lib/pkgconfig/bluez.pc

Matched in manifest-imx6qsabresd-bluez5.populate_sysroot

/home/user/Projets/VTX/VTX_BASE/LINUX/BSP_3.14.28-1.0.0-ga/build_imx6qsabresd/tmp/sysroots/imx6qsabresd/usr/include/bluetooth/bluetooth.h

Matched in manifest-imx6qsabresd-bluez5.populate_sysroot

/home/user/Projets/VTX/VTX_BASE/LINUX/BSP_3.14.28-1.0.0-ga/build_imx6qsabresd/tmp/sysroots/imx6qsabresd/usr/include/bluetooth/rfcomm.h

Matched in manifest-imx6qsabresd-bluez5.populate_sysroot

/home/user/Projets/VTX/VTX_BASE/LINUX/BSP_3.14.28-1.0.0-ga/build_imx6qsabresd/tmp/sysroots/imx6qsabresd/usr/include/bluetooth/hci_lib.h

Matched in manifest-imx6qsabresd-bluez5.populate_sysroot

/home/user/Projets/VTX/VTX_BASE/LINUX/BSP_3.14.28-1.0.0-ga/build_imx6qsabresd/tmp/sysroots/imx6qsabresd/usr/include/bluetooth/hidp.h

Matched in manifest-imx6qsabresd-bluez5.populate_sysroot

/home/user/Projets/VTX/VTX_BASE/LINUX/BSP_3.14.28-1.0.0-ga/build_imx6qsabresd/tmp/sysroots/imx6qsabresd/usr/include/bluetooth/cmtp.h

Matched in manifest-imx6qsabresd-bluez5.populate_sysroot

/home/user/Projets/VTX/VTX_BASE/LINUX/BSP_3.14.28-1.0.0-ga/build_imx6qsabresd/tmp/sysroots/imx6qsabresd/usr/include/bluetooth/hci.h

Matched in manifest-imx6qsabresd-bluez5.populate_sysroot

/home/user/Projets/VTX/VTX_BASE/LINUX/BSP_3.14.28-1.0.0-ga/build_imx6qsabresd/tmp/sysroots/imx6qsabresd/usr/include/bluetooth/sdp.h

Matched in manifest-imx6qsabresd-bluez5.populate_sysroot

/home/user/Projets/VTX/VTX_BASE/LINUX/BSP_3.14.28-1.0.0-ga/build_imx6qsabresd/tmp/sysroots/imx6qsabresd/usr/include/bluetooth/sco.h

Matched in manifest-imx6qsabresd-bluez5.populate_sysroot

/home/user/Projets/VTX/VTX_BASE/LINUX/BSP_3.14.28-1.0.0-ga/build_imx6qsabresd/tmp/sysroots/imx6qsabresd/usr/include/bluetooth/l2cap.h

Matched in manifest-imx6qsabresd-bluez5.populate_sysroot

/home/user/Projets/VTX/VTX_BASE/LINUX/BSP_3.14.28-1.0.0-ga/build_imx6qsabresd/tmp/sysroots/imx6qsabresd/usr/include/bluetooth/sdp_lib.h

Matched in manifest-imx6qsabresd-bluez5.populate_sysroot

/home/user/Projets/VTX/VTX_BASE/LINUX/BSP_3.14.28-1.0.0-ga/build_imx6qsabresd/tmp/sysroots/imx6qsabresd/usr/include/bluetooth/bnep.h

Matched in manifest-imx6qsabresd-bluez5.populate_sysroot

/home/user/Projets/VTX/VTX_BASE/LINUX/BSP_3.14.28-1.0.0-ga/build_imx6qsabresd/tmp/sysroots/imx6qsabresd/sysroot-providers/virtual_bluez

Matched in manifest-imx6qsabresd-bluez5.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.

ERROR: Function failed: sstate_task_postfunc

ERROR: Logfile of failure stored in: /home/user/Projets/VTX/VTX_BASE/LINUX/BSP_3.14.28-1.0.0-ga/build_imx6qsabresd/tmp/work/cortexa9hf-vfp-neon-poky-linux-gnueabi/bluez4/4.101-r11/temp/log.do_populate_sysroot.15282

ERROR: Task 1733 (/home/user/Projets/VTX/VTX_BASE/LINUX/BSP_3.14.28-1.0.0-ga/sources/poky/meta/recipes-connectivity/bluez/bluez4_4.101.bb, do_populate_sysroot) failed with exit code '1'

 

Don't hesitate to mail me if you need more info.

 

Best,

 

Yannick

Outcomes