Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Dimi Tomov <dimi@tpm.dev>
To: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 1/1] package/wolftpm: new package
Date: Thu, 02 Jun 2022 08:01:22 +0300	[thread overview]
Message-ID: <855061e514da0fc44a740cb6687e42ce@tpm.dev> (raw)
In-Reply-To: <20220601233607.336a4072@windsurf>

Thank you Thomas. This is awesome.

Only FYI - I had no issues with wolfssl building from latest buildroot 
master. My only issue was with the config.rpath autoconf file while 
building wolftpm.

Best Regards,
Dimi

On 2022-06-02 12:36 AM, Thomas Petazzoni via buildroot wrote:
> Hello,
> 
> On Thu, 02 Jun 2022 00:03:39 +0300
> Dimi Tomov <dimi@tpm.dev> wrote:
> 
>> Hello Thomas,
>> 
>> I have this working on a STM32MP157F-DK2 board with a ST33 TPM.
>> 
>> https://gist.github.com/tomoveu/8f0519cb8d75a5374a999f29640cf45c
>> 
>> Could it be that because I am using $make wolftpm-rebuild is saving me
>> from seeing the same errors?
> 
> I am not sure why you don't have the error about wolfssl being
> unavailable. It was clearly failing to build here. I would need access
> to your complete build log + output/build/wolftpm-<version>/config.log
> to be able to (perhaps) say what's going on.
> 
>> ps: Do I need to submit v4?
> 
> No, I said the patch was applied. It's in our next branch, see:
> 
> 
> https://git.buildroot.org/buildroot/commit/?h=next&id=4bb884a3c61c6b71e33f69453a90eb2a367f64b7
> 
> Thanks!
> 
> Thomas

-- 
Founder of TPM.dev
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

      reply	other threads:[~2022-06-02  5:01 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-08 21:20 [Buildroot] [PATCH 1/1] package/wolftpm: new package, wolfTPM library for TPM2.0 Dimi Tomov
2022-05-17 19:05 ` Dimi Tomov
2022-05-30 20:30 ` [Buildroot] [PATCH 1/2] " Dimi Tomov
2022-05-30 20:30   ` [Buildroot] [PATCH 2/2] v2: Fix typo in the hash file and create path before using touch Dimi Tomov
2022-05-30 21:32     ` Thomas Petazzoni via buildroot
2022-05-30 21:31   ` [Buildroot] [PATCH 1/2] package/wolftpm: new package, wolfTPM library for TPM2.0 Thomas Petazzoni via buildroot
2022-06-01 19:47   ` [Buildroot] [PATCH 1/1] package/wolftpm: new package Dimi Tomov
2022-06-01 19:51     ` Dimi Tomov
2022-06-01 20:50     ` Thomas Petazzoni via buildroot
2022-06-01 21:03       ` Dimi Tomov
2022-06-01 21:36         ` Thomas Petazzoni via buildroot
2022-06-02  5:01           ` Dimi Tomov [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=855061e514da0fc44a740cb6687e42ce@tpm.dev \
    --to=dimi@tpm.dev \
    --cc=buildroot@buildroot.org \
    --cc=thomas.petazzoni@bootlin.com \
    /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