Problem with Angstrom SDK installer

Technical Support
, , , ,
1

Hi,

I’m trying to install the generated SDK with the Angstrom Installer but the process always hangs after extracting the sysroot. It fails to find some shell scripts.

I’m calling the installer like this from build directory:

../deploy/sdk/angstrom-glibc-x86_64-armv7at2hf-neon-v2016.12-toolchain.sh -S

Output:

Angstrom SDK installer version nodistro.0
    =========================================
    Enter target directory for SDK (default: /usr/local/oecore-x86_64): /usr/local/oecore-x86_64
    You are about to install the SDK to "/usr/local/oecore-x86_64". Proceed[Y/n]? 
    Extracting SDK.....................................................................................................................................................................................................done
    Setting it up...ls: cannot access '/usr/local/oecore-x86_64/environment-setup-*': No such file or directory

The sysroot directory is 4.8GB in size so not much seems to be missing except for the build environment scripts.

2

Which Linux distribution do you use on which you are trying to install the SDK and did the OE build?

3

I’m using ubuntu 16.10. The OE was built without errors. It also runs on the board without any problem. Just the SDK fails to install.

4

Exact same problem here on Ubuntu 16.10 as well. Using this SDK though:

angstrom-glibc-x86_64-armv7at2hf-vfp-neon-v2015.12-toolchain.sh

5

Hi

I assume you did build the SDK with -c populate_sdk and you used the image recipe angstrom-qt5-x11-image.

Recent changes seem to make the order in which the classes populate_sdk and populate_sdk_qt5 are inherited matter and angstrom-qt5-x11-image does it in the wrong order.

Adding populate_sdk before populate_sdk_qt5 forces the correct order. I added this commit which does this.

Max

6

I am also having this same problem

$ ./angstrom-glibc-x86_64-armv7at2hf-neon-v2017.12-toolchain.sh
Angstrom SDK installer version nodistro.0
=========================================
Enter target directory for SDK (default: /usr/local/oecore-x86_64): 
You are about to install the SDK to "/usr/local/oecore-x86_64". Proceed[Y/n]? 
Extracting SDK.................................................................................done
Setting it up...ls: cannot access '/usr/local/oecore-x86_64/environment-setup-*': No such file or directory

but this using the console-tdx-image recipe.

I’m building the SDK with “bitbake console-tdx-image -c populate_sdk”.

It was working fine before with my earlier builds of the sdk but suddenly I’m getting this error. I’ve spent hours trying to figure out what may have changed inbetween but I’m at a loss. I have also tried building and installing on a different machine but I get the same result.

Build host is Ubuntu 16.04 and I’m building for colibri-imx7-emmc, build config output follows:

Build Configuration:
BB_VERSION           = "1.36.0"
BUILD_SYS            = "x86_64-linux"
NATIVELSBSTRING      = "ubuntu-16.04"
TARGET_SYS           = "arm-angstrom-linux-gnueabi"
MACHINE              = "colibri-imx7-emmc"
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:656677f4a68e6747971a4a30550cd72c3beb6a76"
meta-freescale       = "HEAD:15f14f7eb30dde0488a04fbca6a2ac997eeace30"
meta-freescale-3rdparty = "HEAD:a02324e27f7a7ac630dab616f46a8bad7fe2c071"
meta-toradex-tegra   = "HEAD:15885b9b98aff0658f962f1c61352286b0749288"
meta-jetson-tk1      = "HEAD:e8b87fe8da7c6fcffa37ab245f50082953cc1ee1"
meta-toradex-bsp-common = "HEAD:3e713eef6e056c955b82adaf4b45286a98c3fcdf"
meta-oe              
meta-filesystems     
meta-gnome           
meta-xfce            
meta-initramfs       
meta-networking      
meta-multimedia      
meta-python          = "HEAD:352531015014d1957d6444d114f4451e241c4d23"
meta-lxde            = "HEAD:8b0f254b6afa8df1daa240905ffbafd7c794c0ef"
meta-browser         = "HEAD:1cd38d701a49eade80a04140f70d3383117b9745"
meta-qt4             = "HEAD:e290738759ef3f39c9e079eaa9b606a62107e5ba"
meta-qt5             = "HEAD:682ad61c071a9710e9f9d8a32ab1b5f3c14953d1"
meta-qt5-extra       = "HEAD:79e26686520f2ce5f743975e90116b263a33697f"
meta-freescale-distro = "HEAD:51756d1c2058139c8a21f89b86cfd8007b71b7f0"
meta-toradex-demos   = "HEAD:32e07d09ac0279d0c50b6801e26e6d0be776207c"
meta                 = "HEAD:6c20c550a82aed9e8fa312f09888c8f16250159c"

plus my own layer which I’m pulling a few packages from via IMAGE_INSTALL_append in local.conf.

Any ideas what may be causing this?

7

hi @hordur

Welcome to the Toradex Community!!!

Could you please ask a new question, please with all the details to reproduce the issue?

Thanks and best regards
Jaski

8

I’ve run into the same problem. In my case I found that it was related to a recipe extending the “TOOLCHAIN_HOST_TASK”.

This variable MUST be extended using “_append” and not “+=”. Using “+=” results in the error above.

Broken:

TOOLCHAIN_HOST_TASK += " nativesdk-protobuf-compiler "

Works:

TOOLCHAIN_HOST_TASK_append = " nativesdk-protobuf-compiler "
9

hi @spencemt

Thanks for this Input. Best regards.