[meta-freescale] With imx-3.14.52-1.1.0_ga, error with fsl-image-qt5. bluez4 is trying to install files into a shared area when those files already exist.

Paul Knopf pknopf at medxchange.com
Thu Mar 17 00:20:40 PDT 2016


I am trying to build an fsl-image-qt5 and am getting an error as follows.
Any ideas on how to fix this?

pknopf at ubuntu:~/Git/recipes/build$ bitbake fsl-image-qt5
Loading cache: 100%
|########################################################################################################################################################################|
ETA:  00:00:00
Loaded 2551 entries from dependency cache.
Parsing recipes: 100%
|######################################################################################################################################################################|
Time: 00:00:00
Parsing of 2036 .bb files complete (2034 cached, 2 parsed). 2552 targets,
152 skipped, 0 masked, 0 errors.
NOTE: Resolving any missing task queue dependencies
NOTE: multiple providers are available for jpeg (jpeg, libjpeg-turbo)
NOTE: consider defining a PREFERRED_PROVIDER entry to match jpeg
NOTE: multiple providers are available for virtual/mesa (mesa, mesa-gl)
NOTE: consider defining a PREFERRED_PROVIDER entry to match virtual/mesa
NOTE: multiple providers are available for runtime libgl-mesa-dev (mesa,
mesa-gl)
NOTE: consider defining a PREFERRED_PROVIDER entry to match libgl-mesa-dev
NOTE: multiple providers are available for runtime libglapi (mesa, mesa-gl)
NOTE: consider defining a PREFERRED_PROVIDER entry to match libglapi
NOTE: multiple providers are available for jpeg-native (jpeg-native,
libjpeg-turbo-native)
NOTE: consider defining a PREFERRED_PROVIDER entry to match jpeg-native

Build Configuration:
BB_VERSION        = "1.26.0"
BUILD_SYS         = "x86_64-linux"
NATIVELSBSTRING   = "Ubuntu-14.04"
TARGET_SYS        = "arm-poky-linux-gnueabi"
MACHINE           = "seco-uq7-dl-256mbx4"
DISTRO            = "poky"
DISTRO_VERSION    = "1.8.1"
TUNE_FEATURES     = "arm armv7a vfp thumb neon callconvention-hard cortexa9"
TARGET_FPU        = "vfp-neon"
meta
meta-yocto        = "(nobranch):b74ea963cefffad9fbd91d4eb9b240f6a8c86cd0"
meta-oe
meta-multimedia   = "(nobranch):df2f700d66bace65f5d802225232d01cf511fe81"
meta-fsl-arm      = "(nobranch):70ddee3ebeacbc53180ee7221533375bf0c9eac4"
meta-fsl-arm-extra = "(nobranch):41e79c6bd055f12b6252618c22c43a2fed5cfb49"
meta-fsl-demos    = "(nobranch):17f9da65efb5c65c1d44b5cc18584034b29a742b"
meta-bsp
meta-sdk          = "(nobranch):6a96fe97d411e097d2222c8e93198b558f4c0329"
meta-browser      = "(nobranch):30b8d6b3d0d6501c56ef6967a2fa73a3d4bf5fe9"
meta-gnome
meta-networking
meta-python       = "(nobranch):df2f700d66bace65f5d802225232d01cf511fe81"
meta-qt5          = "(nobranch):51b4620392aa9041d8512549bfa554bea368c5ea"
meta-seco-bsp-release = "master:b66187468ceae7f0e588d22110697e814d4ceb77"
meta-overlay      = "master:1e1eee6ce59991a054e669bea878fb1e2f779eb2"

NOTE: Preparing RunQueue
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/pknopf/Git/recipes/build/tmp/sysroots/seco-uq7-dl-256mbx4/lib/udev/hid2hci
 Matched in manifest-seco-uq7-dl-256mbx4-bluez5.populate_sysroot
 /home/pknopf/Git/recipes/build/tmp/sysroots/seco-uq7-dl-256mbx4/usr/lib/libbluetooth.so
 Matched in manifest-seco-uq7-dl-256mbx4-bluez5.populate_sysroot
 /home/pknopf/Git/recipes/build/tmp/sysroots/seco-uq7-dl-256mbx4/usr/lib/
