Linux/PROCESSOR-SDK-AM335X: Arago image with Qt

Hello, I tried to use the command "MACHINE=am335x-evm bitbake -c populate_sdk arago-base-tisdk-image", and I get the same error as with my custom image.. What am I missing?

ERROR: arago-base-image-1.0-r0 do_populate_sdk: Unable to install packages. Command '/home/davide/tisdk/build/arago-tmp-external-linaro-toolchain/work/am335x_evm-linux-gnueabi/davide-base-image/1.0-r0/recipe-sysroot-native/usr/bin/opkg --volatile-cache -f /home/davide/tisdk/build/arago-tmp-external-linaro-toolchain/work/am335x_evm-linux-gnueabi/davide-base-image/1.0-r0/opkg.conf -t /home/davide/tisdk/build/arago-tmp-external-linaro-toolchain/work/am335x_evm-linux-gnueabi/davide-base-image/1.0-r0/temp/ipktemp/ -o /home/davide/tisdk/build/arago-tmp-external-linaro-toolchain/work/am335x_evm-linux-gnueabi/davide-base-image/1.0-r0/sdk/image/tmp/xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx/yyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyy/sysroots/armv7ahf-neon-linux-gnueabi --force_postinstall install packagegroup-core-boot run-postinsts packagegroup-arago-base packagegroup-core-standalone-sdk-target psplash packagegroup-arago-console packagegroup-arago-qte opkg' returned 1: Collected errors:

* Solver encountered 1 problem(s):
* Problem 1/1: * - nothing provides libatomic-dev needed by packagegroup-core-standalone-sdk-target-1.0-r8.all *
* Solution 1: * - do not ask to install a package providing packagegroup-core-standalone-sdk-target

ERROR: davide-base-image-1.0-r0 do_populate_sdk: Function failed: do_populate_sdk ERROR: Logfile of failure stored in: /home/davide/tisdk/build/arago-tmp-external-linaro-toolchain/work/am335x_evm-linux-gnueabi/davide-base-image/1.0-r0/temp/log.do_populate_sdk.550 ERROR: Task (/home/davide/tisdk/sources/meta-arago/meta-arago-distro/recipes-core/images/arago-base-image.bb:do_populate_sdk) failed with exit code '1'

Hi Davidino,

I am looking into your issue currently and I will get back to you by tomorrow.

Regards,
Krunal

Davidino,

Have you tried a complete SDK build, just to see if that works? Have you made any modifications to the configuration on your machine? If so, please share with us these changes.

Thank you.

Hello Krunal and RonB,
Below you can find the entire prompt output trying to compile the arago-base-tisdk-image and its sdk. Is it what you meant RonB? Thank you for anserws.

davide@davide-P553UA:~$ export TOOLCHAIN_PATH_ARMV7=$HOME/gcc-linaro-7.2.1-2017.11-x86_64_arm-linux-gnueabihf
davide@davide-P553UA:~$ cd tisdk
davide@davide-P553UA:~/tisdk$ ./oe-layertool-setup.sh -f configs/processor-sdk/processor-sdk-05.00.00.15-config.txt
/home/davide/tisdk


cloning repo bitbake

Fetching origin
La precedente posizione di HEAD era d0fb46e... fetch2/__init__: Disable pseudo in runfetchcmd()
Si è passati al branch '1.36'
Your branch is up-to-date with 'origin/1.36'.
Already up-to-date.
Note: checking out 'd0fb46eead1f23356d8c3bd53a85047521ef29a7'.

You are in 'detached HEAD' state. You can look around, make experimental
changes and commit them, and you can discard any commits you make in this
state without impacting any branches by performing another checkout.

If you want to create a new branch to retain commits you create, you may
do so (now or later) by using -b with the checkout command again. Example:

git checkout -b <new-branch-name>

HEAD si trova ora a d0fb46e... fetch2/__init__: Disable pseudo in runfetchcmd()


cloning repo meta-processor-sdk

Fetching origin
Da arago-project.org/.../meta-processor-sdk
91dd4b4..8beb5c6 master -> origin/master
La precedente posizione di HEAD era 264dc66... packagegroup-arago-tisdk-opencl: add tidl-utils
Si è passati al branch 'master'
Your branch is behind 'origin/master' by 3 commits, and can be fast-forwarded.
(use "git pull" to update your local branch)
Aggiornamento di 91dd4b4..8beb5c6
Fast-forward
....patch => 0001-turtlebot-navigation-params-yaml.patch} | 15 +++++++++++++--
.../files/0003-turtlebot-bringup-description.launch | 4 ++++
.../ros-mmwave/mmwave-ros-autonomous-robotics_2.5.1.bb | 6 ++++--
.../ti-tisdk-makefile/ti-tisdk-makefile_1.0.bbappend | 4 +++-
4 files changed, 24 insertions(+), 5 deletions(-)
rename recipes-ros/ros-mmwave/files/{0001-turtlebot-navigation-costmap-params-yaml.patch => 0001-turtlebot-navigation-params-yaml.patch} (63%)
create mode 100644 recipes-ros/ros-mmwave/files/0003-turtlebot-bringup-description.launch
Note: checking out '264dc66c689e0e4212c43358382986ee470619d4'.

