Expansion error, unsupported architecture meta-mender-core

93 views
Skip to first unread message

LoveMeow

unread,
Dec 11, 2017, 4:10:08 AM12/11/17
to Mender List mender.io
When I run:
bitbake show-layers

I get the following error :
ERROR: ExpansionError during parsing repositories/meta-mender/meta-mender-core/recipes-mender/mender-artifact/mender-artifact_2.1.1.bb: Failure expanding variable GOPTESTBUILDFLAGS: SkipPackage: Unsupported CPU architecture: ${TUNE_ARCH}

I tried to look for this variable but I cannot find it.

Where could the error be?

Meow

Kristian Amlie

unread,
Dec 11, 2017, 4:19:40 AM12/11/17
to men...@lists.mender.io, LoveMeow
There must be something wrong with the build setup, this variable should
always be set [1]. I would try to build without Mender first and verify
that it works.

[1]
http://www.yoctoproject.org/docs/latest/mega-manual/mega-manual.html#var-TUNE_ARCH

--
Kristian

LoveMeow

unread,
Dec 11, 2017, 4:33:24 AM12/11/17
to Mender List mender.io, ramapriya...@rapyuta-robotics.com
Hi,

Thanks for your reply, it seems to work fine without mender, additionally, when I run bitbake vim for example I get the same error.

Meow

LoveMeow

unread,
Dec 11, 2017, 4:40:33 AM12/11/17
to Mender List mender.io, ramapriya...@rapyuta-robotics.com
I am also able to successfully bitbake vim without the mender core layer


On Monday, December 11, 2017 at 10:19:40 AM UTC+1, Kristian Amlie wrote:

Kristian Amlie

unread,
Dec 11, 2017, 4:44:34 AM12/11/17
to men...@lists.mender.io, LoveMeow
On 11/12/17 10:33, LoveMeow wrote:
> Hi,
>
> Thanks for your reply, it seems to work fine without mender,
> additionally, when I run bitbake vim for example I get the same error.

Hmm, the Yocto documentation says that TUNE_ARCH should always be set,
but it doesn't seem to be present in all the architecture specific
include directories. Maybe this is a bug on their part.

What is the MACHINE you're building for? And when you build, can you
check what TUNE_FEATURES is set to? Both are usually listed near the top
of the build output.

--
Kristian

> On Monday, December 11, 2017 at 10:19:40 AM UTC+1, Kristian Amlie wrote:
>
> On 11/12/17 10:10, LoveMeow wrote:
> > When I run:
> > bitbake show-layers
> >
> > I get the following error :
> > ERROR: ExpansionError during parsing
> >
> repositories/meta-mender/meta-mender-core/recipes-mender/mender-artifact/mender-artifact_2.1.1.bb
> <http://mender-artifact_2.1.1.bb>:
> > Failure expanding variable GOPTESTBUILDFLAGS: SkipPackage:
> Unsupported
> > CPU architecture: ${TUNE_ARCH}
> >
> > I tried to look for this variable but I cannot find it.
> >
> > Where could the error be?
>
> There must be something wrong with the build setup, this variable
> should
> always be set [1]. I would try to build without Mender first and verify
> that it works.
>
> [1]
> http://www.yoctoproject.org/docs/latest/mega-manual/mega-manual.html#var-TUNE_ARCH
> <http://www.yoctoproject.org/docs/latest/mega-manual/mega-manual.html#var-TUNE_ARCH>
>
>
> --
> Kristian
>
> --
> You received this message because you are subscribed to the Google
> Groups "Mender List mender.io" group.
> To unsubscribe from this group and stop receiving emails from it, send
> an email to mender+un...@lists.mender.io
> <mailto:mender+un...@lists.mender.io>.
> To post to this group, send email to men...@lists.mender.io
> <mailto:men...@lists.mender.io>.
> Visit this group at
> https://groups.google.com/a/lists.mender.io/group/mender/.

LoveMeow

unread,
Dec 11, 2017, 4:54:58 AM12/11/17
to Mender List mender.io, ramapriya...@rapyuta-robotics.com
I am building for Apalis Imx6, I dont see any if the things you mentions at the ild output, this is what I get:

