# Yocto dey-image-aws build failing :(

**URL:** <https://forums.digi.com/t/yocto-dey-image-aws-build-failing/19736>\
**Category:** Linux\
**Tags:** greengrass, yocto\
**Created:** [July 24, 2018, 10:27am UTC](https://forums.digi.com/t/yocto-dey-image-aws-build-failing/19736 "2018-07-24T10:27:24Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![emakuh](https://avatars.discourse-cdn.com/v4/letter/e/ed655f/32.png) [@emakuh](https://forums.digi.com/u/emakuh)\
**Post date:** [July 24, 2018, 10:27am UTC](https://forums.digi.com/t/yocto-dey-image-aws-build-failing/19736/1 "2018-07-24T10:27:24Z")

</div>

I’m trying to build the dey-image-aws provided by Digi for the ConnectCore CC-WMX6UL Starter dev kit and am running into failures during the do\_rootfs stage of the build.

Here is the build output:

NOTE: Started PRServer with DBfile: /home/ubuntu/workspace/ccimx6ulstarter/cache/prserv.sqlite3, IP: 127.0.0.1, PORT: 34546, PID: 9634  
Loading cache: 100% |#################################################################################################################################################| Time: 0:00:00  
Loaded 3019 entries from dependency cache.  
Parsing recipes: 100% |###############################################################################################################################################| Time: 0:00:01  
Parsing of 2200 .bb files complete (2189 cached, 11 parsed). 3031 targets, 156 skipped, 0 masked, 0 errors.  
NOTE: There are 1 recipes to be removed from sysroot cortexa7hf-neon, removing…  
NOTE: There are 1 recipes to be removed from sysroot ccimx6ulstarter, removing…  
NOTE: Resolving any missing task queue dependencies

Build Configuration:  
BB\_VERSION = “1.36.0”  
BUILD\_SYS = “x86\_64-linux”  
NATIVELSBSTRING = “universal”  
TARGET\_SYS = “arm-dey-linux-gnueabi”  
MACHINE = “ccimx6ulstarter”  
DISTRO = “dey”  
DISTRO\_VERSION = “2.4-r1”  
TUNE\_FEATURES = “arm armv7ve vfp thumb neon callconvention-hard cortexa7”  
TARGET\_FPU = “hard”  
meta  
meta-poky  
meta-yocto-bsp = “HEAD:9589076fed41fe9c5749445e9210406fea362277”  
meta-oe  
meta-python  
meta-networking  
meta-webserver = “HEAD:352531015014d1957d6444d114f4451e241c4d23”  
meta-qt5 = “HEAD:682ad61c071a9710e9f9d8a32ab1b5f3c14953d1”  
meta-swupdate = “HEAD:6e4eab4f475b0129d6510815a3bbc4748c97dbbe”  
meta-freescale = “HEAD:a4158e3425a79720ddc4c02e76251d567bdceb51”  
meta-fsl-demos = “HEAD:51756d1c2058139c8a21f89b86cfd8007b71b7f0”  
meta-digi-arm  
meta-digi-dey = “HEAD:29add13409e8a0d8cc7f49276b060ae124b7bbe4”

Initialising tasks: 100% |############################################################################################################################################| Time: 0:00:04  
NOTE: Executing SetScene Tasks  
NOTE: Executing RunQueue Tasks  
ERROR: dey-image-aws-1.0-r0 do\_rootfs: Could not invoke dnf. Command ‘/home/ubuntu/workspace/ccimx6ulstarter/tmp/work/ccimx6ulstarter-dey-linux-gnueabi/dey-image-aws/1.0-r0/recipe-sysroot-native/usr/bin/dnf -y -c /home/ubuntu/workspace/ccimx6ulstarter/tmp/work/ccimx6ulstarter-dey-linux-gnueabi/dey-image-aws/1.0-r0/rootfs/etc/dnf/dnf.conf --setopt=reposdir=/home/ubuntu/workspace/ccimx6ulstarter/tmp/work/ccimx6ulstarter-dey-linux-gnueabi/dey-image-aws/1.0-r0/rootfs/etc/yum.repos.d --repofrompath=oe-repo,/home/ubuntu/workspace/ccimx6ulstarter/tmp/work/ccimx6ulstarter-dey-linux-gnueabi/dey-image-aws/1.0-r0/oe-rootfs-repo --installroot=/home/ubuntu/workspace/ccimx6ulstarter/tmp/work/ccimx6ulstarter-dey-linux-gnueabi/dey-image-aws/1.0-r0/rootfs --setopt=logdir=/home/ubuntu/workspace/ccimx6ulstarter/tmp/work/ccimx6ulstarter-dey-linux-gnueabi/dey-image-aws/1.0-r0/temp -x udev-cache --nogpgcheck install packagegroup-dey-wireless dnf packagegroup-dey-bluetooth packagegroup-dey-network run-postinsts greengrass rpm packagegroup-core-ssh-dropbear packagegroup-dey-core’ returned 1:  
Added oe-repo repo from /home/ubuntu/workspace/ccimx6ulstarter/tmp/work/ccimx6ulstarter-dey-linux-gnueabi/dey-image-aws/1.0-r0/oe-rootfs-repo  
Last metadata expiration check: 0:00:00 ago on Fri 20 Jul 2018 05:05:51 PM UTC.  
Error:  
Problem: conflicting requests

- nothing provides libcrypto.so.1.0.0 needed by greengrass-1.5.0-r0.1.cortexa7hf\_neon

ERROR: dey-image-aws-1.0-r0 do\_rootfs: Function failed: do\_rootfs  
ERROR: Logfile of failure stored in: /home/ubuntu/workspace/ccimx6ulstarter/tmp/work/ccimx6ulstarter-dey-linux-gnueabi/dey-image-aws/1.0-r0/temp/log.do\_rootfs.9814  
ERROR: Task (/usr/local/dey-2.4/sources/meta-digi/meta-digi-dey/recipes-core/images/dey-image-aws.bb:do\_rootfs) failed with exit code ‘1’  
NOTE: Tasks Summary: Attempted 3845 tasks of which 3841 didn’t need to be rerun and 1 failed.

Summary: 1 task failed:  
/usr/local/dey-2.4/sources/meta-digi/meta-digi-dey/recipes-core/images/dey-image-aws.bb:do\_rootfs  
Summary: There were 2 ERROR messages shown, returning a non-zero exit code.

I did a find tmp/deploy -name \*libcrypto\* which shows that the library does exist in the deploy directory: tmp/deploy/rpm/cortexa7hf\_neon/libcrypto1.0.2-1.0.2o-r0.0.cortexa7hf\_neon.rpm

I am having a hard time tracking down what recipe is actually requiring libcrypto…from what I can tell the greengrass recipe doesn’t list libcrypto as an RDEPENDS so I’m assuming it is something that it is inheriting the dependency, I just haven’t figured out how to determine the recipe that is actually requiring that library…I’d love some insight into determining that.

Here is a link to the Greengrass recipe that I’m using: [https://paste.ofcode.org/rqwqxWHiNdeZ7JBjEtNepV](https://paste.ofcode.org/rqwqxWHiNdeZ7JBjEtNepV)

Here are a few of my questions…1) what are some first steps in figuring how what recipe depends on libcrypto? 2) How do I figured out what recipe is providing the libcrypto in the tmp/deploy directory, and why isn’t bitbake able to use that to satisfy the libcrypto dependency?

---

<div class="post-metadata">

**Author:** ![Oliver\_K](https://avatars.discourse-cdn.com/v4/letter/o/e95f7d/32.png) [@Oliver\_K](https://forums.digi.com/u/Oliver_K)\
**Post date:** [May 14, 2019, 3:34pm UTC](https://forums.digi.com/t/yocto-dey-image-aws-build-failing/19736/2 "2019-05-14T15:34:15Z")

</div>

I had the same problem and in the first step I simply removed the AWS part in the related bb file (dey-x.x/sources/meta-digi/meta-digi-dey/recipes-core/images/dey-image-aws.bb).
