Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Yair Ben Avraham <yairba@tkos.co.il>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2 1/1] tpm-tools: bump to version 1.3.9.1
Date: Tue, 19 Dec 2017 16:20:08 +0200 (IST)	[thread overview]
Message-ID: <alpine.DEB.2.20.1712191514250.3246@localhost> (raw)
In-Reply-To: <20171219134547.70fae97f@windsurf>

Hi,

On Tue, 19 Dec 2017, Thomas Petazzoni wrote:
> On Tue, 19 Dec 2017 12:34:36 +0200, Yair Ben Avraham wrote:
>
>>  - Revert to pkcs11 support. Building src/data_mgmt directory depends on
>>    P11_SUPPORT which in turn depends on opencryptoki/pkcs11.h header and it's
>>    not a make issue
>
> I don't understand this part however. Could you explain a bit more ?
> What do you mean by "it's not a make issue" ?

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.

By "it's not a make issue" I mean "not handled by tpm-tools.mk".

Thanks,
Yair
--
Yair Ben-Avraham
Tk Open Systems Ltd.
052-343-2297
yairba at tkos.co.il

  reply	other threads:[~2017-12-19 14:20 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 [this message]
2017-12-19 14:44     ` 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=alpine.DEB.2.20.1712191514250.3246@localhost \
    --to=yairba@tkos.co.il \
    --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