From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/2] package/tpm2-tss: add upstream patch to drop hardcoded -lgcrypt from tss2-esys.pc
Date: Sun, 14 Apr 2019 23:21:09 +0200 [thread overview]
Message-ID: <87v9zgfflm.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <20190408115648.11004-1-peter@korsgaard.com> (Peter Korsgaard's message of "Mon, 8 Apr 2019 13:56:46 +0200")
>>>>> "Peter" == Peter Korsgaard <peter@korsgaard.com> writes:
> tss2-esys.pc contains a hardcoded -lgcrypt even though the openssl crypto
> backend (as in Buildroot) may be used, leading to linker errors when using
> esys.
> Given that tpm2-tss doesn't allow static linking, there is no need to
> explicitly list the crypto library dependency.
> Cherry pick an upstream patch to fix this. Notice that the upstream patch
> also changes the default crypto backend to openssl. As this isn't stricly
> needed (we explicitly configure for openssl) and requires autoreconv, drop
> the configure.ac hunk from the patch.
> https://github.com/tpm2-software/tpm2-tss/pull/1173
> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
Committed to 2019.02.x, thanks.
--
Bye, Peter Korsgaard
prev parent reply other threads:[~2019-04-14 21:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-08 11:56 [Buildroot] [PATCH 1/2] package/tpm2-tss: add upstream patch to drop hardcoded -lgcrypt from tss2-esys.pc Peter Korsgaard
2019-04-08 11:56 ` [Buildroot] [PATCH 2/2] package/tpm2-totp: new package Peter Korsgaard
2019-04-08 20:52 ` [Buildroot] [PATCH 1/2] package/tpm2-tss: add upstream patch to drop hardcoded -lgcrypt from tss2-esys.pc Thomas Petazzoni
2019-04-14 21:21 ` Peter Korsgaard [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=87v9zgfflm.fsf@dell.be.48ers.dk \
--to=peter@korsgaard.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.