I've just remembered running into this problem some time back and situation sounded familiar... Yes you are right, we should check for one of the 2.0-only symbols, and I thought we were. We should double-check that in configure.ac. If only gcrypt had a pkg-config file. ________________________________ From: Tricca, Philip B [philip.b.tricca(a)intel.com] Sent: Thursday, October 18, 2018 23:26 To: Fuchs, Andreas Cc: Terry An; tpm2(a)lists.01.org Subject: RE: [tpm2] does anyone compile tpm2-tss-2.1.0 successful on CentOS7? 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 ; 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 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..