Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Sourabh Hegde <hrsourabh011@gmail.com>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] Error while building tpm2-tools package with fapi support
Date: Mon, 22 May 2023 16:16:42 +0200	[thread overview]
Message-ID: <20230522161642.510747dc@windsurf> (raw)
In-Reply-To: <CADYjeSs9N0nKpwFYp9YioQfBUGnbRim5PQNVqSZLFjnXZPMDLQ@mail.gmail.com>

Hello,

On Sat, 20 May 2023 23:34:48 +0200
Sourabh Hegde <hrsourabh011@gmail.com> wrote:

> Yes, you are right.
> But, I did make "tpm2-tools-dirclean && make tpm2-tools-rebuild" and this
> didn't help.
> Also, I tried "make tpm2-tools-dirclean all" and "make tpm2-tools-dircclean
> && make tpm2-tools-reconfigure". This also resulted in the same error.

It's tpm2-tss that you need to rebuild. When you enable
BR2_PACKAGE_TPM2_TOOLS_FAPI, it selects BR2_PACKAGE_TPM2_TSS_FAPI. But
the thing is that tpm2-tss has already been built with
BR2_PACKAGE_TPM2_TSS_FAPI disabled. Buildroot does not have the logic
to automatically realize this. So either you do a full rebuild ("make
clean all"), or you understand that you have to explicitly tell
Buildroot that tpm2-tss needs to be rebuilt.

So, essentially here:

$ make tpm2-tss-dirclean tpm2-tools-dirclean
$ make

Best regards,

Thomas
-- 
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

  reply	other threads:[~2023-05-22 14:16 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-19 10:59 [Buildroot] Error while building tpm2-tools package with fapi support Sourabh Hegde
2023-05-20 19:24 ` Thomas Petazzoni via buildroot
2023-05-20 21:34   ` Sourabh Hegde
2023-05-22 14:16     ` Thomas Petazzoni via buildroot [this message]
2023-06-13 21:21       ` Sourabh Hegde

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=20230522161642.510747dc@windsurf \
    --to=buildroot@buildroot.org \
    --cc=hrsourabh011@gmail.com \
    --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