I kicked off bitbake -k angstrom-lxde-image one directory up from the build directory - what damage have I done?
I let it run to completion despite errors, then got into the correct directory. Note this is on Ubuntu 18, perhaps that is a problem, since I still have 4 errors.
Here’s the log:
WARNING: No recipes available for:
NOTE: Resolving any missing task queue dependencies
BB_VERSION = “1.36.0”
BUILD_SYS = “x86_64-linux”
NATIVELSBSTRING = “ubuntu-18.04”
TARGET_SYS = “arm-angstrom-linux-gnueabi”
MACHINE = “colibri-imx7”
DISTRO = “angstrom”
DISTRO_VERSION = “v2017.12”
TUNE_FEATURES = “arm armv7a vfp thumb neon callconvention-hard”
TARGET_FPU = “hard”
meta-angstrom = “HEAD:3eafb0073465e4808769e7a8ed9d90c83d665868”
meta-toradex-nxp = “HEAD:529a2981915e52cd6a9f4772af65ac225d29f754”
meta-freescale = “HEAD:49ac225a38f6d84519798e3264f2e4d19b84f70a”
meta-freescale-3rdparty = “HEAD:1d6d5961dbf82624b28bb318b4950a64abc31d12”
meta-toradex-tegra = “HEAD:83d29c9dde04d0c8f2460831a6b22bce6579a72e”
meta-jetson-tk1 = “HEAD:e8b87fe8da7c6fcffa37ab245f50082953cc1ee1”
meta-toradex-bsp-common = “HEAD:78612101254076847875278a3f24afa1966dfea0”
meta-python = “HEAD:dacfa2b1920e285531bec55cd2f08743390aaf57”
meta-lxde = “HEAD:dbcbbfd9539a9a017bb6c9b7fd67c3ca22c4cacf”
meta-browser = “HEAD:cf35eca0de52d5a34dabe2068e68348367db8e55”
meta-qt4 = “HEAD:f313dbee2ac3d5fcc9801407947d3cb6cfb90b5d”
meta-qt5 = “HEAD:32bb7d18a08d1c48873d7ab6332d4cc3815a4dff”
meta-qt5-extra = “HEAD:b5bde85b0144877a746656b4567240d68c6c1980”
meta-freescale-distro = “HEAD:0ec6d7e206705702b5b534611754de0787f92b72”
meta-toradex-demos = “HEAD:aa265d1c86597e479629734145b638b51117ef02”
meta = “HEAD:b042347ee8cdbd2dfb0c2f616a94c4cca4b0ecd1”
NOTE: Executing SetScene Tasks
NOTE: Executing RunQueue Tasks
NOTE: Running task 568 of 8232 (virtual:native:/home/steve/oe-core/build/…/layers/openembedded-core/meta/recipes-devtools/e2fsprogs/e2fsprogs_1.43.5.bb:do_compile)
NOTE: recipe e2fsprogs-native-1.43.5-r0: task do_compile: Started
NOTE: Running task 946 of 8232 (virtual:native:/home/steve/oe-core/build/…/layers/openembedded-core/meta/recipes-devtools/qemu/qemu_2.10.0.bb:do_compile)
NOTE: recipe qemu-native-2.10.0-r0: task do_compile: Started
ERROR: e2fsprogs-native-1.43.5-r0 do_compile: oe_runmake failed
ERROR: e2fsprogs-native-1.43.5-r0 do_compile: Function failed: do_compile (log file is located at /home/steve/oe-core/build/tmp-glibc/work/x86_64-linux/e2fsprogs-native/1.43.5-r0/temp/log.do_compile.14232)
ERROR: Logfile of failure stored in: /home/steve/oe-core/build/tmp-glibc/work/x86_64-linux/e2fsprogs-native/1.43.5-r0/temp/log.do_compile.14232
NOTE: recipe e2fsprogs-native-1.43.5-r0: task do_compile: Failed
ERROR: Task (virtual:native:/home/steve/oe-core/build/…/layers/openembedded-core/meta/recipes-devtools/e2fsprogs/e2fsprogs_1.43.5.bb:do_compile) failed with exit code ‘1’
ERROR: qemu-native-2.10.0-r0 do_compile: oe_runmake failed
ERROR: qemu-native-2.10.0-r0 do_compile: Function failed: do_compile (log file is located at /home/steve/oe-core/build/tmp-glibc/work/x86_64-linux/qemu-native/2.10.0-r0/temp/log.do_compile.14233)
ERROR: Logfile of failure stored in: /home/steve/oe-core/build/tmp-glibc/work/x86_64-linux/qemu-native/2.10.0-r0/temp/log.do_compile.14233
NOTE: recipe qemu-native-2.10.0-r0: task do_compile: Failed
ERROR: Task (virtual:native:/home/steve/oe-core/build/…/layers/openembedded-core/meta/recipes-devtools/qemu/qemu_2.10.0.bb:do_compile) failed with exit code ‘1’
NOTE: Tasks Summary: Attempted 2176 tasks of which 2174 didn’t need to be rerun and 2 failed.
NOTE: Writing buildhistory
From High performance, low power Embedded Computing Systems | Toradex Developer Center, the instructions for Ubuntu 16 yield this error on Ubuntu 18:
steve@steve-OptiPlex-7020:~/oe-core$ sudo apt-get install libcrypto++9v5:i386
Reading package lists… Done
Building dependency tree
Reading state information… Done
E: Unable to locate package libcrypto++9v5:i386
E: Couldn’t find any package by regex ‘libcrypto++9v5’
Is there a new package the Ubuntu 18, or do I need a Ubuntu 16 machine?
What exact hardware and software versions of things are you talking about? Please note that Ubuntu 18.04 is not yet supported but should be as of our next round of Q2 updates.
Dear @stevea1949, as Marcel states, currently our active head does not build in Ubuntu 18.04 due to a collision with some of the functions in e2fsprogs, but this may change depending on the machine you are compiling for (for better or worse). The best workaround is to compile in a Ubuntu 16.04 machine. However we found out that some backports could be applied in order to succesfully build as-is. More info here.
I’m building for iMX7, from local.conf:
MACHINE ?= “colibri-imx7”
rest remain commented out.
I also have a line:
ACCEPT_FSL_EULA = “1”
The build PC is a Dell OptiPlex-7020 with 4.15.0-22-generic #24-Ubuntu SMP Wed May 16
The target hardware is Col Evaluation V3.2B, iMX7S 256MB V1.1B
Oh, and from ~/poky/build, a “bitbake core-image-minimal” will run to completion after sourcing oe-init-build-env with only one warning (“ubuntu-18.04” has not been validated), but from ~/oe-core/build it fails (after “. ./export”).
but from ~/oe-core/build it fails (after “. ./export”).
You mean from ~/oe-core/?
. export or
source export should be launched from the root of the oe-core folder.
Also, checking the errors from your question it definitely looks like this is the issue (e2fsprogs and qemu). Please check the original answer to the link for the post where the solution for Ubuntu 18.04 is posted. If still the
. export command is not working, you may retry by cloning the repo again.
I followed the guidance from the link in your answer (fix the conflict with the definition of memfd_create and changed instances of copy_file_range to copy_file_chunk as per the referenced patch), and the new build appears to be working, Thanks!
Thanks for the feedback, glad to know it solved it!