Hello,

I am building Yocto using Atmel BSP, Poky and OE version: Morty.
The eSDK installer builds fine (bitbake -c populate_sdk_ext 
core-image-minimal). Build machine x86_64, Ubuntu 16.04 LTS
If I install the eSDK in the same machine where it was build, it works fine.
However, when I try to install the eSDK in a different machine (x86_64, Ubuntu 
14.04) I get these errors:

Proceed[Y/n]?
Extracting SDK...................................................done
Setting it up...
Extracting buildtools...
Preparing build system...
Parsing recipes: 100% 
|########################################################| Time: 0:00:51
Initialising tasks: 100% 
|#####################################################| Time: 0:00:03
ERROR: Sstate artifact unavailable for 
gettext-minimal-native.do_populate_sysrootETA:  0:00:00
ERROR: Sstate artifact unavailable for quilt-native.do_populate_sysroot        
| ETA:  0:00:00
ERROR: Sstate artifact unavailable for 
u-boot-mkimage-native.do_populate_sysroot ETA:  0:00:00
ERROR: Sstate artifact unavailable for 
libxml-parser-perl-native.do_populate_sysroot:  0:00:00
ERROR: Sstate artifact unavailable for file-native.do_populate_sysroot         
| ETA:  0:00:00

I don't see this behavior if I use Poky Morty, commit: 
6da3e0a0abf1251db243548639979f8d74e99766
I see this behavior with Poky Morty commit: 
759a8085afee51abbe36b0bbfe5bf845f41e0971

Is the install suppose to fail due the lower OS version? I searched in the bug 
tracker, but didn't find anything related to this.
NOTE: I tried the other way: build eSDK in Ubuntu 14.04 and install eSDK in 
Ubuntu 16.04. This works fine.

Thanks,
Carlos




________________________________
The information contained in this message may be confidential and legally 
protected under applicable law. The message is intended solely for the 
addressee(s). If you are not the intended recipient, you are hereby notified 
that any use, forwarding, dissemination, or reproduction of this message is 
strictly prohibited and may be unlawful. If you are not the intended recipient, 
please contact the sender by return e-mail and destroy all copies of the 
original message.
-- 
_______________________________________________
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto

Reply via email to