bitbake vim
NOTE: Trying for parse version info from: gcc version 5.2.1 20151005 (Linaro GCC 5.2-2015.11-2)
NOTE: Trying for parse version info from: gcc version 5.2.1 20151005 (Linaro GCC 5.2-2015.11-2)
NOTE: Trying for parse version info from: gcc version 5.2.1 20151005 (Linaro GCC 5.2-2015.11-2)
Loading cache: 100% |######################################################################################################################| ETA:  00:00:00
Loaded 995 entries from dependency cache.
NOTE: Error during finalise of /home/rama/repositories/meta-mender/meta-mender-core/recipes-mender/mender-artifact/mender-artifact_2.0.0.bb| ETA:  --:--:--
NOTE: Error during finalise of /home/rama/repositories/meta-mender/meta-mender-core/recipes-mender/mender-artifact/mender-artifact_git.bb
NOTE: Error during finalise of /home/rama/repositories/meta-mender/meta-mender-core/recipes-mender/mender-artifact/mender-artifact_2.0.1.bb
NOTE: Error during finalise of /home/rama/repositories/meta-mender/meta-mender-core/recipes-mender/mender-artifact/mender-artifact_2.1.1.bb
NOTE: Error during finalise of /home/rama/repositories/meta-mender/meta-mender-core/recipes-mender/mender-artifact/mender-artifact_1.0.0.bb
NOTE: Error during finalise of /home/rama/repositories/meta-mender/meta-mender-core/recipes-mender/mender-artifact/mender-artifact_2.0.2.bb
NOTE: Error during finalise of /home/rama/repositories/meta-mender/meta-mender-core/recipes-mender/mender-artifact/mender-artifact_2.1.0.bb
NOTE: Error during finalise of /home/rama/repositories/meta-mender/meta-mender-core/recipes-mender/mender/mender_1.3.0b1.bb
NOTE: Error during finalise of /home/rama/repositories/meta-mender/meta-mender-core/recipes-mender/mender/mender_1.2.1.bb
NOTE: Error during finalise of /home/rama/repositories/meta-mender/meta-mender-core/recipes-mender/mender/mender_1.1.0.bb
NOTE: Error during finalise of /home/rama/repositories/meta-mender/meta-mender-core/recipes-mender/mender/mender_git.bb
NOTE: Error during finalise of /home/rama/repositories/meta-mender/meta-mender-core/recipes-mender/mender/mender_1.0.0.bb
NOTE: Error during finalise of /home/rama/repositories/meta-mender/meta-mender-core/recipes-mender/mender/mender_1.2.0.bb
NOTE: Error during finalise of /home/rama/repositories/meta-mender/meta-mender-core/recipes-mender/mender/mender_1.1.2.bb
NOTE: Error during finalise of /home/rama/repositories/meta-mender/meta-mender-core/recipes-mender/mender/mender_1.1.1.bb
NOTE: Error during finalise of /home/rama/repositories/meta-mender/meta-mender-core/recipes-mender/mender/mender_1.0.1.bb
ERROR: ExpansionError during parsing /home/rama/repositories/meta-mender/meta-mender-core/recipes-mender/mender-artifact/mender-artifact_2.0.0.bb: Failure expanding variable GOBIN_FINAL: SkipPackage: Unsupported CPU architecture: ${TUNE_ARCH}

Where else could I check?

LoveMeow

unread,
Dec 11, 2017, 5:01:18 AM12/11/17
to Mender List mender.io, ramapriya...@rapyuta-robotics.com
I also manually set the tune_arch variable to be = "arm", now i get the above error plus some more like the following:


bitbake vim
NOTE: Trying for parse version info from: gcc version 5.2.1 20151005 (Linaro GCC 5.2-2015.11-2)
NOTE: Trying for parse version info from: gcc version 5.2.1 20151005 (Linaro GCC 5.2-2015.11-2)
NOTE: Trying for parse version info from: gcc version 5.2.1 20151005 (Linaro GCC 5.2-2015.11-2)
ERROR: Task do_rootfs_wicenv from /oe-core/build/../stuff/meta-toradex/recipes/images/qt4e-demo-image.bb seems to be empty?!                   | ETA:  00:00:49
ERROR: Task do_rootfs_wicenv from /oe-core/build/../stuff/meta-toradex/recipes/images/angstrom-qt-x11-image.bb seems to be empty?!
ERROR: Task do_rootfs_wicenv from /oe-core/build/../stuff/meta-toradex/recipes/images/console-trdx-image.bb seems to be empty?!
ERROR: Task do_rootfs_wicenv from /oe-core/build/../stuff/meta-toradex/recipes/images/angstrom-qt5-x11-image.bb seems to be empty?!
ERROR: Task do_rootfs_wicenv from /oe-core/build/../stuff/meta-toradex/recipes/images/angstrom-lxde-image.bb seems to be empty?!
ERROR: Task do_rootfs_wicenv from /oe-core/build/../stuff/meta-openembedded/meta-initramfs/recipes-bsp/images/initramfs-kexecboot-image.bb seems to be empty?!2
ERROR: Task do_rootfs_wicenv from /oe-core/build/../stuff/meta-openembedded/meta-initramfs/recipes-bsp/images/initramfs-kexecboot-klibc-image.bb seems to be empty?!
ERROR: Task do_rootfs_wicenv from /oe-core/build/../stuff/meta-openembedded/meta-initramfs/recipes-bsp/images/initramfs-debug-image.bb seems to be empty?!00:56
ERROR: Task do_rootfs_wicenv from /oe-core/build/../stuff/meta-ros/recipes-core/images/core-image-ros-roscore.bb seems to be empty?!           | ETA:  00:00:42
ERROR: Task do_rootfs_wicenv from /oe-core/build/../stuff/meta-ros/recipes-core/images/core-image-ros-world.bb seems to be empty?!
ERROR: Task do_rootfs_wicenv from /oe-core/build/../stuff/meta-ros/recipes-core/images/test-image.bb seems to be empty?!
ERROR: Task do_rootfs_wicenv from /oe-core/build/../stuff/meta-openembedded/meta-xfce/recipes-core/images/core-image-minimal-xfce.bb seems to be empty?!0:00:35
ERROR: Task do_rootfs_wicenv from /oe-core/build/../stuff/meta-angstrom/recipes-images/angstrom/systemd-gnome-image.bb seems to be empty?!     | ETA:  00:00:32
ERROR: Task do_rootfs_wicenv from /oe-core/build/../stuff/meta-angstrom/recipes-images/angstrom/console-image.bb seems to be empty?!
ERROR: Task do_rootfs_wicenv from /oe-core/build/../stuff/meta-angstrom/recipes-images/angstrom/hardware-bringup-image.bb seems to be empty?!
ERROR: Task do_rootfs_wicenv from /oe-core/build/../stuff/meta-angstrom/recipes-images/angstrom/angstrom-image.bb seems to be empty?!
ERROR: Task do_rootfs_wicenv from /oe-core/build/../stuff/meta-angstrom/recipes-images/angstrom/development-gnome-image.bb seems to be empty?!
ERROR: Task do_rootfs_wicenv from /oe-core/build/../stuff/meta-angstrom/recipes-images/angstrom/xfce-nm-image.bb seems to be empty?!           | ETA:  00:00:31
ERROR: Task do_rootfs_wicenv from /oe-core/build/../stuff/meta-angstrom/recipes-images/angstrom/efl-nodm-image.bb seems to be empty?!
ERROR: Task do_rootfs_wicenv from /oe-core/build/../stuff/meta-angstrom/recipes-images/angstrom/systemd-image.bb seems to be empty?!
ERROR: Task do_rootfs_wicenv from /oe-core/build/../stuff/meta-angstrom/recipes-images/angstrom/development-xfce-image.bb seems to be empty?!
ERROR: Task do_rootfs_wicenv from /oe-core/build/../stuff/meta-angstrom/recipes-images/maker/octoprint-image.bb seems to be empty?!
ERROR: Task do_rootfs_wicenv from /oe-core/build/../stuff/meta-angstrom/recipes-images/angstrom/console-base-image.bb seems to be empty?!
NOTE: Error during finalise of /home/rama/repositories/meta-mender/meta-mender-core/recipes-mender/mender-artifact/mender-artifact_2.0.0.bb    | ETA:  00:00:31
ERROR: ExpansionError during parsing /home/rama/repositories/meta-mender/meta-mender-core/recipes-mender/mender-artifact/mender-artifact_2.0.0.bb: Failure expanding variable GOBIN_FINAL: SkipPackage: Unsupported CPU architecture: ${TUNE_ARCH}

NOTE: Error during finalise of /home/rama/repositories/meta-mender/meta-mender-core/recipes-mender/mender-artifact/mender-artifact_git.bb
NOTE: Error during finalise of /home/rama/repositories/meta-mender/meta-mender-core/recipes-mender/mender-artifact/mender-artifact_2.0.2.bb
NOTE: Error during finalise of /home/rama/repositories/meta-mender/meta-mender-core/recipes-mender/mender-artifact/mender-artifact_2.1.1.bb
NOTE: Error during finalise of /home/rama/repositories/meta-mender/meta-mender-core/recipes-mender/mender-artifact/mender-artifact_2.0.1.bb
NOTE: Error during finalise of /home/rama/repositories/meta-mender/meta-mender-core/recipes-mender/mender-artifact/mender-artifact_1.0.0.bb
NOTE: Error during finalise of /home/rama/repositories/meta-mender/meta-mender-core/recipes-mender/mender-artifact/mender-artifact_2.1.0.bb

Summary: There were 24 ERROR messages shown, returning a non-zero exit code.


I thought the error should have been gone since I set tune_arch? Why is it that it works without the mender layer?

Meow

Kristian Amlie

unread,
Dec 11, 2017, 5:02:20 AM12/11/17
to men...@lists.mender.io, LoveMeow
You need to check this without Mender or else it won't build.

--
Kristian

LoveMeow

unread,
Dec 11, 2017, 5:06:50 AM12/11/17
to Mender List mender.io, ramapriya...@rapyuta-robotics.com
It builds without mender, or have I misunderstood you?
Reply all
Reply to author
Forward
0 new messages