From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] Interesting circular dependency, how to solve?
Date: Wed, 6 Jul 2016 20:20:05 +0200 [thread overview]
Message-ID: <20160706202005.6e2ac6c3@free-electrons.com> (raw)
In-Reply-To: <F9C551623D2CBB4C9488801D14F864C6EE83C112@ex-mb1.corp.adtran.com>
Hello,
On Wed, 6 Jul 2016 17:54:01 +0000, ANDY KENNEDY wrote:
> > - When cryptodev-linux is enabled, OpenSSL will depend on it to use
> > crypto accelerators supported in the kernel via cryptodev-linux.
>
> If I understand you correctly, this builds TWO things, right?
>
> If this is the case, make it separate packages to build the
> kernel module then the userspace package.
It builds a kernel module, so it has to depend on "linux", and it
installs cryptodev.h, which OpenSSL needs. I am not sure splitting this
package into two is really a good idea, though it would indeed solve
the problem: all what OpenSSL needs at build time is the cryptodev.h
header file. The kernel module can be built separately, and is only at
runtime.
So, yes, one possibility is to break cryptodev-linux into two packages.
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2016-07-06 18:20 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-06 15:56 [Buildroot] Interesting circular dependency, how to solve? Thomas Petazzoni
2016-07-06 17:54 ` ANDY KENNEDY
2016-07-06 18:20 ` Thomas Petazzoni [this message]
2016-07-06 19:25 ` ANDY KENNEDY
2016-07-07 17:00 ` Yann E. MORIN
2016-07-07 19:26 ` Thomas Petazzoni
2016-07-07 23:25 ` Yann E. MORIN
2016-07-07 16:33 ` Yann E. MORIN
2016-07-07 17:33 ` Yann E. MORIN
2016-07-07 19:31 ` Thomas Petazzoni
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=20160706202005.6e2ac6c3@free-electrons.com \
--to=thomas.petazzoni@free-electrons.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox