No Open Embedded Toolchain


Apologies if this questions is rather basic, I’m a bit new to this.
I have downloaded the OpenEmbedded BSP 2.8. I have added a recipe and compiled the new recipe without problem.

However, I also need to make some minor kernel changes. I have downloaded the kernel source and run “make nconfig” to add new kernel features, as required. No problem.

Problems arise when I try to compile the kernel using the OpenEmbedded toolchain.
It appears I do not have a toolchain in the expected folder “~/oe-core/build/tmp-glibc/sysroots/x86_64-linux/”.
All that I have in the “~/oe-core/build/tmp-glibc/sysroots” folder is a colibri-vf folder.

What could I be doing wrong?

Hi @ashinton

Could you provide the version of the hardware and software of your module?

Regarding you issue, could you have a look here?

Best regards,

Hardware: Colibri VF50 128MB | V1.2B
Software: Linux BSP Release 2.8

I’m trying to compile the kernel outside of OpenEmbedded, but using the OpenEmbedded toolchain, as described in your article “How to setup environment for Embedded Linux application development”. However, despite doing an OpenEmbedded build, the toolchain is not present in the folder “~/oe-core/build/tmp-glibc/sysroots/x86_64-linux/”.

Hi @ashinton

It is not possible to do the build without the Toolchain. I checked it myself and found out that meanwhile the toolchain in moved to a different folder: oe-core2_8/build/tmp-glibc/sysroots-components/x86_64. We will update this developer article.

Usually you should build the SDK using -c populate_sdk option.

Best regards,

So what environment variables do we now set to use the OpenEmbedded toolchain to build the kernel?

The environment variables specified in the article “Build U-Boot and Linux Kernel from Source Code” are as follows:

export ARCH=arm
export PATH=~/oe-core/build/tmp-glibc/sysroots/x86_64-linux/usr/bin:~/oe-core/build/tmp-glibc/sysroots/x86_64-linux/usr/bin/arm-angstrom-linux-gnueabi/:$PATH
export CROSS_COMPILE=arm-angstrom-linux-gnueabi-

What should this change to when using the Linux BSP Release 2.8?

hi @ashinton

We are working on this issue and will come back soon to you.

Best regards,