All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tricca, Philip B <philip.b.tricca at intel.com>
To: tpm2@lists.01.org
Subject: Re: [tpm2] does anyone compile tpm2-tss-2.1.0 successful on CentOS7?
Date: Thu, 18 Oct 2018 21:26:01 +0000	[thread overview]
Message-ID: <DB638850A6A2434A93ECADDA0BC838909ACBE2E1@ORSMSX103.amr.corp.intel.com> (raw)
In-Reply-To: 9F48E1A823B03B4790B7E6E69430724D0147347A88@exch2010c.sit.fraunhofer.de

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

If we're not checking for these dependencies @ configure time then I'd call this a bug. The gcrypt handling stuff in the autoconf file is pretty convoluted but if I'm reading your last message correctly you're saying that it can't tell the difference between libgcrypt 1.2 & 2.0?

From: tpm2 [mailto:tpm2-bounces(a)lists.01.org] On Behalf Of Fuchs, Andreas
Sent: 18 October, 2018 03:35
To: Terry An <terry.an.bj(a)gmail.com>; tpm2(a)lists.01.org
Subject: Re: [tpm2] does anyone compile tpm2-tss-2.1.0 successful on CentOS7?

tpm2-tss requires libgcrypt20 (at least that's was it's called on Ubuntu).
libgcrypt (which is the 1.x branch) is quite old and had a different API than the 20 series...

Maybe that's the problem...
________________________________
From: tpm2 [tpm2-bounces(a)lists.01.org] on behalf of Terry An [terry.an.bj(a)gmail.com]
Sent: Thursday, October 18, 2018 12:18
To: tpm2(a)lists.01.org<mailto:tpm2(a)lists.01.org>
Subject: [tpm2] does anyone compile tpm2-tss-2.1.0 successful on CentOS7?
lots of errors on my laptop.

I have updated libgpg-error, libgcrypt-devel, etc..

[-- Attachment #2: attachment.html --]
[-- Type: text/html, Size: 5103 bytes --]

             reply	other threads:[~2018-10-18 21:26 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-18 21:26 Tricca, Philip B [this message]
  -- strict thread matches above, loose matches on Subject: below --
2018-10-23  9:37 [tpm2] does anyone compile tpm2-tss-2.1.0 successful on CentOS7? Luke Hinds
2018-10-18 21:51 Fuchs, Andreas
2018-10-18 11:07 Terry An
2018-10-18 10:35 Fuchs, Andreas
2018-10-18 10:18 Terry An

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=DB638850A6A2434A93ECADDA0BC838909ACBE2E1@ORSMSX103.amr.corp.intel.com \
    --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 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.