AnsweredAssumed Answered

Compiling vlc for i.MX6 SABRE-SD

Question asked by victor Wang on Jul 18, 2017
Latest reply on Jul 19, 2017 by victor Wang

Hi everyone.

 

I've been trying to build the vlc on the meta-fsl-arm layer and using commend `bitbake vlc` to build then will show errors like below.

 

 

Loading cache: 100% |########################################################################################################################################################################################################| ETA: 00:00:00
Loaded 2826 entries from dependency cache.
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 jpeg-native (jpeg-native, libjpeg-turbo-native)
NOTE: consider defining a PREFERRED_PROVIDER entry to match jpeg-native

Build Configuration:
BB_VERSION = "1.28.0"
BUILD_SYS = "x86_64-linux"
NATIVELSBSTRING = "Ubuntu-14.04"
TARGET_SYS = "arm-poky-linux-gnueabi"
MACHINE = "imx6dlsabresd"
DISTRO = "fsl-imx-x11"
DISTRO_VERSION = "4.1.15-1.2.0"
TUNE_FEATURES = "arm armv7a vfp neon callconvention-hard cortexa9"
TARGET_FPU = "vfp-neon"
meta
meta-yocto = "HEAD:dd0ba9ea4a11ab15348d4fe3574e4b28784db82f"
meta-oe
meta-multimedia = "HEAD:ad6133a2e95f4b83b6b3ea413598e2cd5fb3fd90"
meta-fsl-arm = "fa3:5f36a9211c8aa0e05c1c58cc0014c70dc18f7cf8"
meta-fsl-arm-extra = "HEAD:e200df91b70da254461c59082ddd5db0a3c415a2"
meta-fsl-demos = "HEAD:2231e946e7a94d096394f2b2477e8184c9bbde7b"
meta-bsp
meta-sdk = "HEAD:dfbc90ee74624ce3be636c8bd2a47114fa2b71aa"
meta-browser = "HEAD:b6d46d69a261fe6bd7c1e9811dc2a9bbd0b79aeb"
meta-gnome
meta-networking
meta-python
meta-ruby
meta-filesystems
meta-xfce = "HEAD:ad6133a2e95f4b83b6b3ea413598e2cd5fb3fd90"
meta-qt5 = "HEAD:d5536e34ec985c82b621448ab4325e5cbba38560"

