From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 9316] New: U-boot fails to build if libssl-dev is not installed
Date: Wed, 28 Sep 2016 15:44:51 +0000 [thread overview]
Message-ID: <bug-9316-163@https.bugs.busybox.net/> (raw)
https://bugs.busybox.net/show_bug.cgi?id=9316
Bug ID: 9316
Summary: U-boot fails to build if libssl-dev is not installed
Product: buildroot
Version: unspecified
Hardware: All
OS: Linux
Status: NEW
Severity: normal
Priority: P5
Component: Other
Assignee: unassigned at buildroot.uclibc.org
Reporter: matt.kraai at abbott.com
CC: buildroot at uclibc.org
Target Milestone: ---
When I run "make zynq_zed_defconfig && make" on my Ubuntu 16.04.1 LTS system,
the build fails with the following error messages:
> >>> uboot xilinx-v2016.2 Building
...
> HOSTCC tools/aisimage.o
> In file included from tools/aisimage.c:10:0:
> include/image.h:923:27: fatal error: openssl/evp.h: No such file or directory
> compilation terminated.
> scripts/Makefile.host:108: recipe for target 'tools/aisimage.o' failed
> make[3]: *** [tools/aisimage.o] Error 1
> Makefile:1211: recipe for target 'tools' failed
> make[2]: *** [tools] Error 2
> package/pkg-generic.mk:201: recipe for target '/home/kraai/src/buildroot/output> /build/uboot-xilinx-v2016.2/.stamp_built' failed
> make[1]: *** [/home/kraai/src/buildroot/output/build/uboot-xilinx-v2016.2> /.stamp_built] Error 2
> Makefile:41: recipe for target '_all' failed
> make: *** [_all] Error 2
Installing ssl-dev fixes this problem, but I think U-Boot should depend on
host-openssl in this case.
--
You are receiving this mail because:
You are on the CC list for the bug.
next reply other threads:[~2016-09-28 15:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-28 15:44 bugzilla at busybox.net [this message]
2016-10-20 21:31 ` [Buildroot] [Bug 9316] U-boot fails to build if libssl-dev is not installed bugzilla at busybox.net
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-9316-163@https.bugs.busybox.net/ \
--to=bugzilla@busybox.net \
--cc=buildroot@busybox.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.