You are in 'detached HEAD' state. You can look around, make experimental
changes and commit them, and you can discard any commits you make in this
state without impacting any branches by performing another checkout.

If you want to create a new branch to retain commits you create, you may
do so (now or later) by using -b with the checkout command again. Example:

git checkout -b <new-branch-name>

HEAD si trova ora a 264dc66... packagegroup-arago-tisdk-opencl: add tidl-utils


cloning repo meta-ros

Fetching origin
La precedente posizione di HEAD era e256640... Merge pull request #581 from bulwahn/python3-manifest-change
Si è passati al branch 'master'
Your branch is up-to-date with 'origin/master'.
Already up-to-date.
Note: checking out 'e2566402ab108a19634354a934788109422cf409'.

You are in 'detached HEAD' state. You can look around, make experimental
changes and commit them, and you can discard any commits you make in this
state without impacting any branches by performing another checkout.

If you want to create a new branch to retain commits you create, you may
do so (now or later) by using -b with the checkout command again. Example:

git checkout -b <new-branch-name>

HEAD si trova ora a e256640... Merge pull request #581 from bulwahn/python3-manifest-change


cloning repo meta-arago

Fetching origin
Da arago-project.org/.../meta-arago
d81e074..583307d rocko-next -> origin/rocko-next
warning: refname 'ti2018.01' is ambiguous.
Si è passati al branch 'ti2018.01'
Your branch is up-to-date with 'origin/ti2018.01'.
Already up-to-date.
Note: checking out 'd54e9d6c1d461dbf3189e691088d328bf4c4fb19'.

You are in 'detached HEAD' state. You can look around, make experimental
changes and commit them, and you can discard any commits you make in this
state without impacting any branches by performing another checkout.

If you want to create a new branch to retain commits you create, you may
do so (now or later) by using -b with the checkout command again. Example:

git checkout -b <new-branch-name>

HEAD si trova ora a d54e9d6... tidl-utils: SRCREV bump


cloning repo meta-browser

Fetching origin
La precedente posizione di HEAD era 26d5066... firefox: fix build failures
Si è passati al branch 'master'
Your branch is up-to-date with 'origin/master'.
Already up-to-date.
Note: checking out '26d50665e2f7223c5f4ad7481a8d2431e7cb55fb'.

You are in 'detached HEAD' state. You can look around, make experimental
changes and commit them, and you can discard any commits you make in this
state without impacting any branches by performing another checkout.

If you want to create a new branch to retain commits you create, you may
do so (now or later) by using -b with the checkout command again. Example:

git checkout -b <new-branch-name>

HEAD si trova ora a 26d5066... firefox: fix build failures


cloning repo meta-qt5

Fetching origin
Si è passati al branch 'rocko'
Your branch is up-to-date with 'origin/rocko'.
Already up-to-date.
Note: checking out '682ad61c071a9710e9f9d8a32ab1b5f3c14953d1'.

You are in 'detached HEAD' state. You can look around, make experimental
changes and commit them, and you can discard any commits you make in this
state without impacting any branches by performing another checkout.

If you want to create a new branch to retain commits you create, you may
do so (now or later) by using -b with the checkout command again. Example:

git checkout -b <new-branch-name>

HEAD si trova ora a 682ad61... qt: upgrade to 5.9.6


cloning repo meta-openembedded

Fetching origin
La precedente posizione di HEAD era 3525310... protobuf: Fix fetcher failure for rocko.
Si è passati al branch 'rocko'
Your branch is up-to-date with 'origin/rocko'.
Already up-to-date.
Note: checking out '352531015014d1957d6444d114f4451e241c4d23'.

You are in 'detached HEAD' state. You can look around, make experimental
changes and commit them, and you can discard any commits you make in this
state without impacting any branches by performing another checkout.

If you want to create a new branch to retain commits you create, you may
do so (now or later) by using -b with the checkout command again. Example:

git checkout -b <new-branch-name>

HEAD si trova ora a 3525310... protobuf: Fix fetcher failure for rocko.


cloning repo meta-ti

Fetching origin
warning: refname 'ti2018.01' is ambiguous.
Si è passati al branch 'ti2018.01'
Your branch is up-to-date with 'origin/ti2018.01'.
Already up-to-date.
Note: checking out '8555084679dc5c668e5fb60a16425ca32b10ff21'.

You are in 'detached HEAD' state. You can look around, make experimental
changes and commit them, and you can discard any commits you make in this
state without impacting any branches by performing another checkout.

If you want to create a new branch to retain commits you create, you may
do so (now or later) by using -b with the checkout command again. Example:

git checkout -b <new-branch-name>

HEAD si trova ora a 8555084... mmap-lld: Update to version 2.0.0.8A & adding rtos recipe


cloning repo meta-linaro

Fetching origin
Si è passati al branch 'rocko'
Your branch is up-to-date with 'origin/rocko'.
Already up-to-date.
Note: checking out '75dfb67bbb14a70cd47afda9726e2e1c76731885'.

You are in 'detached HEAD' state. You can look around, make experimental
changes and commit them, and you can discard any commits you make in this
state without impacting any branches by performing another checkout.