NOTE: Preparing RunQueue
ERROR: Multiple .bb files are due to be built which each provide jpeg (/mnt/raid10k/wich/freescale/L4.1.15/sources/meta-openembedded/meta-oe/recipes-core/jpeg/libjpeg-turbo_8d+1.4.1.bb /mnt/raid10k/wich/freescale/L4.1.15/sources/poky/meta/recipes-core/jpeg/jpeg_9a.bb).
This usually means one provides something the other doesn't and should.
WARNING: /mnt/raid10k/wich/freescale/L4.1.15/sources/meta-openembedded/meta-multimedia/recipes-multimedia/vlc/vlc_2.2.1.bb.do_compile is tainted from a forced run
NOTE: Executing SetScene Tasks
NOTE: Executing RunQueue Tasks
ERROR: The recipe libjpeg-turbo is trying to install files into a shared area when those files already exist. Those files and their manifest location are:
/mnt/raid10k/wich/freescale/L4.1.15/build-x11-dl/tmp/sysroots/imx6dlsabresd/pkgdata/runtime/jpeg-tools
Matched in manifest-imx6dlsabresd-jpeg.packagedata
/mnt/raid10k/wich/freescale/L4.1.15/build-x11-dl/tmp/sysroots/imx6dlsabresd/pkgdata/runtime/jpeg-tools.packaged
Matched in manifest-imx6dlsabresd-jpeg.packagedata
/mnt/raid10k/wich/freescale/L4.1.15/build-x11-dl/tmp/sysroots/imx6dlsabresd/pkgdata/runtime-reverse/libjpeg-staticdev
Matched in manifest-imx6dlsabresd-jpeg.packagedata
/mnt/raid10k/wich/freescale/L4.1.15/build-x11-dl/tmp/sysroots/imx6dlsabresd/pkgdata/runtime-reverse/libjpeg-doc
Matched in manifest-imx6dlsabresd-jpeg.packagedata
/mnt/raid10k/wich/freescale/L4.1.15/build-x11-dl/tmp/sysroots/imx6dlsabresd/pkgdata/runtime-reverse/libjpeg-dev
Matched in manifest-imx6dlsabresd-jpeg.packagedata
/mnt/raid10k/wich/freescale/L4.1.15/build-x11-dl/tmp/sysroots/imx6dlsabresd/pkgdata/runtime-reverse/libjpeg-dbg
Matched in manifest-imx6dlsabresd-jpeg.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: /mnt/raid10k/wich/freescale/L4.1.15/build-x11-dl/tmp/work/cortexa9hf-vfp-neon-poky-linux-gnueabi/libjpeg-turbo/8d+1.4.1-r0/temp/log.do_packagedata.29147
ERROR: Task 357 (/mnt/raid10k/wich/freescale/L4.1.15/sources/meta-openembedded/meta-oe/recipes-core/jpeg/libjpeg-turbo_8d+1.4.1.bb, do_packagedata) failed with exit code '1'
ERROR: The recipe libjpeg-turbo is trying to install files into a shared area when those files already exist. Those files and their manifest location are:
/mnt/raid10k/wich/freescale/L4.1.15/build-x11-dl/tmp/sysroots/imx6dlsabresd/sysroot-providers/jpeg
Matched in manifest-imx6dlsabresd-jpeg.populate_sysroot
/mnt/raid10k/wich/freescale/L4.1.15/build-x11-dl/tmp/sysroots/imx6dlsabresd/usr/lib/libjpeg.a
Matched in manifest-imx6dlsabresd-jpeg.populate_sysroot
/mnt/raid10k/wich/freescale/L4.1.15/build-x11-dl/tmp/sysroots/imx6dlsabresd/usr/lib/libjpeg.so
Matched in manifest-imx6dlsabresd-jpeg.populate_sysroot
/mnt/raid10k/wich/freescale/L4.1.15/build-x11-dl/tmp/sysroots/imx6dlsabresd/usr/lib/libjpeg.la
Matched in manifest-imx6dlsabresd-jpeg.populate_sysroot
/mnt/raid10k/wich/freescale/L4.1.15/build-x11-dl/tmp/sysroots/imx6dlsabresd/usr/include/jmorecfg.h
Matched in manifest-imx6dlsabresd-jpeg.populate_sysroot
/mnt/raid10k/wich/freescale/L4.1.15/build-x11-dl/tmp/sysroots/imx6dlsabresd/usr/include/jconfig.h
Matched in manifest-imx6dlsabresd-jpeg.populate_sysroot
/mnt/raid10k/wich/freescale/L4.1.15/build-x11-dl/tmp/sysroots/imx6dlsabresd/usr/include/jerror.h
Matched in manifest-imx6dlsabresd-jpeg.populate_sysroot
/mnt/raid10k/wich/freescale/L4.1.15/build-x11-dl/tmp/sysroots/imx6dlsabresd/usr/include/jpeglib.h
Matched in manifest-imx6dlsabresd-jpeg.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: /mnt/raid10k/wich/freescale/L4.1.15/build-x11-dl/tmp/work/cortexa9hf-vfp-neon-poky-linux-gnueabi/libjpeg-turbo/8d+1.4.1-r0/temp/log.do_populate_sysroot.29146
ERROR: Task 353 (/mnt/raid10k/wich/freescale/L4.1.15/sources/meta-openembedded/meta-oe/recipes-core/jpeg/libjpeg-turbo_8d+1.4.1.bb, do_populate_sysroot) failed with exit code '1'
NOTE: Tasks Summary: Attempted 2803 tasks of which 2801 didn't need to be rerun and 2 failed.
Waiting for 0 running tasks to finish:

Summary: 2 tasks failed:
/mnt/raid10k/wich/freescale/L4.1.15/sources/meta-openembedded/meta-oe/recipes-core/jpeg/libjpeg-turbo_8d+1.4.1.bb, do_packagedata
/mnt/raid10k/wich/freescale/L4.1.15/sources/meta-openembedded/meta-oe/recipes-core/jpeg/libjpeg-turbo_8d+1.4.1.bb, do_populate_sysroot
Summary: There was 1 WARNING message shown.
Summary: There were 7 ERROR messages shown, returning a non-zero exit code. 

 

 

After some googling, it seems that other people have the same problem, whereas it compiles perfectly for other platforms.

My question is why will i get those errors? Did i have to modify the lib file?

 

Thanks in advance.

Outcomes