Linux/AM5708: Bitbake error

error log:

Initialising tasks: 100% |####################################################################################################################################################################| Time: 0:00:06
NOTE: Executing SetScene Tasks
NOTE: Executing RunQueue Tasks
WARNING: ti-ipc-3.46.00.02-r1.0 do_fetch: Failed to fetch URL git://git.ti.com/ipc/ipcdev.git;protocol=git;branch=3.46;name=ipcdev, attempting MIRRORS if available
ERROR: ti-ipc-3.46.00.02-r1.0 do_fetch: Fetcher failure: Fetch command export DBUS_SESSION_BUS_ADDRESS="unix:abstract=/tmp/dbus-NxSlbAm8iW"; export SSH_AUTH_SOCK="/run/user/0/keyring-cYcmvf/ssh"; export GIT_PROXY_COMMAND="oe-git-proxy"; export all_proxy="socks5://127.0.0.1:20000/"; export ALL_PROXY="socks5://127.0.0.1:20000/"; export no_proxy="example.com"; export NO_PROXY="example.com"; export ftp_proxy="http://127.0.0.1:20000/"; export https_proxy="https://127.0.0.1:20000/"; export http_proxy="http://127.0.0.1:20000/"; export PATH="/root/psdk/tisdk/sources/oe-core/scripts:/root/psdk/tisdk/build/arago-tmp-external-linaro-toolchain/sysroots/x86_64-linux/usr/bin/arm-linux-gnueabi:/root/psdk/tisdk/build/arago-tmp-external-linaro-toolchain/sysroots/am57xx-evm/usr/bin/crossscripts:/root/psdk/tisdk/build/arago-tmp-external-linaro-toolchain/sysroots/x86_64-linux/usr/sbin:/root/psdk/tisdk/build/arago-tmp-external-linaro-toolchain/sysroots/x86_64-linux/usr/bin:/root/psdk/tisdk/build/arago-tmp-external-linaro-toolchain/sysroots/x86_64-linux/sbin:/root/psdk/tisdk/build/arago-tmp-external-linaro-toolchain/sysroots/x86_64-linux/bin:/root/gcc-linaro-7.2.1-2017.11-x86_64_arm-linux-gnueabihf/bin:/root/psdk/tisdk/sources/meta-browser/scripts:/root/psdk/tisdk/sources/oe-core/scripts:/root/psdk/tisdk/sources/bitbake/bin:/root/psdk/tisdk/sources/meta-browser/scripts:/root/psdk/tisdk/sources/oe-core/scripts:/root/psdk/tisdk/sources/bitbake/bin:/root/psdk/tisdk/sources/meta-browser/scripts:/root/psdk/tisdk/sources/oe-core/scripts:/root/psdk/tisdk/sources/bitbake/bin:/root/psdk/tisdk/sources/meta-browser/scripts:/root/psdk/tisdk/sources/oe-core/scripts:/root/psdk/tisdk/sources/bitbake/bin:/root/gcc-linaro-7.2.1-2017.11-x86_64_arm-linux-gnueabihf/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games"; export HOME="/root"; LANG=C git -c core.fsyncobjectfiles=0 clone --bare --mirror git://git.ti.com/ipc/ipcdev.git /root/psdk/tisdk/downloads/git2/git.ti.com.ipc.ipcdev.git --progress failed with exit code 128, output:
Cloning into bare repository '/root/psdk/tisdk/downloads/git2/git.ti.com.ipc.ipcdev.git'...
fatal: the remote end hung up unexpectedly

ERROR: ti-ipc-3.46.00.02-r1.0 do_fetch: Fetcher failure for URL: 'git://git.ti.com/ipc/ipcdev.git;protocol=git;branch=3.46;name=ipcdev'. Unable to fetch URL from any source.
ERROR: ti-ipc-3.46.00.02-r1.0 do_fetch: Function failed: base_do_fetch
ERROR: Logfile of failure stored in: /root/psdk/tisdk/build/arago-tmp-external-linaro-toolchain/work/am57xx_evm-linux-gnueabi/ti-ipc/3.46.00.02-r1.0/temp/log.do_fetch.24257
ERROR: Task (/root/psdk/tisdk/sources/meta-ti/recipes-ti/ipc/ti-ipc_git.bb:do_fetch) failed with exit code '1'
Waiting for 3 running tasks to finish:

error:

o/public/cpp/bindings/interface_ptr.h:14:0,
| from /root/psdk/tisdk/build/arago-tmp-external-linaro-toolchain/work/armv7ahf-neon-linux-gnueabi/qtwebengine/5.7.1+gitAUTOINC+9cc97f0c63_b3c79e92f0-r0.tisdk0/git/src/3rdparty/chromium/mojo/public/cpp/bindings/lib/bindings_serialization.h:15,
| from /root/psdk/tisdk/build/arago-tmp-external-linaro-toolchain/work/armv7ahf-neon-linux-gnueabi/qtwebengine/5.7.1+gitAUTOINC+9cc97f0c63_b3c79e92f0-r0.tisdk0/git/src/3rdparty/chromium/mojo/public/cpp/bindings/lib/array_internal.h:16,
| from /root/psdk/tisdk/build/arago-tmp-external-linaro-toolchain/work/armv7ahf-neon-linux-gnueabi/qtwebengine/5.7.1+gitAUTOINC+9cc97f0c63_b3c79e92f0-r0.tisdk0/git/src/3rdparty/chromium/mojo/public/cpp/bindings/array.h:16,
| from gen/mojo/public/interfaces/bindings/interface_control_messages.mojom.h:10,
| from /root/psdk/tisdk/build/arago-tmp-external-linaro-toolchain/work/armv7ahf-neon-linux-gnueabi/qtwebengine/5.7.1+gitAUTOINC+9cc97f0c63_b3c79e92f0-r0.tisdk0/git/src/3rdparty/chromium/mojo/public/cpp/bindings/lib/control_message_handler.cc:13:
| /root/psdk/tisdk/build/arago-tmp-external-linaro-toolchain/work/armv7ahf-neon-linux-gnueabi/qtwebengine/5.7.1+gitAUTOINC+9cc97f0c63_b3c79e92f0-r0.tisdk0/git/src/3rdparty/chromium/mojo/public/cpp/bindings/interface_ptr_info.h: In member function ‘mojo::InterfacePtrInfo<Interface>& mojo::InterfacePtrInfo<Interface>::operator=(mojo::InterfacePtrInfo<Interface>&&)’:
| /root/psdk/tisdk/build/arago-tmp-external-linaro-toolchain/work/armv7ahf-neon-linux-gnueabi/qtwebengine/5.7.1+gitAUTOINC+9cc97f0c63_b3c79e92f0-r0.tisdk0/git/src/3rdparty/chromium/mojo/public/cpp/bindings/interface_ptr_info.h:37:31: error: ‘mojo::ScopedMessagePipeHandle {aka class mojo::ScopedHandleBase<mojo::MessagePipeHandle>}’ has no member named ‘Pass’
| handle_ = other.handle_.Pass();
| ^~~~
| [1700/11076] CXX obj/src/3rdparty/chromium/mojo/public/cpp/bindings/lib/mojo_cpp_bindings.message.o
| [1701/11076] CXX obj/src/3rdparty/chromium/mojo/public/cpp/bindings/lib/mojo_cpp_bindings.fixed_buffer.o
| FAILED: obj/src/3rdparty/chromium/mojo/public/cpp/bindings/lib/mojo_cpp_bindings.fixed_buffer.o
| arm-linux-gnueabihf-g++ -march=armv7-a -marm -mfpu=neon -mfloat-abi=hard --sysroot=/root/psdk/tisdk/build/arago-tmp-external-linaro-toolchain/sysroots/am57xx-evm -MMD -MF obj/src/3rdparty/chromium/mojo/public/cpp/bindings/lib/mojo_cpp_bindings.fixed_buffer.o.d -DV8_DEPRECATION_WARNINGS -DCLD_VERSION=2 -DTOOLKIT_QT -D_FILE_OFFSET_BITS=64 -DNO_TCMALLOC -DDISABLE_NACL -DGL_GLEXT_PROTOTYPES -DEGL_EGLEXT_PROTOTYPES '-DOPENSSLDIR="/usr/lib/ssl"' -DOPENSSL_LOAD_CONF -DEGL_API_FB=1 -DLINUX=1 -DCHROMIUM_BUILD -DUI_COMPOSITOR_IMAGE_TRANSPORT -DUSE_AURA=1 -DUSE_OZONE=1 -DUSE_DEFAULT_RENDER_THEME=1 -DUSE_LIBJPEG_TURBO=1 -DENABLE_ONE_CLICK_SIGNIN -DENABLE_MEDIA_ROUTER=1 -DENABLE_CONFIGURATION_POLICY -DENABLE_HIDPI=1 -DENABLE_TOPCHROME_MD=1 -DDONT_EMBED_BUILD_METADATA -DFIELDTRIAL_TESTING_ENABLED -DENABLE_BACKGROUND=1 -DENABLE_APP_LIST=1 -DENABLE_SETTINGS_APP=1 -DENABLE_SUPERVISED_USERS=1 -DENABLE_MDNS=1 -DENABLE_SERVICE_DISCOVERY=1 -DUSE_OPENSSL=1 -DUSE_OPENSSL_CERTS=1 -D__STDC_CONSTANT_MACROS -D__STDC_FORMAT_MACROS -DNDEBUG -DNO_UNWIND_TABLES -DNVALGRIND -DDYNAMIC_ANNOTATIONS_ENABLED=0 '-DQTWEBENGINEPROCESS_NAME="QtWebEngineProcess"' -Igen/shim_headers/libevent/target '-I/root/psdk/tisdk/build/arago-tmp-external-linaro-toolchain/work/armv7ahf-neon-linux-gnueabi/qtwebengine/5.7.1+gitAUTOINC+9cc97f0c63_b3c79e92f0-r0.tisdk0/git/src/3rdparty/chromium' -Igen -fstack-protector --param=ssp-buffer-size=4 -pthread -fno-strict-aliasing -Wall -Wno-extra -Wno-unused-parameter -Wno-missing-field-initializers -fvisibility=hidden -pipe -fPIC -Wno-unused-local-typedefs -I/root/psdk/tisdk/build/arago-tmp-external-linaro-toolchain/sysroots/am57xx-evm/usr/include/dbus-1.0 -I/root/psdk/tisdk/build/arago-tmp-external-linaro-toolchain/sysroots/am57xx-evm/usr/lib/dbus-1.0/include -I/root/psdk/tisdk/build/arago-tmp-external-linaro-toolchain/sysroots/am57xx-evm/usr/include/dbus-1.0 -I/root/psdk/tisdk/build/arago-tmp-external-linaro-toolchain/sysroots/am57xx-evm/usr/lib/dbus-1.0/include -march=armv7-a -mtune=generic-armv7-a -mfpu=neon -mfloat-abi=hard -mthumb --sysroot=/root/psdk/tisdk/build/arago-tmp-external-linaro-toolchain/sysroots/am57xx-evm -Os -fno-ident -fdata-sections -ffunction-sections -fno-unwind-tables -fno-asynchronous-unwind-tables -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=2 -isystem/root/gcc-linaro-7.2.1-2017.11-x86_64_arm-linux-gnueabihf/arm-linux-gnueabihf/include -isystem/root/gcc-linaro-7.2.1-2017.11-x86_64_arm-linux-gnueabihf/arm-linux-gnueabihf/include -O2 -pipe -g -feliminate-unused-debug-types -fdebug-prefix-map=/root/psdk/tisdk/build/arago-tmp-external-linaro-toolchain/work/armv7ahf-neon-linux-gnueabi/qtwebengine/5.7.1+gitAUTOINC+9cc97f0c63_b3c79e92f0-r0.tisdk0=/usr/src/debug/qtwebengine/5.7.1+gitAUTOINC+9cc97f0c63_b3c79e92f0-r0.tisdk0 -fdebug-prefix-map=/root/psdk/tisdk/build/arago-tmp-external-linaro-toolchain/sysroots/x86_64-linux= -fdebug-prefix-map=/root/psdk/tisdk/build/arago-tmp-external-linaro-toolchain/sysroots/am57xx-evm= -fno-exceptions -fno-rtti -fno-threadsafe-statics -fvisibility-inlines-hidden -fno-delete-null-pointer-checks -Wno-abi -std=gnu++11 -Wno-narrowing -c /root/psdk/tisdk/build/arago-tmp-external-linaro-toolchain/work/armv7ahf-neon-linux-gnueabi/qtwebengine/5.7.1+gitAUTOINC+9cc97f0c63_b3c79e92f0-r0.tisdk0/git/src/3rdparty/chromium/mojo/public/cpp/bindings/lib/fixed_buffer.cc -o obj/src/3rdparty/chromium/mojo/public/cpp/bindings/lib/mojo_cpp_bindings.fixed_buffer.o
| In file included from /root/psdk/tisdk/build/arago-tmp-external-linaro-toolchain/work/armv7ahf-neon-linux-gnueabi/qtwebengine/5.7.1+gitAUTOINC+9cc97f0c63_b3c79e92f0-r0.tisdk0/git/src/3rdparty/chromium/mojo/public/cpp/bindings/interface_ptr.h:14:0,
| from /root/psdk/tisdk/build/arago-tmp-external-linaro-toolchain/work/armv7ahf-neon-linux-gnueabi/qtwebengine/5.7.1+gitAUTOINC+9cc97f0c63_b3c79e92f0-r0.tisdk0/git/src/3rdparty/chromium/mojo/public/cpp/bindings/lib/bindings_serialization.h:15,
| from /root/psdk/tisdk/build/arago-tmp-external-linaro-toolchain/work/armv7ahf-neon-linux-gnueabi/qtwebengine/5.7.1+gitAUTOINC+9cc97f0c63_b3c79e92f0-r0.tisdk0/git/src/3rdparty/chromium/mojo/public/cpp/bindings/lib/fixed_buffer.cc:12:
| /root/psdk/tisdk/build/arago-tmp-external-linaro-toolchain/work/armv7ahf-neon-linux-gnueabi/qtwebengine/5.7.1+gitAUTOINC+9cc97f0c63_b3c79e92f0-r0.tisdk0/git/src/3rdparty/chromium/mojo/public/cpp/bindings/interface_ptr_info.h: In member function ‘mojo::InterfacePtrInfo<Interface>& mojo::InterfacePtrInfo<Interface>::operator=(mojo::InterfacePtrInfo<Interface>&&)’:
| /root/psdk/tisdk/build/arago-tmp-external-linaro-toolchain/work/armv7ahf-neon-linux-gnueabi/qtwebengine/5.7.1+gitAUTOINC+9cc97f0c63_b3c79e92f0-r0.tisdk0/git/src/3rdparty/chromium/mojo/public/cpp/bindings/interface_ptr_info.h:37:31: error: ‘mojo::ScopedMessagePipeHandle {aka class mojo::ScopedHandleBase<mojo::MessagePipeHandle>}’ has no member named ‘Pass’
| handle_ = other.handle_.Pass();
| ^~~~
| ERROR: oe_runmake failed
| [1702/11076] CXX obj/src/3rdparty/chromium/mojo/message_pump/mojo_message_pump_lib.handle_watcher.o
| [1703/11076] CXX obj/src/3rdparty/chromium/mojo/public/cpp/bindings/lib/mojo_cpp_bindings.no_interface.o
| [1704/11076] CXX obj/src/3rdparty/chromium/mojo/public/cpp/bindings/lib/mojo_cpp_bindings.interface_endpoint_client.o
| [1705/11076] CXX obj/src/3rdparty/chromium/base/trace_event/base.trace_log.o
| ninja: build stopped: subcommand failed.
| make[3]: *** [invoke_ninja] Error 1
| make[3]: Leaving directory `/root/psdk/tisdk/build/arago-tmp-external-linaro-toolchain/work/armv7ahf-neon-linux-gnueabi/qtwebengine/5.7.1+gitAUTOINC+9cc97f0c63_b3c79e92f0-r0.tisdk0/git/src/core'
| make[2]: *** [sub-gyp_run-pro-make_first] Error 2
| make[2]: Leaving directory `/root/psdk/tisdk/build/arago-tmp-external-linaro-toolchain/work/armv7ahf-neon-linux-gnueabi/qtwebengine/5.7.1+gitAUTOINC+9cc97f0c63_b3c79e92f0-r0.tisdk0/git/src/core'
| make[1]: *** [sub-core-make_first] Error 2
| make[1]: Leaving directory `/root/psdk/tisdk/build/arago-tmp-external-linaro-toolchain/work/armv7ahf-neon-linux-gnueabi/qtwebengine/5.7.1+gitAUTOINC+9cc97f0c63_b3c79e92f0-r0.tisdk0/git/src'
| make: *** [sub-src-make_first] Error 2
| WARNING: /root/psdk/tisdk/build/arago-tmp-external-linaro-toolchain/work/armv7ahf-neon-linux-gnueabi/qtwebengine/5.7.1+gitAUTOINC+9cc97f0c63_b3c79e92f0-r0.tisdk0/temp/run.do_compile.90561:1 exit 1 from 'exit 1'
| ERROR: Function failed: do_compile (log file is located at /root/psdk/tisdk/build/arago-tmp-external-linaro-toolchain/work/armv7ahf-neon-linux-gnueabi/qtwebengine/5.7.1+gitAUTOINC+9cc97f0c63_b3c79e92f0-r0.tisdk0/temp/log.do_compile.90561)
ERROR: Task (/root/psdk/tisdk/sources/meta-qt5/recipes-qt/qt5/qtwebengine_git.bb:do_compile) failed with exit code '1'
NOTE: Tasks Summary: Attempted 3037 tasks of which 2359 didn't need to be rerun and 1 failed.

Summary: 1 task failed:
/root/psdk/tisdk/sources/meta-qt5/recipes-qt/qt5/qtwebengine_git.bb:do_compile
Summary: There was 1 WARNING message shown.
Summary: There were 2 ERROR messages shown, returning a non-zero exit code.
[root@zengjia_vivado:build#]

error log :

  CC [M]  /root/psdk/tisdk/build/arago-tmp-external-linaro-toolchain/work/am57xx_evm-linux-gnueabi/ti-sgx-ddk-km/1.14.3699939-r7m/git/eurasia_km/eurasiacon/binary2_omap_linux_release/target/kbuild/services4/srvkm/common/lists.o
/root/psdk/tisdk/build/arago-tmp-external-linaro-toolchain/work/am57xx_evm-linux-gnueabi/ti-sgx-ddk-km/1.14.3699939-r7m/git/eurasia_km/eurasiacon/binary2_omap_linux_release/target/kbuild/services4/srvkm/common/devicemem.c: In function 'FreeMemCallBackCommon':
/root/psdk/tisdk/build/arago-tmp-external-linaro-toolchain/work/am57xx_evm-linux-gnueabi/ti-sgx-ddk-km/1.14.3699939-r7m/git/eurasia_km/eurasiacon/binary2_omap_linux_release/target/kbuild/services4/srvkm/common/devicemem.c:1073:5: error: this statement may fall through [-Werror=implicit-fallthrough=]
     freeExternal(psMemInfo);
     ^~~~~~~~~~~~~~~~~~~~~~~
/root/psdk/tisdk/build/arago-tmp-external-linaro-toolchain/work/am57xx_evm-linux-gnueabi/ti-sgx-ddk-km/1.14.3699939-r7m/git/eurasia_km/eurasiacon/binary2_omap_linux_release/target/kbuild/services4/srvkm/common/devicemem.c:1074:4: note: here
    case PVRSRV_MEMTYPE_DEVICE:
    ^~~~
  CC [M]  /root/psdk/tisdk/build/arago-tmp-external-linaro-toolchain/work/am57xx_evm-linux-gnueabi/ti-sgx-ddk-km/1.14.3699939-r7m/git/eurasia_km/eurasiacon/binary2_omap_linux_release/target/kbuild/services4/srvkm/common/mem.o
  CC [M]  /root/psdk/tisdk/build/arago-tmp-external-linaro-toolchain/work/am57xx_evm-linux-gnueabi/ti-sgx-ddk-km/1.14.3699939-r7m/git/eurasia_km/eurasiacon/binary2_omap_linux_release/target/kbuild/services4/srvkm/common/mem_debug.o
  CC [M]  /root/psdk/tisdk/build/arago-tmp-external-linaro-toolchain/work/am57xx_evm-linux-gnueabi/ti-sgx-ddk-km/1.14.3699939-r7m/git/eurasia_km/eurasiacon/binary2_omap_linux_release/target/kbuild/services4/srvkm/common/metrics.o
  CC [M]  /root/psdk/tisdk/build/arago-tmp-external-linaro-toolchain/work/am57xx_evm-linux-gnueabi/ti-sgx-ddk-km/1.14.3699939-r7m/git/eurasia_km/eurasiacon/binary2_omap_linux_release/target/kbuild/services4/srvkm/common/osfunc_common.o
cc1: all warnings being treated as errors
  CC [M]  /root/psdk/tisdk/build/arago-tmp-external-linaro-toolchain/work/am57xx_evm-linux-gnueabi/ti-sgx-ddk-km/1.14.3699939-r7m/git/eurasia_km/eurasiacon/binary2_omap_linux_release/target/kbuild/services4/srvkm/common/pdump_common.o
make[4]: *** [/root/psdk/tisdk/build/arago-tmp-external-linaro-toolchain/work/am57xx_evm-linux-gnueabi/ti-sgx-ddk-km/1.14.3699939-r7m/git/eurasia_km/eurasiacon/binary2_omap_linux_release/target/kbuild/services4/srvkm/common/devicemem.o] Error 1
make[4]: *** Waiting for unfinished jobs....
make[3]: *** [_module_/root/psdk/tisdk/build/arago-tmp-external-linaro-toolchain/work/am57xx_evm-linux-gnueabi/ti-sgx-ddk-km/1.14.3699939-r7m/git/eurasia_km/eurasiacon/binary2_omap_linux_release/target/kbuild] Error 2
make[2]: *** [sub-make] Error 2
make[1]: *** [kbuild] Error 2
make: *** [build] Error 2
WARNING: /root/psdk/tisdk/build/arago-tmp-external-linaro-toolchain/work/am57xx_evm-linux-gnueabi/ti-sgx-ddk-km/1.14.3699939-r7m/temp/run.do_compile.92226:1 exit 1 from 'exit 1'

error log:

d by uid 0, which is the same as the user running bitbake. This may be due to host contamination [host-user-contaminated]
WARNING: gstreamer1.0-plugins-base-1.8.3-r0.arago0 do_package_qa: QA Issue: gstreamer1.0-plugins-base: /gstreamer1.0-plugins-base-tcp-dev/usr/lib/gstreamer-1.0/libgsttcp.la is owned by uid 0, which is the same as the user running bitbake. This may be due to host contamination [host-user-contaminated]
WARNING: gstreamer1.0-plugins-base-1.8.3-r0.arago0 do_package_qa: QA Issue: gstreamer1.0-plugins-base: /libgstvideo-1.0/usr/lib/libgstvideo-1.0.so.0.803.0 is owned by uid 0, which is the same as the user running bitbake. This may be due to host contamination
gstreamer1.0-plugins-base: /libgstvideo-1.0/usr/lib/libgstvideo-1.0.so.0 is owned by uid 0, which is the same as the user running bitbake. This may be due to host contamination [host-user-contaminated]
WARNING: gstreamer1.0-plugins-base-1.8.3-r0.arago0 do_package_qa: QA Issue: gstreamer1.0-plugins-base: /gstreamer1.0-plugins-base-theora/usr/lib/gstreamer-1.0/libgsttheora.so is owned by uid 0, which is the same as the user running bitbake. This may be due to host contamination [host-user-contaminated]
WARNING: gstreamer1.0-plugins-base-1.8.3-r0.arago0 do_package_qa: QA Issue: gstreamer1.0-plugins-base: /gstreamer1.0-plugins-base-videoscale-dev/usr/lib/gstreamer-1.0/libgstvideoscale.la is owned by uid 0, which is the same as the user running bitbake. This may be due to host contamination [host-user-contaminated]
WARNING: gstreamer1.0-plugins-base-1.8.3-r0.arago0 do_package_qa: QA Issue: gstreamer1.0-plugins-base: /gstreamer1.0-plugins-base-tcp/usr/lib/gstreamer-1.0/libgsttcp.so is owned by uid 0, which is the same as the user running bitbake. This may be due to host contamination [host-user-contaminated]
WARNING: gstreamer1.0-plugins-base-1.8.3-r0.arago0 do_package_qa: QA Issue: gstreamer1.0-plugins-base: /gstreamer1.0-plugins-base-encodebin-dev/usr/lib/gstreamer-1.0/libgstencodebin.la is owned by uid 0, which is the same as the user running bitbake. This may be due to host contamination [host-user-contaminated]
WARNING: gstreamer1.0-plugins-base-1.8.3-r0.arago0 do_package_qa: QA Issue: gstreamer1.0-plugins-base: /gstreamer1.0-plugins-base-ogg-dev/usr/lib/gstreamer-1.0/libgstogg.la is owned by uid 0, which is the same as the user running bitbake. This may be due to host contamination [host-user-contaminated]
WARNING: gstreamer1.0-plugins-base-1.8.3-r0.arago0 do_package_qa: QA Issue: gstreamer1.0-plugins-base: /libgstaudio-1.0/usr/lib/libgstaudio-1.0.so.0.803.0 is owned by uid 0, which is the same as the user running bitbake. This may be due to host contamination
gstreamer1.0-plugins-base: /libgstaudio-1.0/usr/lib/libgstaudio-1.0.so.0 is owned by uid 0, which is the same as the user running bitbake. This may be due to host contamination [host-user-contaminated]
WARNING: gstreamer1.0-plugins-base-1.8.3-r0.arago0 do_package_qa: QA Issue: gstreamer1.0-plugins-base: /gstreamer1.0-plugins-base-adder/usr/lib/gstreamer-1.0/libgstadder.so is owned by uid 0, which is the same as the user running bitbake. This may be due to host contamination [host-user-contaminated]
WARNING: gstreamer1.0-plugins-base-1.8.3-r0.arago0 do_package_qa: QA Issue: gstreamer1.0-plugins-base: /gstreamer1.0-plugins-base-app/usr/lib/gstreamer-1.0/libgstapp.so is owned by uid 0, which is the same as the user running bitbake. This may be due to host contamination [host-user-contaminated]
WARNING: gstreamer1.0-plugins-base-1.8.3-r0.arago0 do_package_qa: QA Issue: gstreamer1.0-plugins-base: /gstreamer1.0-plugins-base-audiotestsrc/usr/lib/gstreamer-1.0/libgstaudiotestsrc.so is owned by uid 0, which is the same as the user running bitbake. This may be due to host contamination [host-user-contaminated]
WARNING: gstreamer1.0-plugins-base-1.8.3-r0.arago0 do_package_qa: QA Issue: gstreamer1.0-plugins-base: /libgstapp-1.0/usr/lib/libgstapp-1.0.so.0 is owned by uid 0, which is the same as the user running bitbake. This may be due to host contamination
gstreamer1.0-plugins-base: /libgstapp-1.0/usr/lib/libgstapp-1.0.so.0.803.0 is owned by uid 0, which is the same as the user running bitbake. This may be due to host contamination [host-user-contaminated]
WARNING: gstreamer1.0-plugins-base-1.8.3-r0.arago0 do_package_qa: QA Issue: gstreamer1.0-plugins-base: /gstreamer1.0-plugins-base-typefindfunctions/usr/lib/gstreamer-1.0/libgsttypefindfunctions.so is owned by uid 0, which is the same as the user running bitbake. This may be due to host contamination [host-user-contaminated]
WARNING: gstreamer1.0-plugins-base-1.8.3-r0.arago0 do_package_qa: QA Issue: gstreamer1.0-plugins-base: /gstreamer1.0-plugins-base-alsa-dev/usr/lib/gstreamer-1.0/libgstalsa.la is owned by uid 0, which is the same as the user running bitbake. This may be due to host contamination [host-user-contaminated]
WARNING: gstreamer1.0-plugins-base-1.8.3-r0.arago0 do_package_qa: QA Issue: gstreamer1.0-plugins-base: /gstreamer1.0-plugins-base-playback/usr/lib/gstreamer-1.0/libgstplayback.so is owned by uid 0, which is the same as the user running bitbake. This may be due to host contamination [host-user-contaminated]
WARNING: gstreamer1.0-plugins-base-1.8.3-r0.arago0 do_package_qa: QA Issue: gstreamer1.0-plugins-base: /libgstsdp-1.0/usr/lib/libgstsdp-1.0.so.0.803.0 is owned by uid 0, which is the same as the user running bitbake. This may be due to host contamination
gstreamer1.0-plugins-base: /libgstsdp-1.0/usr/lib/libgstsdp-1.0.so.0 is owned by uid 0, which is the same as the user running bitbake. This may be due to host contamination [host-user-contaminated]
WARNING: gstreamer1.0-plugins-base-1.8.3-r0.arago0 do_package_qa: QA Issue: gstreamer1.0-plugins-base: /gstreamer1.0-plugins-base-audiotestsrc-dev/usr/lib/gstreamer-1.0/libgstaudiotestsrc.la is owned by uid 0, which is the same as the user running bitbake. This may be due to host contamination [host-user-contaminated]
WARNING: gstreamer1.0-plugins-base-1.8.3-r0.arago0 do_package_qa: QA Issue: gstreamer1.0-plugins-base: /gstreamer1.0-plugins-base-pango-dev/usr/lib/gstreamer-1.0/libgstpango.la is owned by uid 0, which is the same as the user running bitbake. This may be due to host contamination [host-user-contaminated]
NOTE: Tasks Summary: Attempted 3848 tasks of which 3814 didn't need to be rerun and 2 failed.

Summary: 2 tasks failed:
  /root/psdk/tisdk/sources/meta-ti/recipes-graphics/libgles/ti-sgx-ddk-um_1.14.3699939.bb:do_package_qa
  /root/psdk/tisdk/sources/meta-qt5/recipes-qt/qt5/qtquickcontrols2_git.bb:do_package_qa
Summary: There were 139 WARNING messages shown.
Summary: There were 8 ERROR messages shown, returning a non-zero exit code.
[root@zengjia_vivado:build#] 

error log:

pcre: /libpcre-doc/usr/share/man/man3/pcre32_get_stringnumber.3 is owned by uid 0, which is the same as the user running bitbake. This may be due to host contamination
libpcre: /libpcre-doc/usr/share/man/man3/pcre_jit_stack_free.3 is owned by uid 0, which is the same as the user running bitbake. This may be due to host contamination
libpcre: /libpcre-doc/usr/share/man/man3/pcreprecompile.3 is owned by uid 0, which is the same as the user running bitbake. This may be due to host contamination
libpcre: /libpcre-doc/usr/share/man/man3/pcresample.3 is owned by uid 0, which is the same as the user running bitbake. This may be due to host contamination
libpcre: /libpcre-doc/usr/share/man/man3/pcre_free_substring_list.3 is owned by uid 0, which is the same as the user running bitbake. This may be due to host contamination
libpcre: /libpcre-doc/usr/share/man/man3/pcre_get_substring.3 is owned by uid 0, which is the same as the user running bitbake. This may be due to host contamination
libpcre: /libpcre-doc/usr/share/man/man3/pcre16_get_substring_list.3 is owned by uid 0, which is the same as the user running bitbake. This may be due to host contamination
libpcre: /libpcre-doc/usr/share/man/man3/pcre16_get_named_substring.3 is owned by uid 0, which is the same as the user running bitbake. This may be due to host contamination
libpcre: /libpcre-doc/usr/share/man/man3/pcrecompat.3 is owned by uid 0, which is the same as the user running bitbake. This may be due to host contamination
libpcre: /libpcre-doc/usr/share/man/man3/pcre16_get_stringnumber.3 is owned by uid 0, which is the same as the user running bitbake. This may be due to host contamination
libpcre: /libpcre-doc/usr/share/man/man3/pcre_compile.3 is owned by uid 0, which is the same as the user running bitbake. This may be due to host contamination
libpcre: /libpcre-doc/usr/share/man/man3/pcre_pattern_to_host_byte_order.3 is owned by uid 0, which is the same as the user running bitbake. This may be due to host contamination
libpcre: /libpcre-doc/usr/share/man/man3/pcre_get_stringtable_entries.3 is owned by uid 0, which is the same as the user running bitbake. This may be due to host contamination
libpcre: /libpcre-doc/usr/share/man/man1/pcre-config.1 is owned by uid 0, which is the same as the user running bitbake. This may be due to host contamination [host-user-contaminated]
NOTE: Checking Package: pcretest
NOTE: arm-linux-gnueabihf-objdump -p /root/psdk/tisdk/build/arago-tmp-external-linaro-toolchain/work/armv7ahf-neon-linux-gnueabi/libpcre/8.39-r0/packages-split/pcretest/usr/bin/pcretest
WARNING: QA Issue: libpcre: /pcretest/usr/bin/pcretest is owned by uid 0, which is the same as the user running bitbake. This may be due to host contamination [host-user-contaminated]
NOTE: Checking Package: libpcreposix
NOTE: arm-linux-gnueabihf-objdump -p /root/psdk/tisdk/build/arago-tmp-external-linaro-toolchain/work/armv7ahf-neon-linux-gnueabi/libpcre/8.39-r0/packages-split/libpcreposix/usr/lib/libpcreposix.so.0.0.4
WARNING: QA Issue: libpcre: /libpcreposix/usr/lib/libpcreposix.so.0 is owned by uid 0, which is the same as the user running bitbake. This may be due to host contamination
libpcre: /libpcreposix/usr/lib/libpcreposix.so.0.0.4 is owned by uid 0, which is the same as the user running bitbake. This may be due to host contamination [host-user-contaminated]
NOTE: Checking Package: pcregrep
NOTE: arm-linux-gnueabihf-objdump -p /root/psdk/tisdk/build/arago-tmp-external-linaro-toolchain/work/armv7ahf-neon-linux-gnueabi/libpcre/8.39-r0/packages-split/pcregrep/usr/bin/pcregrep
WARNING: QA Issue: libpcre: /pcregrep/usr/bin/pcregrep is owned by uid 0, which is the same as the user running bitbake. This may be due to host contamination [host-user-contaminated]
NOTE: Checking Package: libpcre-dev
WARNING: QA Issue: libpcre: /libpcre-dev/usr/include/pcreposix.h is owned by uid 0, which is the same as the user running bitbake. This may be due to host contamination
libpcre: /libpcre-dev/usr/include/pcre_scanner.h is owned by uid 0, which is the same as the user running bitbake. This may be due to host contamination
libpcre: /libpcre-dev/usr/include/pcre_stringpiece.h is owned by uid 0, which is the same as the user running bitbake. This may be due to host contamination
libpcre: /libpcre-dev/usr/include/pcrecpparg.h is owned by uid 0, which is the same as the user running bitbake. This may be due to host contamination
libpcre: /libpcre-dev/usr/include/pcre.h is owned by uid 0, which is the same as the user running bitbake. This may be due to host contamination
libpcre: /libpcre-dev/usr/include/pcrecpp.h is owned by uid 0, which is the same as the user running bitbake. This may be due to host contamination
libpcre: /libpcre-dev/usr/lib/libpcre.la is owned by uid 0, which is the same as the user running bitbake. This may be due to host contamination
libpcre: /libpcre-dev/usr/lib/libpcrecpp.la is owned by uid 0, which is the same as the user running bitbake. This may be due to host contamination
libpcre: /libpcre-dev/usr/lib/libpcreposix.la is owned by uid 0, which is the same as the user running bitbake. This may be due to host contamination
libpcre: /libpcre-dev/usr/lib/libpcre.so is owned by uid 0, which is the same as the user running bitbake. This may be due to host contamination
libpcre: /libpcre-dev/usr/lib/libpcreposix.so is owned by uid 0, which is the same as the user running bitbake. This may be due to host contamination
libpcre: /libpcre-dev/usr/lib/libpcrecpp.so is owned by uid 0, which is the same as the user running bitbake. This may be due to host contamination
libpcre: /libpcre-dev/usr/lib/pkgconfig/libpcre.pc is owned by uid 0, which is the same as the user running bitbake. This may be due to host contamination
libpcre: /libpcre-dev/usr/lib/pkgconfig/libpcreposix.pc is owned by uid 0, which is the same as the user running bitbake. This may be due to host contamination
libpcre: /libpcre-dev/usr/lib/pkgconfig/libpcrecpp.pc is owned by uid 0, which is the same as the user running bitbake. This may be due to host contamination
libpcre: /libpcre-dev/usr/bin/pcre-config is owned by uid 0, which is the same as the user running bitbake. This may be due to host contamination [host-user-contaminated]
ERROR: QA run found fatal errors. Please consider fixing them.
DEBUG: Python function do_package_qa finished
ERROR: Function failed: do_package_qa
[root@zengjia_vivado:meta-qt5#] 

error log:

[root@zengjia_vivado:build#] MACHINE=am57xx-evm bitbake arago-base-tisdk-image > logfile
ERROR: qtsvg-5.7.1+gitAUTOINC+d3d3db5a75-r0 do_package_qa: QA Issue: qtsvg-plugins rdepends on external-linaro-toolchain-dbg [debug-deps]
ERROR: qtsvg-5.7.1+gitAUTOINC+d3d3db5a75-r0 do_package_qa: QA Issue: qtsvg-examples rdepends on external-linaro-toolchain-dbg [debug-deps]
ERROR: qtsvg-5.7.1+gitAUTOINC+d3d3db5a75-r0 do_package_qa: QA Issue: qtsvg rdepends on external-linaro-toolchain-dbg [debug-deps]
ERROR: libpcre-8.39-r0 do_package_qa: QA Issue: libpcrecpp rdepends on external-linaro-toolchain-dbg [debug-deps]
ERROR: qtsvg-5.7.1+gitAUTOINC+d3d3db5a75-r0 do_package_qa: QA run found fatal errors. Please consider fixing them.
ERROR: qtsvg-5.7.1+gitAUTOINC+d3d3db5a75-r0 do_package_qa: Function failed: do_package_qa
ERROR: Logfile of failure stored in: /root/psdk/tisdk/build/arago-tmp-external-linaro-toolchain/work/armv7ahf-neon-linux-gnueabi/qtsvg/5.7.1+gitAUTOINC+d3d3db5a75-r0/temp/log.do_package_qa.66029
ERROR: Task (/root/psdk/tisdk/sources/meta-qt5/recipes-qt/qt5/qtsvg_git.bb:do_package_qa) failed with exit code '1'
ERROR: icu-57.1-r0 do_package_qa: QA Issue: libicutu rdepends on external-linaro-toolchain-dbg [debug-deps]
ERROR: libpcre-8.39-r0 do_package_qa: QA run found fatal errors. Please consider fixing them.
ERROR: libpcre-8.39-r0 do_package_qa: Function failed: do_package_qa
ERROR: Logfile of failure stored in: /root/psdk/tisdk/build/arago-tmp-external-linaro-toolchain/work/armv7ahf-neon-linux-gnueabi/libpcre/8.39-r0/temp/log.do_package_qa.65986
ERROR: Task (/root/psdk/tisdk/sources/oe-core/meta/recipes-support/libpcre/libpcre_8.39.bb:do_package_qa) failed with exit code '1'
ERROR: icu-57.1-r0 do_package_qa: QA Issue: icu rdepends on external-linaro-toolchain-dbg [debug-deps]
ERROR: icu-57.1-r0 do_package_qa: QA Issue: libicule rdepends on external-linaro-toolchain-dbg [debug-deps]
ERROR: icu-57.1-r0 do_package_qa: QA Issue: libicuuc rdepends on external-linaro-toolchain-dbg [debug-deps]
ERROR: icu-57.1-r0 do_package_qa: QA Issue: libicui18n rdepends on external-linaro-toolchain-dbg [debug-deps]
ERROR: icu-57.1-r0 do_package_qa: QA Issue: libicuio rdepends on external-linaro-toolchain-dbg [debug-deps]
ERROR: icu-57.1-r0 do_package_qa: QA Issue: libiculx rdepends on external-linaro-toolchain-dbg [debug-deps]
ERROR: icu-57.1-r0 do_package_qa: QA run found fatal errors. Please consider fixing them.
ERROR: icu-57.1-r0 do_package_qa: Function failed: do_package_qa
ERROR: Logfile of failure stored in: /root/psdk/tisdk/build/arago-tmp-external-linaro-toolchain/work/armv7ahf-neon-linux-gnueabi/icu/57.1-r0/temp/log.do_package_qa.65988
ERROR: Task (/root/psdk/tisdk/sources/oe-core/meta/recipes-support/icu/icu_57.1.bb:do_package_qa) failed with exit code '1'
[root@zengjia_vivado:build#]

Part Number: AM5708

Tool/software: Linux

error log:

[root@zengjia_vivado:build#] MACHINE=am57xx-evm bitbake arago-base-tisdk-image > logfile 
ERROR: libical-2.0.0-r0 do_package_qa: QA Issue: libical rdepends on external-linaro-toolchain-dbg [debug-deps]
ERROR: libical-2.0.0-r0 do_package_qa: QA run found fatal errors. Please consider fixing them.
ERROR: libical-2.0.0-r0 do_package_qa: Function failed: do_package_qa
ERROR: Logfile of failure stored in: /root/psdk/tisdk/build/arago-tmp-external-linaro-toolchain/work/armv7ahf-neon-linux-gnueabi/libical/2.0.0-r0/temp/log.do_package_qa.37571
ERROR: Task (/root/psdk/tisdk/sources/oe-core/meta/recipes-support/libical/libical_2.0.0.bb:do_package_qa) failed with exit code '1'
ERROR: icu-57.1-r0 do_package_qa: QA Issue: libicule rdepends on external-linaro-toolchain-dbg [debug-deps]
ERROR: icu-57.1-r0 do_package_qa: QA Issue: icu rdepends on external-linaro-toolchain-dbg [debug-deps]
ERROR: icu-57.1-r0 do_package_qa: QA Issue: libicuio rdepends on external-linaro-toolchain-dbg [debug-deps]
ERROR: icu-57.1-r0 do_package_qa: QA Issue: libicuuc rdepends on external-linaro-toolchain-dbg [debug-deps]
ERROR: icu-57.1-r0 do_package_qa: QA Issue: libicui18n rdepends on external-linaro-toolchain-dbg [debug-deps]
ERROR: icu-57.1-r0 do_package_qa: QA Issue: libicutu rdepends on external-linaro-toolchain-dbg [debug-deps]
ERROR: icu-57.1-r0 do_package_qa: QA Issue: libiculx rdepends on external-linaro-toolchain-dbg [debug-deps]
ERROR: icu-57.1-r0 do_package_qa: QA run found fatal errors. Please consider fixing them.
ERROR: icu-57.1-r0 do_package_qa: Function failed: do_package_qa
ERROR: Logfile of failure stored in: /root/psdk/tisdk/build/arago-tmp-external-linaro-toolchain/work/armv7ahf-neon-linux-gnueabi/icu/57.1-r0/temp/log.do_package_qa.37653
ERROR: Task (/root/psdk/tisdk/sources/oe-core/meta/recipes-support/icu/icu_57.1.bb:do_package_qa) failed with exit code '1'
[root@zengjia_vivado:build#] 

log file:

am5708_psdk_build_logfile.txt

The problem is similar to the link below, but I don't know how they solved it.

https://e2e.ti.com/support/processors/f/791/t/608191#pi320966=1

Part Number: AM5708

Tool/software: Linux

error log:

[root@zengjia_vivado:build#] MACHINE=am57xx-evm bitbake arago-base-tisdk-image > logfile 
ERROR: libical-2.0.0-r0 do_package_qa: QA Issue: libical rdepends on external-linaro-toolchain-dbg [debug-deps]
ERROR: libical-2.0.0-r0 do_package_qa: QA run found fatal errors. Please consider fixing them.
ERROR: libical-2.0.0-r0 do_package_qa: Function failed: do_package_qa
ERROR: Logfile of failure stored in: /root/psdk/tisdk/build/arago-tmp-external-linaro-toolchain/work/armv7ahf-neon-linux-gnueabi/libical/2.0.0-r0/temp/log.do_package_qa.37571
ERROR: Task (/root/psdk/tisdk/sources/oe-core/meta/recipes-support/libical/libical_2.0.0.bb:do_package_qa) failed with exit code '1'
ERROR: icu-57.1-r0 do_package_qa: QA Issue: libicule rdepends on external-linaro-toolchain-dbg [debug-deps]
ERROR: icu-57.1-r0 do_package_qa: QA Issue: icu rdepends on external-linaro-toolchain-dbg [debug-deps]
ERROR: icu-57.1-r0 do_package_qa: QA Issue: libicuio rdepends on external-linaro-toolchain-dbg [debug-deps]
ERROR: icu-57.1-r0 do_package_qa: QA Issue: libicuuc rdepends on external-linaro-toolchain-dbg [debug-deps]
ERROR: icu-57.1-r0 do_package_qa: QA Issue: libicui18n rdepends on external-linaro-toolchain-dbg [debug-deps]
ERROR: icu-57.1-r0 do_package_qa: QA Issue: libicutu rdepends on external-linaro-toolchain-dbg [debug-deps]
ERROR: icu-57.1-r0 do_package_qa: QA Issue: libiculx rdepends on external-linaro-toolchain-dbg [debug-deps]
ERROR: icu-57.1-r0 do_package_qa: QA run found fatal errors. Please consider fixing them.
ERROR: icu-57.1-r0 do_package_qa: Function failed: do_package_qa
ERROR: Logfile of failure stored in: /root/psdk/tisdk/build/arago-tmp-external-linaro-toolchain/work/armv7ahf-neon-linux-gnueabi/icu/57.1-r0/temp/log.do_package_qa.37653
ERROR: Task (/root/psdk/tisdk/sources/oe-core/meta/recipes-support/icu/icu_57.1.bb:do_package_qa) failed with exit code '1'
[root@zengjia_vivado:build#] 

log file:

8171.am5708_psdk_build_logfile.txt

The problem is similar to the link below, but I don't know how they solved it.

https://e2e.ti.com/support/processors/f/791/t/608191#pi320966=1

This post is too messy, I have solved most of the problems now, so I mark this post as solved.

Now I have a very strange problem, I don't know how to solve it, the new post link address is as follows:

https://e2e.ti.com/support/processors/f/791/t/608191#pi320966=1

All the above problems have been solved and need to be fixed by patches.But there's a very strange question that's been raised. Read on.

Can you attach the log file?

log info:

[root@zengjia_vivado:build#] 
[root@zengjia_vivado:build#] MACHINE=am57xx-evm bitbake arago-base-tisdk-image > logfile 
ERROR: libical-2.0.0-r0 do_package_qa: QA Issue: libical rdepends on external-linaro-toolchain-dbg [debug-deps]
ERROR: libical-2.0.0-r0 do_package_qa: QA run found fatal errors. Please consider fixing them.
ERROR: libical-2.0.0-r0 do_package_qa: Function failed: do_package_qa
ERROR: Logfile of failure stored in: /root/psdk/tisdk/build/arago-tmp-external-linaro-toolchain/work/armv7ahf-neon-linux-gnueabi/libical/2.0.0-r0/temp/log.do_package_qa.37571
ERROR: Task (/root/psdk/tisdk/sources/oe-core/meta/recipes-support/libical/libical_2.0.0.bb:do_package_qa) failed with exit code '1'
ERROR: icu-57.1-r0 do_package_qa: QA Issue: libicule rdepends on external-linaro-toolchain-dbg [debug-deps]
ERROR: icu-57.1-r0 do_package_qa: QA Issue: icu rdepends on external-linaro-toolchain-dbg [debug-deps]
ERROR: icu-57.1-r0 do_package_qa: QA Issue: libicuio rdepends on external-linaro-toolchain-dbg [debug-deps]
ERROR: icu-57.1-r0 do_package_qa: QA Issue: libicuuc rdepends on external-linaro-toolchain-dbg [debug-deps]
ERROR: icu-57.1-r0 do_package_qa: QA Issue: libicui18n rdepends on external-linaro-toolchain-dbg [debug-deps]
ERROR: icu-57.1-r0 do_package_qa: QA Issue: libicutu rdepends on external-linaro-toolchain-dbg [debug-deps]
ERROR: icu-57.1-r0 do_package_qa: QA Issue: libiculx rdepends on external-linaro-toolchain-dbg [debug-deps]
ERROR: icu-57.1-r0 do_package_qa: QA run found fatal errors. Please consider fixing them.
ERROR: icu-57.1-r0 do_package_qa: Function failed: do_package_qa
ERROR: Logfile of failure stored in: /root/psdk/tisdk/build/arago-tmp-external-linaro-toolchain/work/armv7ahf-neon-linux-gnueabi/icu/57.1-r0/temp/log.do_package_qa.37653
ERROR: Task (/root/psdk/tisdk/sources/oe-core/meta/recipes-support/icu/icu_57.1.bb:do_package_qa) failed with exit code '1'
[root@zengjia_vivado:build#] 

log file:

6254.am5708_psdk_build_logfile.txt

DEBUG: Executing python function sstate_task_prefunc
DEBUG: Python function sstate_task_prefunc finished
DEBUG: Executing python function do_package_qa
NOTE: DO PACKAGE QA
DEBUG: Executing python function read_subpackage_metadata
DEBUG: Python function read_subpackage_metadata finished
NOTE: Checking Package: libical-locale
NOTE: Checking Package: libical-dbg
NOTE: arm-linux-gnueabihf-objdump -p /root/psdk/tisdk/build/arago-tmp-external-linaro-toolchain/work/armv7ahf-neon-linux-gnueabi/libical/2.0.0-r0/packages-split/libical-dbg/usr/lib/.debug/libicalss.so.2.0.0
NOTE: arm-linux-gnueabihf-objdump -p /root/psdk/tisdk/build/arago-tmp-external-linaro-toolchain/work/armv7ahf-neon-linux-gnueabi/libical/2.0.0-r0/packages-split/libical-dbg/usr/lib/.debug/libical.so.2.0.0
NOTE: arm-linux-gnueabihf-objdump -p /root/psdk/tisdk/build/arago-tmp-external-linaro-toolchain/work/armv7ahf-neon-linux-gnueabi/libical/2.0.0-r0/packages-split/libical-dbg/usr/lib/.debug/libical_cxx.so.2.0.0
NOTE: arm-linux-gnueabihf-objdump -p /root/psdk/tisdk/build/arago-tmp-external-linaro-toolchain/work/armv7ahf-neon-linux-gnueabi/libical/2.0.0-r0/packages-split/libical-dbg/usr/lib/.debug/libicalvcal.so.2.0.0
NOTE: arm-linux-gnueabihf-objdump -p /root/psdk/tisdk/build/arago-tmp-external-linaro-toolchain/work/armv7ahf-neon-linux-gnueabi/libical/2.0.0-r0/packages-split/libical-dbg/usr/lib/.debug/libicalss_cxx.so.2.0.0
WARNING: QA Issue: libical: /libical-dbg/usr/src/debug/libical/2.0.0-r0/build/config.h is owned by uid 0, which is the same as the user running bitbake. This may be due to host contamination
libical: /libical-dbg/usr/src/debug/libical/2.0.0-r0/build/src/libical/icalrestriction.c is owned by uid 0, which is the same as the user running bitbake. This may be due to host contamination
libical: /libical-dbg/usr/src/debug/libical/2.0.0-r0/build/src/libical/icalderivedparameter.h is owned by uid 0, which is the same as the user running bitbake. This may be due to host contamination
libical: /libical-dbg/usr/src/debug/libical/2.0.0-r0/build/src/libical/icalderivedvalue.h is owned by uid 0, which is the same as the user running bitbake. This may be due to host contamination
libical: /libical-dbg/usr/src/debug/libical/2.0.0-r0/build/src/libical/icalderivedproperty.h is owned by uid 0, which is the same as the user running bitbake. This may be due to host contamination
libical: /libical-dbg/usr/src/debug/libical/2.0.0-r0/build/src/libical/icalderivedproperty.c is owned by uid 0, which is the same as the user running bitbake. This may be due to host contamination
libical: /libical-dbg/usr/src/debug/libical/2.0.0-r0/build/src/libical/icalderivedvalue.c is owned by uid 0, which is the same as the user running bitbake. This may be due to host contamination
libical: /libical-dbg/usr/src/debug/libical/2.0.0-r0/build/src/libical/icalderivedparameter.c is owned by uid 0, which is the same as the user running bitbake. This may be due to host contamination
libical: /libical-dbg/usr/src/debug/libical/2.0.0-r0/libical-2.0.0/src/libical/icalmime.c is owned by uid 0, which is the same as the user running bitbake. This may be due to host contamination
libical: /libical-dbg/usr/src/debug/libical/2.0.0-r0/libical-2.0.0/src/libical/icaltypes.c is owned by uid 0, which is the same as the user running bitbake. This may be due to host contamination
libical: /libical-dbg/usr/src/debug/libical/2.0.0-r0/libical-2.0.0/src/libical/icalparser.h is owned by uid 0, which is the same as the user running bitbake. This may be due to host contamination
libical: /libical-dbg/usr/src/debug/libical/2.0.0-r0/libical-2.0.0/src/libical/icalperiod.h is owned by uid 0, which is the same as the user running bitbake. This may be due to host contamination
libical: /libical-dbg/usr/src/debug/libical/2.0.0-r0/libical-2.0.0/src/libical/vcomponent_cxx.cpp is owned by uid 0, which is the same as the user running bitbake. This may be due to host contamination
libical: /libical-dbg/usr/src/debug/libical/2.0.0-r0/libical-2.0.0/src/libical/icalarray.c is owned by uid 0, which is the same as the user running bitbake. This may be due to host contamination
libical: /libical-dbg/usr/src/debug/libical/2.0.0-r0/libical-2.0.0/src/libical/icalproperty.c is owned by uid 0, which is the same as the user running bitbake. This may be due to host contamination
libical: /libical-dbg/usr/src/debug/libical/2.0.0-r0/libical-2.0.0/src/libical/icalcomponent.c is owned by uid 0, which is the same as the user running bitbake. This may be due to host contamination
libical: /libical-dbg/usr/src/debug/libical/2.0.0-r0/libical-2.0.0/src/libical/icalerror.h is owned by uid 0, which is the same as the user running bitbake. This may be due to host contamination
libical: /libical-dbg/usr/src/debug/libical/2.0.0-r0/libical-2.0.0/src/libical/icaltimezone.c is owned by uid 0, which is the same as the user running bitbake. This may be due to host contamination
libical: /libical-dbg/usr/src/debug/libical/2.0.0-r0/libical-2.0.0/src/libical/icalvalue.h is owned by uid 0, which is the same as the user running bitbake. This may be due to host contamination
libical: /libical-dbg/usr/src/debug/libical/2.0.0-r0/libical-2.0.0/src/libical/icaltypes.h is owned by uid 0, which is the same as the user running bitbake. This may be due to host contamination
libical: /libical-dbg/usr/src/debug/libical/2.0.0-r0/libical-2.0.0/src/libical/icalattach.c is owned by uid 0, which is the same as the user running bitbake. This may be due to host contamination
libical: /libical-dbg/usr/src/debug/libical/2.0.0-r0/libical-2.0.0/src/libical/icalproperty_cxx.h is owned by uid 0, which is the same as the user running bitbake. This may be due to host contamination
libical: /libical-dbg/usr/src/debug/libical/2.0.0-r0/libical-2.0.0/src/libical/caldate.c is owned by uid 0, which is the same as the user running bitbake. This may be due to host contamination
libical: /libical-dbg/usr/src/debug/libical/2.0.0-r0/libical-2.0.0/src/libical/icalparameterimpl.h is owned by uid 0, which is the same as the user running bitbake. This may be due to host contamination
libical: /libical-dbg/usr/src/debug/libical/2.0.0-r0/libical-2.0.0/src/libical/icalparameter_cxx.cpp is owned by uid 0, which is the same as the user running bitbake. This may be due to host contamination
libical: /libical-dbg/usr/src/debug/libical/2.0.0-r0/libical-2.0.0/src/libical/icallangbind.c is owned by uid 0, which is the same as the user running bitbake. This may be due to host contamination
libical: /libical-dbg/usr/src/debug/libical/2.0.0-r0/libical-2.0.0/src/libical/icalmemory.c is owned by uid 0, which is the same as the user running bitbake. This may be due to host contamination
libical: /libical-dbg/usr/src/debug/libical/2.0.0-r0/libical-2.0.0/src/libical/icalcomponent.h is owned by uid 0, which is the same as the user running bitbake. This may be due to host contamination
libical: /libical-dbg/usr/src/debug/libical/2.0.0-r0/libical-2.0.0/src/libical/icalproperty_cxx.cpp is owned by uid 0, which is the same as the user running bitbake. This may be due to host contamination
libical: /libical-dbg/usr/src/debug/libical/2.0.0-r0/libical-2.0.0/src/libical/icalrestriction.h is owned by uid 0, which is the same as the user running bitbake. This may be due to host contamination
libical: /libical-dbg/usr/src/debug/libical/2.0.0-r0/libical-2.0.0/src/libical/icaltimezone.h is owned by uid 0, which is the same as the user running bitbake. This may be due to host contamination
libical: /libical-dbg/usr/src/debug/libical/2.0.0-r0/libical-2.0.0/src/libical/sspm.c is owned by uid 0, which is the same as the user running bitbake. This may be due to host contamination
libical: /libical-dbg/usr/src/debug/libical/2.0.0-r0/libical-2.0.0/src/libical/icalrecur.c is owned by uid 0, which is the same as the user running bitbake. This may be due to host contamination
libical: /libical-dbg/usr/src/debug/libical/2.0.0-r0/libical-2.0.0/src/libical/icaltz-util.c is owned by uid 0, which is the same as the user running bitbake. This may be due to host contamination
libical: /libical-dbg/usr/src/debug/libical/2.0.0-r0/libical-2.0.0/src/libical/icalvalueimpl.h is owned by uid 0, which is the same as the user running bitbake. This may be due to host contamination
libical: /libical-dbg/usr/src/debug/libical/2.0.0-r0/libical-2.0.0/src/libical/icalproperty.h is owned by uid 0, which is the same as the user running bitbake. This may be due to host contamination
libical: /libical-dbg/usr/src/debug/libical/2.0.0-r0/libical-2.0.0/src/libical/icalvalue_cxx.cpp is owned by uid 0, which is the same as the user running bitbake. This may be due to host contamination
libical: /libical-dbg/usr/src/debug/libical/2.0.0-r0/libical-2.0.0/src/libical/icalerror.c is owned by uid 0, which is the same as the user running bitbake. This may be due to host contamination
libical: /libical-dbg/usr/src/debug/libical/2.0.0-r0/libical-2.0.0/src/libical/icalmemory.h is owned by uid 0, which is the same as the user running bitbake. This may be due to host contamination
libical: /libical-dbg/usr/src/debug/libical/2.0.0-r0/libical-2.0.0/src/libical/astime.h is owned by uid 0, which is the same as the user running bitbake. This may be due to host contamination
libical: /libical-dbg/usr/src/debug/libical/2.0.0-r0/libical-2.0.0/src/libical/icalvalue.c is owned by uid 0, which is the same as the user running bitbake. This may be due to host contamination
libical: /libical-dbg/usr/src/debug/libical/2.0.0-r0/libical-2.0.0/src/libical/icaltimezoneimpl.h is owned by uid 0, which is the same as the user running bitbake. This may be due to host contamination
libical: /libical-dbg/usr/src/debug/libical/2.0.0-r0/libical-2.0.0/src/libical/icalenums.h is owned by uid 0, which is the same as the user running bitbake. This may be due to host contamination
libical: /libical-dbg/usr/src/debug/libical/2.0.0-r0/libical-2.0.0/src/libical/icalrecur.h is owned by uid 0, which is the same as the user running bitbake. This may be due to host contamination
libical: /libical-dbg/usr/src/debug/libical/2.0.0-r0/libical-2.0.0/src/libical/icalarray.h is owned by uid 0, which is the same as the user running bitbake. This may be due to host contamination
libical: /libical-dbg/usr/src/debug/libical/2.0.0-r0/libical-2.0.0/src/libical/icalparameter_cxx.h is owned by uid 0, which is the same as the user running bitbake. This may be due to host contamination
libical: /libical-dbg/usr/src/debug/libical/2.0.0-r0/libical-2.0.0/src/libical/pvl.h is owned by uid 0, which is the same as the user running bitbake. This may be due to host contamination
libical: /libical-dbg/usr/src/debug/libical/2.0.0-r0/libical-2.0.0/src/libical/icaltime.h is owned by uid 0, which is the same as the user running bitbake. This may be due to host contamination
libical: /libical-dbg/usr/src/debug/libical/2.0.0-r0/libical-2.0.0/src/libical/icaltz-util.h is owned by uid 0, which is the same as the user running bitbake. This may be due to host contamination
libical: /libical-dbg/usr/src/debug/libical/2.0.0-r0/libical-2.0.0/src/libical/icalparameter.h is owned by uid 0, which is the same as the user running bitbake. This may be due to host contamination
libical: /libical-dbg/usr/src/debug/libical/2.0.0-r0/libical-2.0.0/src/libical/vcomponent_cxx.h is owned by uid 0, which is the same as the user running bitbake. This may be due to host contamination
libical: /libical-dbg/usr/src/debug/libical/2.0.0-r0/libical-2.0.0/src/libical/icaltime.c is owned by uid 0, which is the same as the user running bitbake. This may be due to host contamination
libical: /libical-dbg/usr/src/debug/libical/2.0.0-r0/libical-2.0.0/src/libical/icalattachimpl.h is owned by uid 0, which is the same as the user running bitbake. This may be due to host contamination
libical: /libical-dbg/usr/src/debug/libical/2.0.0-r0/libical-2.0.0/src/libical/icalparameter.c is owned by uid 0, which is the same as the user running bitbake. This may be due to host contamination
libical: /libical-dbg/usr/src/debug/libical/2.0.0-r0/libical-2.0.0/src/libical/icalduration.c is owned by uid 0, which is the same as the user running bitbake. This may be due to host contamination
libical: /libical-dbg/usr/src/debug/libical/2.0.0-r0/libical-2.0.0/src/libical/icalparser.c is owned by uid 0, which is the same as the user running bitbake. This may be due to host contamination
libical: /libical-dbg/usr/src/debug/libical/2.0.0-r0/libical-2.0.0/src/libical/icalvalue_cxx.h is owned by uid 0, which is the same as the user running bitbake. This may be due to host contamination
libical: /libical-dbg/usr/src/debug/libical/2.0.0-r0/libical-2.0.0/src/libical/sspm.h is owned by uid 0, which is the same as the user running bitbake. This may be due to host contamination
libical: /libical-dbg/usr/src/debug/libical/2.0.0-r0/libical-2.0.0/src/libical/icalperiod.c is owned by uid 0, which is the same as the user running bitbake. This may be due to host contamination
libical: /libical-dbg/usr/src/debug/libical/2.0.0-r0/libical-2.0.0/src/libical/pvl.c is owned by uid 0, which is the same as the user running bitbake. This may be due to host contamination
libical: /libical-dbg/usr/src/debug/libical/2.0.0-r0/libical-2.0.0/src/libical/icptrholder_cxx.h is owned by uid 0, which is the same as the user running bitbake. This may be due to host contamination
libical: /libical-dbg/usr/src/debug/libical/2.0.0-r0/libical-2.0.0/src/libical/icalattach.h is owned by uid 0, which is the same as the user running bitbake. This may be due to host contamination
libical: /libical-dbg/usr/src/debug/libical/2.0.0-r0/libical-2.0.0/src/libical/icalduration.h is owned by uid 0, which is the same as the user running bitbake. This may be due to host contamination
libical: /libical-dbg/usr/src/debug/libical/2.0.0-r0/libical-2.0.0/src/libical/icalenums.c is owned by uid 0, which is the same as the user running bitbake. This may be due to host contamination
libical: /libical-dbg/usr/src/debug/libical/2.0.0-r0/libical-2.0.0/src/libicalvcal/vcc.h is owned by uid 0, which is the same as the user running bitbake. This may be due to host contamination
libical: /libical-dbg/usr/src/debug/libical/2.0.0-r0/libical-2.0.0/src/libicalvcal/vobject.c is owned by uid 0, which is the same as the user running bitbake. This may be due to host contamination
libical: /libical-dbg/usr/src/debug/libical/2.0.0-r0/libical-2.0.0/src/libicalvcal/vobject.h is owned by uid 0, which is the same as the user running bitbake. This may be due to host contamination
libical: /libical-dbg/usr/src/debug/libical/2.0.0-r0/libical-2.0.0/src/libicalvcal/icalvcal.c is owned by uid 0, which is the same as the user running bitbake. This may be due to host contamination
libical: /libical-dbg/usr/src/debug/libical/2.0.0-r0/libical-2.0.0/src/libicalvcal/vcaltmp.c is owned by uid 0, which is the same as the user running bitbake. This may be due to host contamination
libical: /libical-dbg/usr/src/debug/libical/2.0.0-r0/libical-2.0.0/src/libicalvcal/vcc.c is owned by uid 0, which is the same as the user running bitbake. This may be due to host contamination
libical: /libical-dbg/usr/src/debug/libical/2.0.0-r0/libical-2.0.0/src/libicalvcal/icalvcal.h is owned by uid 0, which is the same as the user running bitbake. This may be due to host contamination
libical: /libical-dbg/usr/src/debug/libical/2.0.0-r0/libical-2.0.0/src/libicalss/icalssyacc.h is owned by uid 0, which is the same as the user running bitbake. This may be due to host contamination
libical: /libical-dbg/usr/src/debug/libical/2.0.0-r0/libical-2.0.0/src/libicalss/icalclusterimpl.h is owned by uid 0, which is the same as the user running bitbake. This may be due to host contamination
libical: /libical-dbg/usr/src/debug/libical/2.0.0-r0/libical-2.0.0/src/libicalss/icalsslexer.c is owned by uid 0, which is the same as the user running bitbake. This may be due to host contamination
libical: /libical-dbg/usr/src/debug/libical/2.0.0-r0/libical-2.0.0/src/libicalss/icaldirsetimpl.h is owned by uid 0, which is the same as the user running bitbake. This may be due to host contamination
libical: /libical-dbg/usr/src/debug/libical/2.0.0-r0/libical-2.0.0/src/libicalss/icalssyacc.c is owned by uid 0, which is the same as the user running bitbake. This may be due to host contamination
libical: /libical-dbg/usr/src/debug/libical/2.0.0-r0/libical-2.0.0/src/libicalss/icaldirset.c is owned by uid 0, which is the same as the user running bitbake. This may be due to host contamination
libical: /libical-dbg/usr/src/debug/libical/2.0.0-r0/libical-2.0.0/src/libicalss/icalcalendar.h is owned by uid 0, which is the same as the user running bitbake. This may be due to host contamination
libical: /libical-dbg/usr/src/debug/libical/2.0.0-r0/libical-2.0.0/src/libicalss/icalspanlist.c is owned by uid 0, which is the same as the user running bitbake. This may be due to host contamination
libical: /libical-dbg/usr/src/debug/libical/2.0.0-r0/libical-2.0.0/src/libicalss/icalspanlist.h is owned by uid 0, which is the same as the user running bitbake. This may be due to host contamination
libical: /libical-dbg/usr/src/debug/libical/2.0.0-r0/libical-2.0.0/src/libicalss/icalgauge.c is owned by uid 0, which is the same as the user running bitbake. This may be due to host contamination
libical: /libical-dbg/usr/src/debug/libical/2.0.0-r0/libical-2.0.0/src/libicalss/icalmessage.c is owned by uid 0, which is the same as the user running bitbake. This may be due to host contamination
libical: /libical-dbg/usr/src/debug/libical/2.0.0-r0/libical-2.0.0/src/libicalss/icaldirset.h is owned by uid 0, which is the same as the user running bitbake. This may be due to host contamination
libical: /libical-dbg/usr/src/debug/libical/2.0.0-r0/libical-2.0.0/src/libicalss/icalfileset.h is owned by uid 0, which is the same as the user running bitbake. This may be due to host contamination
libical: /libical-dbg/usr/src/debug/libical/2.0.0-r0/libical-2.0.0/src/libicalss/icalset.h is owned by uid 0, which is the same as the user running bitbake. This may be due to host contamination
libical: /libical-dbg/usr/src/debug/libical/2.0.0-r0/libical-2.0.0/src/libicalss/icalcalendar.c is owned by uid 0, which is the same as the user running bitbake. This may be due to host contamination
libical: /libical-dbg/usr/src/debug/libical/2.0.0-r0/libical-2.0.0/src/libicalss/icalset.c is owned by uid 0, which is the same as the user running bitbake. This may be due to host contamination
libical: /libical-dbg/usr/src/debug/libical/2.0.0-r0/libical-2.0.0/src/libicalss/icalspanlist_cxx.h is owned by uid 0, which is the same as the user running bitbake. This may be due to host contamination
libical: /libical-dbg/usr/src/debug/libical/2.0.0-r0/libical-2.0.0/src/libicalss/icalfileset.c is owned by uid 0, which is the same as the user running bitbake. This may be due to host contamination
libical: /libical-dbg/usr/src/debug/libical/2.0.0-r0/libical-2.0.0/src/libicalss/icalgaugeimpl.h is owned by uid 0, which is the same as the user running bitbake. This may be due to host contamination
libical: /libical-dbg/usr/src/debug/libical/2.0.0-r0/libical-2.0.0/src/libicalss/icalcluster.h is owned by uid 0, which is the same as the user running bitbake. This may be due to host contamination
libical: /libical-dbg/usr/src/debug/libical/2.0.0-r0/libical-2.0.0/src/libicalss/icalspanlist_cxx.cpp is owned by uid 0, which is the same as the user running bitbake. This may be due to host contamination
libical: /libical-dbg/usr/src/debug/libical/2.0.0-r0/libical-2.0.0/src/libicalss/icalgauge.h is owned by uid 0, which is the same as the user running bitbake. This may be due to host contamination
libical: /libical-dbg/usr/src/debug/libical/2.0.0-r0/libical-2.0.0/src/libicalss/icalfilesetimpl.h is owned by uid 0, which is the same as the user running bitbake. This may be due to host contamination
libical: /libical-dbg/usr/src/debug/libical/2.0.0-r0/libical-2.0.0/src/libicalss/icalcluster.c is owned by uid 0, which is the same as the user running bitbake. This may be due to host contamination
libical: /libical-dbg/usr/src/debug/libical/2.0.0-r0/libical-2.0.0/src/libicalss/icalclassify.c is owned by uid 0, which is the same as the user running bitbake. This may be due to host contamination
libical: /libical-dbg/usr/lib/.debug/libicalss.so.2.0.0 is owned by uid 0, which is the same as the user running bitbake. This may be due to host contamination
libical: /libical-dbg/usr/lib/.debug/libical.so.2.0.0 is owned by uid 0, which is the same as the user running bitbake. This may be due to host contamination
libical: /libical-dbg/usr/lib/.debug/libical_cxx.so.2.0.0 is owned by uid 0, which is the same as the user running bitbake. This may be due to host contamination
libical: /libical-dbg/usr/lib/.debug/libicalvcal.so.2.0.0 is owned by uid 0, which is the same as the user running bitbake. This may be due to host contamination
libical: /libical-dbg/usr/lib/.debug/libicalss_cxx.so.2.0.0 is owned by uid 0, which is the same as the user running bitbake. This may be due to host contamination [host-user-contaminated]
NOTE: Checking Package: libical-dev
WARNING: QA Issue: libical: /libical-dev/usr/include/libical/icalssyacc.h is owned by uid 0, which is the same as the user running bitbake. This may be due to host contamination
libical: /libical-dev/usr/include/libical/icalparser.h is owned by uid 0, which is the same as the user running bitbake. This may be due to host contamination
libical: /libical-dev/usr/include/libical/icalclassify.h is owned by uid 0, which is the same as the user running bitbake. This may be due to host contamination
libical: /libical-dev/usr/include/libical/libical_ical_export.h is owned by uid 0, which is the same as the user running bitbake. This may be due to host contamination
libical: /libical-dev/usr/include/libical/icalperiod.h is owned by uid 0, which is the same as the user running bitbake. This may be due to host contamination
libical: /libical-dev/usr/include/libical/vcc.h is owned by uid 0, which is the same as the user running bitbake. This may be due to host contamination
libical: /libical-dev/usr/include/libical/icalerror.h is owned by uid 0, which is the same as the user running bitbake. This may be due to host contamination
libical: /libical-dev/usr/include/libical/icalvalue.h is owned by uid 0, which is the same as the user running bitbake. This may be due to host contamination
libical: /libical-dev/usr/include/libical/icaltypes.h is owned by uid 0, which is the same as the user running bitbake. This may be due to host contamination
libical: /libical-dev/usr/include/libical/icalproperty_cxx.h is owned by uid 0, which is the same as the user running bitbake. This may be due to host contamination
libical: /libical-dev/usr/include/libical/icaldirsetimpl.h is owned by uid 0, which is the same as the user running bitbake. This may be due to host contamination
libical: /libical-dev/usr/include/libical/icalderivedparameter.h is owned by uid 0, which is the same as the user running bitbake. This may be due to host contamination
libical: /libical-dev/usr/include/libical/icalderivedvalue.h is owned by uid 0, which is the same as the user running bitbake. This may be due to host contamination
libical: /libical-dev/usr/include/libical/icalcalendar.h is owned by uid 0, which is the same as the user running bitbake. This may be due to host contamination
libical: /libical-dev/usr/include/libical/icalderivedproperty.h is owned by uid 0, which is the same as the user running bitbake. This may be due to host contamination
libical: /libical-dev/usr/include/libical/icalcomponent.h is owned by uid 0, which is the same as the user running bitbake. This may be due to host contamination
libical: /libical-dev/usr/include/libical/icalrestriction.h is owned by uid 0, which is the same as the user running bitbake. This may be due to host contamination
libical: /libical-dev/usr/include/libical/icalmessage.h is owned by uid 0, which is the same as the user running bitbake. This may be due to host contamination
libical: /libical-dev/usr/include/libical/icalspanlist.h is owned by uid 0, which is the same as the user running bitbake. This may be due to host contamination
libical: /libical-dev/usr/include/libical/vobject.h is owned by uid 0, which is the same as the user running bitbake. This may be due to host contamination
libical: /libical-dev/usr/include/libical/icaltimezone.h is owned by uid 0, which is the same as the user running bitbake. This may be due to host contamination
libical: /libical-dev/usr/include/libical/icaldirset.h is owned by uid 0, which is the same as the user running bitbake. This may be due to host contamination
libical: /libical-dev/usr/include/libical/libical_icalss_export.h is owned by uid 0, which is the same as the user running bitbake. This may be due to host contamination
libical: /libical-dev/usr/include/libical/icalproperty.h is owned by uid 0, which is the same as the user running bitbake. This may be due to host contamination
libical: /libical-dev/usr/include/libical/icalfileset.h is owned by uid 0, which is the same as the user running bitbake. This may be due to host contamination
libical: /libical-dev/usr/include/libical/icalmemory.h is owned by uid 0, which is the same as the user running bitbake. This may be due to host contamination
libical: /libical-dev/usr/include/libical/icalenums.h is owned by uid 0, which is the same as the user running bitbake. This may be due to host contamination
libical: /libical-dev/usr/include/libical/icalset.h is owned by uid 0, which is the same as the user running bitbake. This may be due to host contamination
libical: /libical-dev/usr/include/libical/icalss.h is owned by uid 0, which is the same as the user running bitbake. This may be due to host contamination
libical: /libical-dev/usr/include/libical/icalrecur.h is owned by uid 0, which is the same as the user running bitbake. This may be due to host contamination
libical: /libical-dev/usr/include/libical/icalspanlist_cxx.h is owned by uid 0, which is the same as the user running bitbake. This may be due to host contamination
libical: /libical-dev/usr/include/libical/ical.h is owned by uid 0, which is the same as the user running bitbake. This may be due to host contamination
libical: /libical-dev/usr/include/libical/icalarray.h is owned by uid 0, which is the same as the user running bitbake. This may be due to host contamination
libical: /libical-dev/usr/include/libical/icalparameter_cxx.h is owned by uid 0, which is the same as the user running bitbake. This may be due to host contamination
libical: /libical-dev/usr/include/libical/icalgaugeimpl.h is owned by uid 0, which is the same as the user running bitbake. This may be due to host contamination
libical: /libical-dev/usr/include/libical/pvl.h is owned by uid 0, which is the same as the user running bitbake. This may be due to host contamination
libical: /libical-dev/usr/include/libical/icaltime.h is owned by uid 0, which is the same as the user running bitbake. This may be due to host contamination
libical: /libical-dev/usr/include/libical/icalcluster.h is owned by uid 0, which is the same as the user running bitbake. This may be due to host contamination
libical: /libical-dev/usr/include/libical/vcaltmp.h is owned by uid 0, which is the same as the user running bitbake. This may be due to host contamination
libical: /libical-dev/usr/include/libical/icaltz-util.h is owned by uid 0, which is the same as the user running bitbake. This may be due to host contamination
libical: /libical-dev/usr/include/libical/icalparameter.h is owned by uid 0, which is the same as the user running bitbake. This may be due to host contamination
libical: /libical-dev/usr/include/libical/vcomponent_cxx.h is owned by uid 0, which is the same as the user running bitbake. This may be due to host contamination
libical: /libical-dev/usr/include/libical/icalgauge.h is owned by uid 0, which is the same as the user running bitbake. This may be due to host contamination
libical: /libical-dev/usr/include/libical/icalvalue_cxx.h is owned by uid 0, which is the same as the user running bitbake. This may be due to host contamination
libical: /libical-dev/usr/include/libical/libical_vcal_export.h is owned by uid 0, which is the same as the user running bitbake. This may be due to host contamination
libical: /libical-dev/usr/include/libical/icallangbind.h is owned by uid 0, which is the same as the user running bitbake. This may be due to host contamination
libical: /libical-dev/usr/include/libical/icalfilesetimpl.h is owned by uid 0, which is the same as the user running bitbake. This may be due to host contamination
libical: /libical-dev/usr/include/libical/sspm.h is owned by uid 0, which is the same as the user running bitbake. This may be due to host contamination
libical: /libical-dev/usr/include/libical/icptrholder_cxx.h is owned by uid 0, which is the same as the user running bitbake. This may be due to host contamination
libical: /libical-dev/usr/include/libical/icalattach.h is owned by uid 0, which is the same as the user running bitbake. This may be due to host contamination
libical: /libical-dev/usr/include/libical/icalduration.h is owned by uid 0, which is the same as the user running bitbake. This may be due to host contamination
libical: /libical-dev/usr/include/libical/icalvcal.h is owned by uid 0, which is the same as the user running bitbake. This may be due to host contamination
libical: /libical-dev/usr/include/libical/icalmime.h is owned by uid 0, which is the same as the user running bitbake. This may be due to host contamination
libical: /libical-dev/usr/lib/libical_cxx.so is owned by uid 0, which is the same as the user running bitbake. This may be due to host contamination
libical: /libical-dev/usr/lib/libical.so is owned by uid 0, which is the same as the user running bitbake. This may be due to host contamination
libical: /libical-dev/usr/lib/libicalss.so is owned by uid 0, which is the same as the user running bitbake. This may be due to host contamination
libical: /libical-dev/usr/lib/libicalvcal.so is owned by uid 0, which is the same as the user running bitbake. This may be due to host contamination
libical: /libical-dev/usr/lib/libicalss_cxx.so is owned by uid 0, which is the same as the user running bitbake. This may be due to host contamination
libical: /libical-dev/usr/lib/cmake/LibIcal/LibIcalConfig.cmake is owned by uid 0, which is the same as the user running bitbake. This may be due to host contamination
libical: /libical-dev/usr/lib/cmake/LibIcal/LibIcalConfigVersion.cmake is owned by uid 0, which is the same as the user running bitbake. This may be due to host contamination
libical: /libical-dev/usr/lib/cmake/LibIcal/LibIcalTargets-noconfig.cmake is owned by uid 0, which is the same as the user running bitbake. This may be due to host contamination
libical: /libical-dev/usr/lib/cmake/LibIcal/LibIcalTargets.cmake is owned by uid 0, which is the same as the user running bitbake. This may be due to host contamination
libical: /libical-dev/usr/lib/pkgconfig/libical.pc is owned by uid 0, which is the same as the user running bitbake. This may be due to host contamination [host-user-contaminated]
NOTE: Checking Package: libical
NOTE: arm-linux-gnueabihf-objdump -p /root/psdk/tisdk/build/arago-tmp-external-linaro-toolchain/work/armv7ahf-neon-linux-gnueabi/libical/2.0.0-r0/packages-split/libical/usr/lib/libicalss.so.2.0.0
NOTE: arm-linux-gnueabihf-objdump -p /root/psdk/tisdk/build/arago-tmp-external-linaro-toolchain/work/armv7ahf-neon-linux-gnueabi/libical/2.0.0-r0/packages-split/libical/usr/lib/libical.so.2.0.0
NOTE: arm-linux-gnueabihf-objdump -p /root/psdk/tisdk/build/arago-tmp-external-linaro-toolchain/work/armv7ahf-neon-linux-gnueabi/libical/2.0.0-r0/packages-split/libical/usr/lib/libical_cxx.so.2.0.0
NOTE: arm-linux-gnueabihf-objdump -p /root/psdk/tisdk/build/arago-tmp-external-linaro-toolchain/work/armv7ahf-neon-linux-gnueabi/libical/2.0.0-r0/packages-split/libical/usr/lib/libicalvcal.so.2.0.0
NOTE: arm-linux-gnueabihf-objdump -p /root/psdk/tisdk/build/arago-tmp-external-linaro-toolchain/work/armv7ahf-neon-linux-gnueabi/libical/2.0.0-r0/packages-split/libical/usr/lib/libicalss_cxx.so.2.0.0
WARNING: QA Issue: libical: /libical/usr/lib/libical_cxx.so.2 is owned by uid 0, which is the same as the user running bitbake. This may be due to host contamination
libical: /libical/usr/lib/libicalss.so.2.0.0 is owned by uid 0, which is the same as the user running bitbake. This may be due to host contamination
libical: /libical/usr/lib/libical.so.2.0.0 is owned by uid 0, which is the same as the user running bitbake. This may be due to host contamination
libical: /libical/usr/lib/libical.so.2 is owned by uid 0, which is the same as the user running bitbake. This may be due to host contamination
libical: /libical/usr/lib/libical_cxx.so.2.0.0 is owned by uid 0, which is the same as the user running bitbake. This may be due to host contamination
libical: /libical/usr/lib/libicalvcal.so.2.0.0 is owned by uid 0, which is the same as the user running bitbake. This may be due to host contamination
libical: /libical/usr/lib/libicalss_cxx.so.2.0.0 is owned by uid 0, which is the same as the user running bitbake. This may be due to host contamination
libical: /libical/usr/lib/libicalvcal.so.2 is owned by uid 0, which is the same as the user running bitbake. This may be due to host contamination
libical: /libical/usr/lib/libicalss_cxx.so.2 is owned by uid 0, which is the same as the user running bitbake. This may be due to host contamination
libical: /libical/usr/lib/libicalss.so.2 is owned by uid 0, which is the same as the user running bitbake. This may be due to host contamination [host-user-contaminated]
ERROR: QA Issue: libical rdepends on external-linaro-toolchain-dbg [debug-deps]
WARNING: QA Issue: /usr/lib/libical_cxx.so.2.0.0 contained in package libical requires libstdc++.so.6(CXXABI_1.3.9), but no providers found in RDEPENDS_libical? [file-rdeps]
NOTE: Checking Package: libical-staticdev
WARNING: QA Issue: libical: /libical-staticdev/usr/lib/libicalss.a is owned by uid 0, which is the same as the user running bitbake. This may be due to host contamination
libical: /libical-staticdev/usr/lib/libicalvcal.a is owned by uid 0, which is the same as the user running bitbake. This may be due to host contamination
libical: /libical-staticdev/usr/lib/libicalss_cxx.a is owned by uid 0, which is the same as the user running bitbake. This may be due to host contamination
libical: /libical-staticdev/usr/lib/libical_cxx.a is owned by uid 0, which is the same as the user running bitbake. This may be due to host contamination
libical: /libical-staticdev/usr/lib/libical.a is owned by uid 0, which is the same as the user running bitbake. This may be due to host contamination [host-user-contaminated]
NOTE: Checking Package: libical-doc
ERROR: QA run found fatal errors. Please consider fixing them.
DEBUG: Python function do_package_qa finished
ERROR: Function failed: do_package_qa

log.do_package_qa.37653.txt

The problem is similar to the link below, but I don't know how they solved it.

https://e2e.ti.com/support/processors/f/791/t/608191#pi320966=1

OK,thank you very mutch.

The above problem is solved.

The following problems occur.

cmd : MACHINE=am57xx-evm bitbake opencl  --force -c compile

Error log:

| cd /root/psdk/tisdk/build/arago-tmp-external-linaro-toolchain/work/am57xx_evm-linux-gnueabi/opencl/1.1.13.0-r0.0/build/src && /root/gcc-linaro-7.2.1-2017.11-x86_64_arm-linux-gnueabihf/bin/arm-linux-gnueabihf-g++   -DOpenCL_EXPORTS -I/root/psdk/tisdk/build/arago-tmp-external-linaro-toolchain/work/am57xx_evm-linux-gnueabi/opencl/1.1.13.0-r0.0/git/host/include -I/root/psdk/tisdk/build/arago-tmp-external-linaro-toolchain/work/am57xx_evm-linux-gnueabi/opencl/1.1.13.0-r0.0/git/host/src -I/include -I/root/psdk/tisdk/build/arago-tmp-external-linaro-toolchain/work/am57xx_evm-linux-gnueabi/opencl/1.1.13.0-r0.0/build/src -I/root/psdk/tisdk/build/arago-tmp-external-linaro-toolchain/work/am57xx_evm-linux-gnueabi/opencl/1.1.13.0-r0.0/git/host/src/core/dsp/tal/ocl_load/DLOAD_API -I/root/psdk/tisdk/build/arago-tmp-external-linaro-toolchain/work/am57xx_evm-linux-gnueabi/opencl/1.1.13.0-r0.0/git/host/src/core/dsp/tal/ocl_load/DLOAD -I/root/psdk/tisdk/build/arago-tmp-external-linaro-toolchain/work/am57xx_evm-linux-gnueabi/opencl/1.1.13.0-r0.0/git/host/src/core/dsp/tal -I/root/psdk/tisdk/build/arago-tmp-external-linaro-toolchain/work/am57xx_evm-linux-gnueabi/opencl/1.1.13.0-r0.0/git/host/src/core/dsp  -march=armv7-a -marm -mfpu=neon  -mfloat-abi=hard  --sysroot=/root/psdk/tisdk/build/arago-tmp-external-linaro-toolchain/sysroots/am57xx-evm  -isystem/root/gcc-linaro-7.2.1-2017.11-x86_64_arm-linux-gnueabihf/arm-linux-gnueabihf/include  -O2 -pipe -g -feliminate-unused-debug-types -fdebug-prefix-map=/root/psdk/tisdk/build/arago-tmp-external-linaro-toolchain/work/am57xx_evm-linux-gnueabi/opencl/1.1.13.0-r0.0=/usr/src/debug/opencl/1.1.13.0-r0.0 -fdebug-prefix-map=/root/psdk/tisdk/build/arago-tmp-external-linaro-toolchain/sysroots/x86_64-linux= -fdebug-prefix-map=/root/psdk/tisdk/build/arago-tmp-external-linaro-toolchain/sysroots/am57xx-evm=   -march=armv7-a -marm -mfpu=neon  -mfloat-abi=hard  --sysroot=/root/psdk/tisdk/build/arago-tmp-external-linaro-toolchain/sysroots/am57xx-evm -std=c++11 -Wno-unused-variable -Werror -Wno-literal-suffix -Wno-deprecated-declarations -fpermissive -D_FILE_OFFSET_BITS=64 -D_PRODUCT_VERSION=01.01.13.0 -DBOOST_SYSTEM_NO_DEPRECATED=1 -DBOOST_SYSTEM_NO_LIB=1 -DPACKAGE=ti-opencl -DPACKAGE_VERSION=01.01.13.0 -O3 -DDEVICE_AM57 -DULM_ENABLED -fPIC   -I/root/psdk/tisdk/build/arago-tmp-external-linaro-toolchain/sysroots/am57xx-evm/usr/include/ti-llvm3.6  -DNDEBUG -D_GNU_SOURCE -D__STDC_CONSTANT_MACROS -D__STDC_FORMAT_MACROS -D__STDC_LIMIT_MACROS -O3 -fomit-frame-pointer -std=c++11 -fvisibility-inlines-hidden -fPIC -ffunction-sections -fdata-sections -o CMakeFiles/OpenCL.dir/core/cpu/program.cpp.o -c /root/psdk/tisdk/build/arago-tmp-external-linaro-toolchain/work/am57xx_evm-linux-gnueabi/opencl/1.1.13.0-r0.0/git/host/src/core/cpu/program.cpp
| /root/psdk/tisdk/build/arago-tmp-external-linaro-toolchain/work/am57xx_evm-linux-gnueabi/opencl/1.1.13.0-r0.0/git/host/src/core/platform.cpp:62:1: error: static assertion failed: Class Platform must be of C++ standard layout type.
|  static_assert(std::is_standard_layout<Platform>::value,
|  ^~~~~~~~~~~~~
| make[2]: *** [src/CMakeFiles/OpenCL.dir/core/platform.cpp.o] Error 1
| make[2]: *** Waiting for unfinished jobs....
| make[2]: Leaving directory `/root/psdk/tisdk/build/arago-tmp-external-linaro-toolchain/work/am57xx_evm-linux-gnueabi/opencl/1.1.13.0-r0.0/build'
| make[1]: *** [src/CMakeFiles/OpenCL.dir/all] Error 2
| make[1]: Leaving directory `/root/psdk/tisdk/build/arago-tmp-external-linaro-toolchain/work/am57xx_evm-linux-gnueabi/opencl/1.1.13.0-r0.0/build'
| make: *** [all] Error 2
| ERROR: Function failed: do_compile (log file is located at /root/psdk/tisdk/build/arago-tmp-external-linaro-toolchain/work/am57xx_evm-linux-gnueabi/opencl/1.1.13.0-r0.0/temp/log.do_compile.119320)
ERROR: Task (/root/psdk/tisdk/sources/meta-arago/meta-arago-extras/recipes-ti/ocl/opencl_git.bb:do_compile) failed with exit code '1'
NOTE: Tasks Summary: Attempted 856 tasks of which 855 didn't need to be rerun and 1 failed.

Summary: 1 task failed:
  /root/psdk/tisdk/sources/meta-arago/meta-arago-extras/recipes-ti/ocl/opencl_git.bb:do_compile
Summary: There was 1 WARNING message shown.
Summary: There were 2 ERROR messages shown, returning a non-zero exit code.