If you want to create a new branch to retain commits you create, you may
do so (now or later) by using -b with the checkout command again. Example:

git checkout -b <new-branch-name>

HEAD si trova ora a 75dfb67... optee-os: simplify deploy logic


cloning repo oe-core

Fetching origin
remote: Counting objects: 45, done.
remote: Compressing objects: 100% (45/45), done.
remote: Total 45 (delta 36), reused 0 (delta 0)
Unpacking objects: 100% (45/45), done.
Da git://git.openembedded.org/openembedded-core
957a2f9..bb378dc master-next -> origin/master-next
La precedente posizione di HEAD era 931a52e... linux-firmware: package rtl8168 firmware
Si è passati al branch 'rocko'
Your branch is up-to-date with 'origin/rocko'.
Already up-to-date.
Note: checking out '931a52e8698f684ccbb26ddec18764ad9d9a3e8f'.

You are in 'detached HEAD' state. You can look around, make experimental
changes and commit them, and you can discard any commits you make in this
state without impacting any branches by performing another checkout.

If you want to create a new branch to retain commits you create, you may
do so (now or later) by using -b with the checkout command again. Example:

git checkout -b <new-branch-name>

HEAD si trova ora a 931a52e... linux-firmware: package rtl8168 firmware


################################################################################
The bblayers.conf configuration file has been created for you with some
default values. Please verify the contents of your conf/bblayers.conf
file for correctness.

NOTE: Any additional entries to this file will be lost if the ./oe-layertool-setup.sh
script is run again. To add entries permanently to this file
please add them to the config file used and rerun the
./oe-layertool-setup.sh script.



################################################################################
The local.conf configuration file has been created for you with some
default values. Please verify the contents of your conf/local.conf
file for correctness.

By default the number of threads used by the build is set to the number
of CPUs found on your system.

NOTE: You will probably want to change the default MACHINE setting in the
local.conf file to the machine you are trying to build.



################################################################################
A setenv file has been created for you in the conf directory. Please verify
The contents of this file. Once you have verified the contents please source
this file to configure your environment for building:

. conf/setenv

You can then start building using the bitbake command. You will likely want
to set the MACHINE option if you have not done so in your local.conf file.

For example:
MACHINE=xxxxx bitbake <target>

Common targets are:
core-image-minimal
core-image-sato
meta-toolchain
meta-toolchain-sdk
adt-installer
meta-ide-support
davide@davide-P553UA:~/tisdk$ cd build
davide@davide-P553UA:~/tisdk/build$ . conf/setenv
davide@davide-P553UA:~/tisdk/build$ MACHINE=am335x-evm bitbake arago-base-tisdk-image
NOTE: Your conf/bblayers.conf has been automatically updated.
NOTE: Your conf/bblayers.conf has been automatically updated.
Parsing recipes: 100% |##########################################| Time: 0:07:28
Parsing of 3139 .bb files complete (0 cached, 3139 parsed). 4048 targets, 484 skipped, 0 masked, 0 errors.
WARNING: No recipes available for:
/home/davide/tisdk/sources/meta-arago/meta-arago-distro/recipes-multimedia/gstreamer/gstreamer1.0-plugins-base_1.8.3.bbappend
/home/davide/tisdk/sources/meta-processor-sdk/recipes-devtools/python/python3-native_3.5.2.bbappend
/home/davide/tisdk/sources/meta-processor-sdk/recipes-graphics/wayland/weston_1.11.0.bbappend
NOTE: Resolving any missing task queue dependencies

Build Configuration:
BB_VERSION = "1.36.0"
BUILD_SYS = "x86_64-linux"
NATIVELSBSTRING = "ubuntu-16.04"
TARGET_SYS = "arm-linux-gnueabi"
MACHINE = "am335x-evm"
DISTRO = "arago"
DISTRO_VERSION = "2018.04"
TUNE_FEATURES = "arm armv7a vfp thumb neon callconvention-hard"
TARGET_FPU = "hard"
meta-processor-sdk = "HEAD:264dc66c689e0e4212c43358382986ee470619d4"
meta-ros = "HEAD:e2566402ab108a19634354a934788109422cf409"
meta-arago-distro
meta-arago-extras = "HEAD:d54e9d6c1d461dbf3189e691088d328bf4c4fb19"
meta-browser = "HEAD:26d50665e2f7223c5f4ad7481a8d2431e7cb55fb"
meta-qt5 = "HEAD:682ad61c071a9710e9f9d8a32ab1b5f3c14953d1"
meta-networking
meta-python
meta-oe
meta-gnome
meta-multimedia = "HEAD:352531015014d1957d6444d114f4451e241c4d23"
meta-ti = "HEAD:8555084679dc5c668e5fb60a16425ca32b10ff21"
meta-linaro-toolchain
meta-optee = "HEAD:75dfb67bbb14a70cd47afda9726e2e1c76731885"
meta = "HEAD:931a52e8698f684ccbb26ddec18764ad9d9a3e8f"