libbluetooth.la
 Matched in manifest-seco-uq7-dl-256mbx4-bluez5.populate_sysroot
 /home/pknopf/Git/recipes/build/tmp/sysroots/seco-uq7-dl-256mbx4/usr/lib/libbluetooth.so.3
 Matched in manifest-seco-uq7-dl-256mbx4-bluez5.populate_sysroot
 /home/pknopf/Git/recipes/build/tmp/sysroots/seco-uq7-dl-256mbx4/usr/lib/pkgconfig/bluez.pc
 Matched in manifest-seco-uq7-dl-256mbx4-bluez5.populate_sysroot
 /home/pknopf/Git/recipes/build/tmp/sysroots/seco-uq7-dl-256mbx4/usr/include/bluetooth/hci_lib.h
 Matched in manifest-seco-uq7-dl-256mbx4-bluez5.populate_sysroot
 /home/pknopf/Git/recipes/build/tmp/sysroots/seco-uq7-dl-256mbx4/usr/include/bluetooth/bluetooth.h
 Matched in manifest-seco-uq7-dl-256mbx4-bluez5.populate_sysroot
 /home/pknopf/Git/recipes/build/tmp/sysroots/seco-uq7-dl-256mbx4/usr/include/bluetooth/rfcomm.h
 Matched in manifest-seco-uq7-dl-256mbx4-bluez5.populate_sysroot
 /home/pknopf/Git/recipes/build/tmp/sysroots/seco-uq7-dl-256mbx4/usr/include/bluetooth/hidp.h
 Matched in manifest-seco-uq7-dl-256mbx4-bluez5.populate_sysroot
 /home/pknopf/Git/recipes/build/tmp/sysroots/seco-uq7-dl-256mbx4/usr/include/bluetooth/sdp_lib.h
 Matched in manifest-seco-uq7-dl-256mbx4-bluez5.populate_sysroot
 /home/pknopf/Git/recipes/build/tmp/sysroots/seco-uq7-dl-256mbx4/usr/include/bluetooth/cmtp.h
 Matched in manifest-seco-uq7-dl-256mbx4-bluez5.populate_sysroot
 /home/pknopf/Git/recipes/build/tmp/sysroots/seco-uq7-dl-256mbx4/usr/include/bluetooth/sdp.h
 Matched in manifest-seco-uq7-dl-256mbx4-bluez5.populate_sysroot
 /home/pknopf/Git/recipes/build/tmp/sysroots/seco-uq7-dl-256mbx4/usr/include/bluetooth/bnep.h
 Matched in manifest-seco-uq7-dl-256mbx4-bluez5.populate_sysroot
 /home/pknopf/Git/recipes/build/tmp/sysroots/seco-uq7-dl-256mbx4/usr/include/bluetooth/sco.h
 Matched in manifest-seco-uq7-dl-256mbx4-bluez5.populate_sysroot
 /home/pknopf/Git/recipes/build/tmp/sysroots/seco-uq7-dl-256mbx4/usr/include/bluetooth/hci.h
 Matched in manifest-seco-uq7-dl-256mbx4-bluez5.populate_sysroot
 /home/pknopf/Git/recipes/build/tmp/sysroots/seco-uq7-dl-256mbx4/usr/include/bluetooth/l2cap.h
 Matched in manifest-seco-uq7-dl-256mbx4-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/pknopf/Git/recipes/build/tmp/work/cortexa9hf-vfp-neon-poky-linux-gnueabi/bluez4/4.101-r11/temp/log.do_populate_sysroot.124714
ERROR: Task 2168
(/home/pknopf/Git/recipes/fsl-release-bsp/sources/poky/meta/recipes-connectivity/bluez/
bluez4_4.101.bb, do_populate_sysroot) failed with exit code '1'
NOTE: Tasks Summary: Attempted 1289 tasks of which 1282 didn't need to be
rerun and 1 failed.
Waiting for 0 running tasks to finish:

Summary: 1 task failed:

/home/pknopf/Git/recipes/fsl-release-bsp/sources/poky/meta/recipes-connectivity/bluez/
bluez4_4.101.bb, do_populate_sysroot
Summary: There were 3 ERROR messages shown, returning a non-zero exit code.

-- 

Thanks,
Paul Knopf
Software Engineer
Med X Change, Inc
pknopf at medxchange.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.yoctoproject.org/pipermail/meta-freescale/attachments/20160317/190cb18b/attachment.html>


More information about the meta-freescale mailing list