All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2 1/1] tpm-tools: bump to version 1.3.9.1
Date: Tue, 19 Dec 2017 15:44:18 +0100	[thread overview]
Message-ID: <20171219154418.24a00bc9@windsurf> (raw)
In-Reply-To: <alpine.DEB.2.20.1712191514250.3246@localhost>

Hello,

On Tue, 19 Dec 2017 16:20:08 +0200 (IST), Yair Ben Avraham wrote:

> In commit 4ef0ef3 "tpm-tools: new package", the pkcs11 support explicitly 
> disabled due to "... it is not handled by tpm-tools.mk currently."
> 
> The building of src/data_mgmt commands, which enable the pkcs11 support 
> (see ./configure file), depends on the P11_SUPPORT flag (see 
> src/Makefile.am) which in turn depends on opencryptoki/pkcs11.h header 
> (see ./configure.ac file).
> 
> So the reason that pkcs11 is not supported it's not because that 
> tpm-tools.mk not handle it, but because of the lack of 
> opencryptoki/pkcs11.h header.

And so?

The reason why tpm-tools.mk explicitly disables it is because we
generally try to explicitly disable features that are not handled by
Buildroot. I.e if package A needs package B to enable a given feature,
then Buildroot passes --disable-B in order to be sure that the
configure script will not mistakenly enable it (some configure scripts
are for example confused by host-installed libraries and headers).

So, I'm sorry, but your explanation doesn't make much sense to me. So
either I still don't understand what you mean, or you did not
understand why --disable-pkcs11-support was originally added.

If nothing provides opencryptoki/pkcs11.h, then this option should
continue to be explicitly disabled.

Best regards,

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com

      reply	other threads:[~2017-12-19 14:44 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-19 10:34 [Buildroot] [PATCH v2 1/1] tpm-tools: bump to version 1.3.9.1 Yair Ben Avraham
2017-12-19 12:45 ` Thomas Petazzoni
2017-12-19 14:20   ` Yair Ben Avraham
2017-12-19 14:44     ` Thomas Petazzoni [this message]

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=20171219154418.24a00bc9@windsurf \
    --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 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.