Initialising tasks: 100% |#######################################| Time: 0:00:16
NOTE: Executing SetScene Tasks
NOTE: Executing RunQueue Tasks
WARNING: external-linaro-toolchain-2017.11-r0.arago36 do_package: QA Issue: external-linaro-toolchain: Files/directories were installed but not shipped in any package:
/lib/libcilkrts.so.5
/lib/libcilkrts.so
/lib/libcilkrts.so.5.0.0
/lib/libcilkrts.spec
Please set FILES such that these items are packaged. Alternatively if they are unneeded, avoid installing them or delete them within do_install.
external-linaro-toolchain: 4 installed and not shipped files. [installed-vs-shipped]
WARNING: external-linaro-toolchain-2017.11-r0.arago36 do_populate_lic: ${COREBASE}/LICENSE is not a valid license file, please use '${COMMON_LICENSE_DIR}/MIT' for a MIT License file in LIC_FILES_CHKSUM. This will become an error in the future
WARNING: ti-cgt-pru-native-2.2.1-r0 do_populate_lic: ti-cgt-pru-native: No generic license file exists for: Hewlett-Packard in any provider
WARNING: external-linaro-toolchain-2017.11-r0.arago36 do_package_qa: QA Issue: external-linaro-toolchain: /libgomp-dev/usr/lib/gcc/arm-linux-gnueabi/7.2.1/include/omp.h is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
external-linaro-toolchain: /libgomp-dev/lib/libgomp.spec is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination [host-user-contaminated]
WARNING: external-linaro-toolchain-2017.11-r0.arago36 do_package_qa: QA Issue: external-linaro-toolchain: /libasan-dev/lib/libsanitizer.spec is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination [host-user-contaminated]
WARNING: external-linaro-toolchain-2017.11-r0.arago36 do_package_qa: QA Issue: external-linaro-toolchain: /libstdc++/lib/libstdc++.so.6.0.24 is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
external-linaro-toolchain: /libstdc++/lib/libstdc++.so.6.0.24-gdb.py is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination [host-user-contaminated]
WARNING: external-linaro-toolchain-2017.11-r0.arago36 do_package_qa: QA Issue: external-linaro-toolchain: /libcidn/lib/libcidn-2.25.so is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination [host-user-contaminated]
WARNING: external-linaro-toolchain-2017.11-r0.arago36 do_package_qa: QA Issue: external-linaro-toolchain: /libitm/lib/libitm.so.1.0.0 is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination [host-user-contaminated]
WARNING: external-linaro-toolchain-2017.11-r0.arago36 do_package_qa: QA Issue: external-linaro-toolchain: /glibc-extra-nss/lib/libnss_db-2.25.so is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination [host-user-contaminated]
WARNING: external-linaro-toolchain-2017.11-r0.arago36 do_package_qa: QA Issue: external-linaro-toolchain: /external-linaro-toolchain-pcprofile/lib/libpcprofile.so is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination [host-user-contaminated]
WARNING: external-linaro-toolchain-2017.11-r0.arago36 do_package_qa: QA Issue: external-linaro-toolchain: /libmemusage/lib/libmemusage.so is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination [host-user-contaminated]
WARNING: external-linaro-toolchain-2017.11-r0.arago36 do_package_qa: QA Issue: external-linaro-toolchain: /external-linaro-toolchain-utils/usr/bin/sprof is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
external-linaro-toolchain: /external-linaro-toolchain-utils/usr/bin/locale is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
external-linaro-toolchain: /external-linaro-toolchain-utils/usr/bin/getent is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
external-linaro-toolchain: /external-linaro-toolchain-utils/usr/bin/makedb is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
external-linaro-toolchain: /external-linaro-toolchain-utils/usr/bin/rpcgen is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
external-linaro-toolchain: /external-linaro-toolchain-utils/usr/bin/getconf is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
external-linaro-toolchain: /external-linaro-toolchain-utils/usr/bin/pcprofiledump is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
external-linaro-toolchain: /external-linaro-toolchain-utils/usr/bin/pldd is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
external-linaro-toolchain: /external-linaro-toolchain-utils/usr/bin/gencat is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
external-linaro-toolchain: /external-linaro-toolchain-utils/usr/bin/iconv is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination [host-user-contaminated]
WARNING: external-linaro-toolchain-2017.11-r0.arago36 do_package_qa: QA Issue: external-linaro-toolchain: /glibc-thread-db/lib/libthread_db-1.0.so is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination [host-user-contaminated]
WARNING: external-linaro-toolchain-2017.11-r0.arago36 do_package_qa: QA Issue: external-linaro-toolchain: /ldd/usr/bin/ldd is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination [host-user-contaminated]
WARNING: external-linaro-toolchain-2017.11-r0.arago36 do_package_qa: QA Issue: No GNU_HASH in the elf binary: '/home/davide/tisdk/build/arago-tmp-external-linaro-toolchain/work/armv7ahf-neon-linux-gnueabi/external-linaro-toolchain/2017.11-r0.arago36/packages-split/libstdc++-dbg/lib/debug/libstdc++.so.6.0.24' [ldflags]
WARNING: external-linaro-toolchain-2017.11-r0.arago36 do_package_qa: QA Issue: non -staticdev package contains static .a library: libstdc++-dbg path '/work/armv7ahf-neon-linux-gnueabi/external-linaro-toolchain/2017.11-r0.arago36/packages-split/libstdc++-dbg/lib/debug/libstdc++.a'
non -staticdev package contains static .a library: libstdc++-dbg path '/work/armv7ahf-neon-linux-gnueabi/external-linaro-toolchain/2017.11-r0.arago36/packages-split/libstdc++-dbg/lib/debug/libstdc++fs.a' [staticdev]
WARNING: external-linaro-toolchain-2017.11-r0.arago36 do_package_qa: QA Issue: external-linaro-toolchain: /libstdc++-dbg/lib/debug/libstdc++.so.6.0.24 is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
external-linaro-toolchain: /libstdc++-dbg/lib/debug/libstdc++.a is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
external-linaro-toolchain: /libstdc++-dbg/lib/debug/libstdc++fs.a is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination [host-user-contaminated]
WARNING: external-linaro-toolchain-2017.11-r0.arago36 do_package_qa: QA Issue: external-linaro-toolchain: /libatomic/lib/libatomic.so.1.2.0 is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination [host-user-contaminated]
WARNING: external-linaro-toolchain-2017.11-r0.arago36 do_package_qa: QA Issue: external-linaro-toolchain: /libitm-staticdev/lib/libitm.a is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination [host-user-contaminated]
WARNING: external-linaro-toolchain-2017.11-r0.arago36 do_package_qa: QA Issue: external-linaro-toolchain: /libstdc++-staticdev/lib/libsupc++.a is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
external-linaro-toolchain: /libstdc++-staticdev/lib/libstdc++.a is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination [host-user-contaminated]
WARNING: external-linaro-toolchain-2017.11-r0.arago36 do_package_qa: QA Issue: external-linaro-toolchain: /tzcode/usr/bin/tzselect is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination [host-user-contaminated]
WARNING: external-linaro-toolchain-2017.11-r0.arago36 do_package_qa: QA Issue: external-linaro-toolchain: /libitm-dev/lib/libitm.spec is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination [host-user-contaminated]
WARNING: external-linaro-toolchain-2017.11-r0.arago36 do_package_qa: QA Issue: external-linaro-toolchain: /libsegfault/lib/libSegFault.so is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination [host-user-contaminated]
WARNING: external-linaro-toolchain-2017.11-r0.arago36 do_package_qa: QA Issue: external-linaro-toolchain: /libgfortran/lib/libgfortran.so.4.0.0 is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination [host-user-contaminated]
WARNING: external-linaro-toolchain-2017.11-r0.arago36 do_package_qa: QA Issue: external-linaro-toolchain: /libgcc-dev/usr/lib/libgcc.a is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
external-linaro-toolchain: /libgcc-dev/lib/libgcc_s.so is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination [host-user-contaminated]
WARNING: external-linaro-toolchain-2017.11-r0.arago36 do_package_qa: QA Issue: non -staticdev package contains static .a library: libgcc-dev path '/work/armv7ahf-neon-linux-gnueabi/external-linaro-toolchain/2017.11-r0.arago36/packages-split/libgcc-dev/usr/lib/libgcc.a' [staticdev]
WARNING: external-linaro-toolchain-2017.11-r0.arago36 do_package_qa: QA Issue: external-linaro-toolchain: /libgcc/lib/libgcc_s.so.1 is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination [host-user-contaminated]
WARNING: external-linaro-toolchain-2017.11-r0.arago36 do_package_qa: QA Issue: external-linaro-toolchain: /external-linaro-toolchain-staticdev/usr/lib/libutil.a is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
external-linaro-toolchain: /external-linaro-toolchain-staticdev/usr/lib/libg.a is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
external-linaro-toolchain: /external-linaro-toolchain-staticdev/usr/lib/librt.a is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
external-linaro-toolchain: /external-linaro-toolchain-staticdev/usr/lib/libmcheck.a is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
external-linaro-toolchain: /external-linaro-toolchain-staticdev/usr/lib/librpcsvc.a is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
external-linaro-toolchain: /external-linaro-toolchain-staticdev/usr/lib/libdl.a is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
external-linaro-toolchain: /external-linaro-toolchain-staticdev/usr/lib/libieee.a is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
external-linaro-toolchain: /external-linaro-toolchain-staticdev/usr/lib/libanl.a is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
external-linaro-toolchain: /external-linaro-toolchain-staticdev/usr/lib/libresolv.a is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
external-linaro-toolchain: /external-linaro-toolchain-staticdev/usr/lib/libm.a is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
external-linaro-toolchain: /external-linaro-toolchain-staticdev/usr/lib/libpthread.a is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
external-linaro-toolchain: /external-linaro-toolchain-staticdev/usr/lib/libBrokenLocale.a is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
external-linaro-toolchain: /external-linaro-toolchain-staticdev/usr/lib/libc.a is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
external-linaro-toolchain: /external-linaro-toolchain-staticdev/usr/lib/libcrypt.a is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
external-linaro-toolchain: /external-linaro-toolchain-staticdev/usr/lib/libnsl.a is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
external-linaro-toolchain: /external-linaro-toolchain-staticdev/lib/libasan.a is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
external-linaro-toolchain: /external-linaro-toolchain-staticdev/lib/libubsan.a is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
external-linaro-toolchain: /external-linaro-toolchain-staticdev/lib/libcilkrts.a is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
external-linaro-toolchain: /external-linaro-toolchain-staticdev/lib/libgfortran.a is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
external-linaro-toolchain: /external-linaro-toolchain-staticdev/lib/libstdc++fs.a is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination [host-user-contaminated]
WARNING: external-linaro-toolchain-2017.11-r0.arago36 do_package_qa: QA Issue: external-linaro-toolchain: /libubsan/lib/libubsan.so.0.0.0 is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination [host-user-contaminated]
WARNING: external-linaro-toolchain-2017.11-r0.arago36 do_package_qa: QA Issue: external-linaro-toolchain: /libgomp/lib/libgomp.so.1.0.0 is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination [host-user-contaminated]
WARNING: external-linaro-toolchain-2017.11-r0.arago36 do_package_qa: QA Issue: external-linaro-toolchain: /libsotruss/usr/lib/audit/sotruss-lib.so is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination [host-user-contaminated]
WARNING: external-linaro-toolchain-2017.11-r0.arago36 do_package_qa: QA Issue: external-linaro-toolchain: /external-linaro-toolchain-dev/usr/lib/Scrt1.o is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
external-linaro-toolchain: /external-linaro-toolchain-dev/usr/lib/crtfastmath.o is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
external-linaro-toolchain: /external-linaro-toolchain-dev/usr/lib/gcrt1.o is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
external-linaro-toolchain: /external-linaro-toolchain-dev/usr/lib/libpthread_nonshared.a is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
external-linaro-toolchain: /external-linaro-toolchain-dev/usr/lib/crtendS.o is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
external-linaro-toolchain: /external-linaro-toolchain-dev/usr/lib/crtbeginS.o is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
external-linaro-toolchain: /external-linaro-toolchain-dev/usr/lib/libc.so is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
external-linaro-toolchain: /external-linaro-toolchain-dev/usr/lib/Mcrt1.o is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
external-linaro-toolchain: /external-linaro-toolchain-dev/usr/lib/libpthread.so is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
external-linaro-toolchain: /external-linaro-toolchain-dev/usr/lib/crt1.o is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
external-linaro-toolchain: /external-linaro-toolchain-dev/usr/lib/crtbeginT.o is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
external-linaro-toolchain: /external-linaro-toolchain-dev/usr/lib/libc_nonshared.a is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
external-linaro-toolchain: /external-linaro-toolchain-dev/usr/lib/crtn.o is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
external-linaro-toolchain: /external-linaro-toolchain-dev/usr/lib/crtbegin.o is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
external-linaro-toolchain: /external-linaro-toolchain-dev/usr/lib/crti.o is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
external-linaro-toolchain: /external-linaro-toolchain-dev/usr/lib/crtend.o is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
external-linaro-toolchain: /external-linaro-toolchain-dev/lib/libasan_preinit.o is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination [host-user-contaminated]
WARNING: external-linaro-toolchain-2017.11-r0.arago36 do_package_qa: QA Issue: external-linaro-toolchain: /libasan/lib/libasan.so.4.0.0 is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination [host-user-contaminated]
WARNING: external-linaro-toolchain-2017.11-r0.arago36 do_package_qa: QA Issue: external-linaro-toolchain: /libssp-dev/lib/libssp_nonshared.a is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination [host-user-contaminated]
WARNING: external-linaro-toolchain-2017.11-r0.arago36 do_package_qa: QA Issue: external-linaro-toolchain: /external-linaro-toolchain/lib/libnss_files-2.25.so is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
external-linaro-toolchain: /external-linaro-toolchain/lib/libnss_nis-2.25.so is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
external-linaro-toolchain: /external-linaro-toolchain/lib/libnss_hesiod-2.25.so is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
external-linaro-toolchain: /external-linaro-toolchain/lib/libdl-2.25.so is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
external-linaro-toolchain: /external-linaro-toolchain/lib/libnsl-2.25.so is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
external-linaro-toolchain: /external-linaro-toolchain/lib/libnss_compat-2.25.so is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
external-linaro-toolchain: /external-linaro-toolchain/lib/librt-2.25.so is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
external-linaro-toolchain: /external-linaro-toolchain/lib/libBrokenLocale-2.25.so is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
external-linaro-toolchain: /external-linaro-toolchain/lib/libutil-2.25.so is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
external-linaro-toolchain: /external-linaro-toolchain/lib/ld-2.25.so is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
external-linaro-toolchain: /external-linaro-toolchain/lib/libpthread-2.25.so is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
external-linaro-toolchain: /external-linaro-toolchain/lib/libnss_dns-2.25.so is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
external-linaro-toolchain: /external-linaro-toolchain/lib/libm-2.25.so is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
external-linaro-toolchain: /external-linaro-toolchain/lib/libc-2.25.so is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
external-linaro-toolchain: /external-linaro-toolchain/lib/libnss_nisplus-2.25.so is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
external-linaro-toolchain: /external-linaro-toolchain/lib/libresolv-2.25.so is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
external-linaro-toolchain: /external-linaro-toolchain/lib/libcrypt-2.25.so is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
external-linaro-toolchain: /external-linaro-toolchain/lib/libanl-2.25.so is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination
external-linaro-toolchain: /external-linaro-toolchain/sbin/ldconfig is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination [host-user-contaminated]
WARNING: external-linaro-toolchain-2017.11-r0.arago36 do_package_qa: QA Issue: external-linaro-toolchain: /libgfortran-dev/lib/libgfortran.spec is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination [host-user-contaminated]
WARNING: external-linaro-toolchain-2017.11-r0.arago36 do_package_qa: QA Issue: external-linaro-toolchain: /libgomp-staticdev/lib/libgomp.a is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination [host-user-contaminated]
WARNING: external-linaro-toolchain-2017.11-r0.arago36 do_package_qa: QA Issue: external-linaro-toolchain: /catchsegv/usr/bin/catchsegv is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination [host-user-contaminated]
WARNING: external-linaro-toolchain-2017.11-r0.arago36 do_package_qa: QA Issue: external-linaro-toolchain: /libssp-staticdev/lib/libssp.a is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination [host-user-contaminated]
WARNING: external-linaro-toolchain-2017.11-r0.arago36 do_package_qa: QA Issue: external-linaro-toolchain: /libatomic-staticdev/lib/libatomic.a is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination [host-user-contaminated]
WARNING: external-linaro-toolchain-2017.11-r0.arago36 do_package_qa: QA Issue: external-linaro-toolchain: /libssp/lib/libssp.so.0.0.0 is owned by uid 1000, which is the same as the user running bitbake. This may be due to host contamination [host-user-contaminated]
NOTE: Tasks Summary: Attempted 4284 tasks of which 6 didn't need to be rerun and all succeeded.

Summary: There were 42 WARNING messages shown.
davide@davide-P553UA:~/tisdk/build$ MACHINE=am335x-evm bitbake -c populate_sdk arago-base-tisdk-image
Loading cache: 100% |############################################| Time: 0:00:01
Loaded 4045 entries from dependency cache.
Parsing recipes: 100% |##########################################| Time: 0:00:14
Parsing of 3139 .bb files complete (3136 cached, 3 parsed). 4048 targets, 484 skipped, 0 masked, 0 errors.
WARNING: No recipes available for:
/home/davide/tisdk/sources/meta-arago/meta-arago-distro/recipes-multimedia/gstreamer/gstreamer1.0-plugins-base_1.8.3.bbappend
/home/davide/tisdk/sources/meta-processor-sdk/recipes-devtools/python/python3-native_3.5.2.bbappend
/home/davide/tisdk/sources/meta-processor-sdk/recipes-graphics/wayland/weston_1.11.0.bbappend
NOTE: Resolving any missing task queue dependencies

Build Configuration:
BB_VERSION = "1.36.0"
BUILD_SYS = "x86_64-linux"
NATIVELSBSTRING = "ubuntu-16.04"
TARGET_SYS = "arm-linux-gnueabi"
MACHINE = "am335x-evm"
DISTRO = "arago"
DISTRO_VERSION = "2018.04"
TUNE_FEATURES = "arm armv7a vfp thumb neon callconvention-hard"
TARGET_FPU = "hard"
meta-processor-sdk = "HEAD:264dc66c689e0e4212c43358382986ee470619d4"
meta-ros = "HEAD:e2566402ab108a19634354a934788109422cf409"
meta-arago-distro
meta-arago-extras = "HEAD:d54e9d6c1d461dbf3189e691088d328bf4c4fb19"
meta-browser = "HEAD:26d50665e2f7223c5f4ad7481a8d2431e7cb55fb"
meta-qt5 = "HEAD:682ad61c071a9710e9f9d8a32ab1b5f3c14953d1"
meta-networking
meta-python
meta-oe
meta-gnome
meta-multimedia = "HEAD:352531015014d1957d6444d114f4451e241c4d23"
meta-ti = "HEAD:8555084679dc5c668e5fb60a16425ca32b10ff21"
meta-linaro-toolchain
meta-optee = "HEAD:75dfb67bbb14a70cd47afda9726e2e1c76731885"
meta = "HEAD:931a52e8698f684ccbb26ddec18764ad9d9a3e8f"

