TPM2 (Trusted Platform Module) userspace development
 help / color / mirror / Atom feed
From: Trevor Woerner <twoerner at gmail.com>
To: tpm2@lists.01.org
Subject: Re: [tpm2] OE recipe for tpm2-tss works with 1.4.0 but not 2.0.0
Date: Thu, 12 Jul 2018 20:34:09 -0400	[thread overview]
Message-ID: <20180713003409.GA16423@linux-uys3> (raw)
In-Reply-To: 73e5e9a53c6f43089d7b50b46024bca9@AZDC-MMB02.GD-MS.US

[-- Attachment #1: Type: text/plain, Size: 1015 bytes --]

Hi Peter,

On Thu 2018-07-12 @ 06:25:52 PM, Scheie, Peter M wrote:
> I'm trying to get the tpm2-tss package in our WindRiver 8 build system
> (bitbake) upgraded from 1.4.0 to 2.0.0. I'm using the tpm2-tss recipe from
> OpenEmbedded which I think was originally written for 1.x (1.3?) and it's
> been working fine with the tpm2-tss_1.4.0.tar.gz file.

Do you know which layers, and which branches of these layers, you're using in
your build? Neither OpenEmbedded core itself nor meta-openembedded include any
TPM2 recipes, they are provided by other, added-on layers. There are at least
3 different layers of which I'm aware that provide the TPM2 recipes:

	meta-secure-core: https://github.com/jiazhang0/meta-secure-core.git
	meta-security:    https://git.yoctoproject.org/cgit/cgit.cgi/meta-security
	meta-measured:    https://github.com/flihp/meta-measured

If you could provide the "Build Configuration:" (that is printed at the start
of every build) for your specific build, that might help.

             reply	other threads:[~2018-07-13  0:34 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-13  0:34 Trevor Woerner [this message]
  -- strict thread matches above, loose matches on Subject: below --
2018-07-16 16:38 [tpm2] OE recipe for tpm2-tss works with 1.4.0 but not 2.0.0 Scheie, Peter M
2018-07-13  0:47 Trevor Woerner
2018-07-12 21:33 Scheie, Peter M
2018-07-12 18:25 Scheie, Peter M

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=20180713003409.GA16423@linux-uys3 \
    --to=tpm2@lists.01.org \
    /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