From: David Van Arnem <dvanarnem@cmlab.biz>
To: buildroot@busybox.net
Subject: [Buildroot] Using openssl functions in another package
Date: Fri, 20 Nov 2015 12:35:34 -0700 [thread overview]
Message-ID: <564F7606.4020309@cmlab.biz> (raw)
Hi all,
I have a custom package (source in C) that uses some of OpenSSL's SHA
functions to perform hashing. I can build successfully outside of the
buildroot tree by both including the SHA header file in the C source with:
#include <openssl/sha.h>
and then adding the crypto library in the CC command:
$(CC) -lcrypto -o prog prog.c
However, when I try to build the package in buildroot, using the same CC
command in the Makefile, I get the following error:
prog.c: fatal error: openssl/sha.h: No such file or directory
I have enabled the openssl package in my buildroot configuration, and
set up my custom package's Config.in to depend on it:
depends on BR2_PACKAGE_OPENSSL
My target is a MicroBlaze (little endian, single core) processor. What
else might I need to do to use the OpenSSL SHA functions correctly and
avoid this error?
--
Thanks,
David
next reply other threads:[~2015-11-20 19:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-20 19:35 David Van Arnem [this message]
2015-11-20 22:06 ` [Buildroot] Using openssl functions in another package Arnout Vandecappelle
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=564F7606.4020309@cmlab.biz \
--to=dvanarnem@cmlab.biz \
--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.