Initialising tasks: 100% |#######################################| Time: 0:00:11
NOTE: Executing SetScene Tasks
NOTE: Executing RunQueue Tasks
ERROR: arago-base-tisdk-image-1.0-r0 do_populate_sdk: Unable to install packages. Command '/home/davide/tisdk/build/arago-tmp-external-linaro-toolchain/work/am335x_evm-linux-gnueabi/arago-base-tisdk-image/1.0-r0/recipe-sysroot-native/usr/bin/opkg --volatile-cache -f /home/davide/tisdk/build/arago-tmp-external-linaro-toolchain/work/am335x_evm-linux-gnueabi/arago-base-tisdk-image/1.0-r0/opkg.conf -t /home/davide/tisdk/build/arago-tmp-external-linaro-toolchain/work/am335x_evm-linux-gnueabi/arago-base-tisdk-image/1.0-r0/temp/ipktemp/ -o /home/davide/tisdk/build/arago-tmp-external-linaro-toolchain/work/am335x_evm-linux-gnueabi/arago-base-tisdk-image/1.0-r0/sdk/image/tmp/xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx/yyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyyy/sysroots/armv7ahf-neon-linux-gnueabi --force_postinstall install systemd-initramfs packagegroup-arago-base-tisdk packagegroup-arago-console packagegroup-arago-test packagegroup-arago-base psplash run-postinsts packagegroup-core-boot packagegroup-core-standalone-sdk-target opkg' returned 1:
Collected errors:
* Solver encountered 1 problem(s):
* Problem 1/1:
* - nothing provides libatomic-dev needed by packagegroup-core-standalone-sdk-target-1.0-r8.all
*
* Solution 1:
* - do not ask to install a package providing packagegroup-core-standalone-sdk-target



ERROR: arago-base-tisdk-image-1.0-r0 do_populate_sdk: Function failed: do_populate_sdk
ERROR: Logfile of failure stored in: /home/davide/tisdk/build/arago-tmp-external-linaro-toolchain/work/am335x_evm-linux-gnueabi/arago-base-tisdk-image/1.0-r0/temp/log.do_populate_sdk.9702
ERROR: Task (/home/davide/tisdk/sources/meta-arago/meta-arago-distro/recipes-core/images/arago-base-tisdk-image.bb:do_populate_sdk) failed with exit code '1'
NOTE: Tasks Summary: Attempted 4515 tasks of which 3310 didn't need to be rerun and 1 failed.

Summary: 1 task failed:
/home/davide/tisdk/sources/meta-arago/meta-arago-distro/recipes-core/images/arago-base-tisdk-image.bb:do_populate_sdk
Summary: There was 1 WARNING message shown.
Summary: There were 2 ERROR messages shown, returning a non-zero exit code.

Hi Davidino,

On the following TI page, you will find instructions on building the SDK. I was successfully able to build without any errors. Could you please follow the steps mentioned in the guide and see if you are still getting errors? Also, as Ron mentioned, have you made any modifications on your machine because it should build without needing to change any files.

Regards,

Krunal

Hello Krunal, thank you for your message.

• Since I've been working with Arago, I've always followed the steps that you indicated with your link software-dl.ti.com/.../Overview.html
• I' ve never changed the local.conf file contained in the build folder.
• The only thing that I did, consisted of making a copy of arago-base-sdk-image.bb recipe, and customize it.
• Today, I've erased everything on my PC, and started from the scratch the process for building the arago-base-sdk-image. It doesn't change a thing.
  In my previous post I've pasted all the steps that I do. More specifically, the image is created even though, it generate several warnings (see previous post).

The error arises when I use the command MACHINE=am335x-evm bitbake -c populated_sdk arago-base-tisdk-image, (see previous post for the error).

I know that this command it's not listed in the arago procedures, but it does exist in yocto for making a toolchain matching the platform with a sysroot folder matching our target root filesystem. Is it normal??

Thank you for your help.

Davidino

Hi Davidino,

I have reached out to our Yocto experts and I will keep you posted on any updates.

Regards,
Krunal

Hello Krunal,

are there any news about my issue?

Please consider that without cross-complied libraries and a cross-compiler, based on the image, I cannot even start to develop applications. I'm completely stuck..

Thank you for your help.

Hi Davidino,

After discussing with few folks, I found out that you need to use “meta-toolchain-arago” or “meta-toolchain-arago-tisdk” to build the toolchain installer. Unfortunately, “populate_sdk” will not work and as a reference, please refer to the following link.

Regards,

Krunal

Hello krunal,

thank you very much for your answers and patience. Just to recap, this is my idea of the differences between yocto and arago concerning the cross-compiler, please correct me if I'm wrong:

• In YOCTO, with bitbake -c populate_sdk, I can create a cross-compiler with a sysroot folder matching our target root filesystem. In other words if in a custom image recipe I add IMAGE_INSTALL += " opencv", using -c populate_sdk, I get opencv cross-compiled libraries in my sysroot folder. This is very convinient because the SDK contains exactly whatever change is done to the image recipe.
  
  
• In ARAGO, with bitbake meta-toolchain-arago-tisdk, I have several cross-compiled libraries but they don't match the target root filesystem. As example, if I create the image arago-base-tisdk-image, clearly this image doesn't contain opencv but inside meta-toolchain sysroot, opencv libraries DO exist. I suppose that if I need to add something that is not contained in meta-toolcain-arago-tisdk sysroots, the meta-toolchain-arago-tisdk recipe has to be customized and it doesn't seem as easy as with images.

Last question: What is the difference between arago-base-image and arago-base-tisdk-image ?

Thank you

FYI, I just created an FAQ on this topic, showing how the '-c populate_sdk' step can be made work if one must use it.

e2e.ti.com/.../faq-am6x-using-a-yocto-internal-toolchain-for-target-image-builds-and-cross-development-sdk-installer-generation-with-yocto-dunfell-based-v8-x-sdks-for-sitara-mpus