I’m trying to run a TPM2.0 simulator on macOS Sonoma (14.2.1) using Official TPM 2.0 Reference Implementation (by Microsoft) and it seems to be failing at generating a make file for executing. This is what I get when I execute the following steps:

 $ export PKG_CONFIG_PATH="/usr/local/opt/openssl/lib/pkgconfig"

 $ ./bootstrap
 Generating file lists: src.mk
 Setting up build
 Setting default vendor strings

 $ PKG_CONFIG_PATH="/usr/local/opt/openssl/lib/pkgconfig" EXTRA_CFLAGS=-fno-common ./configure
 checking for gcc... gcc
 checking whether the C compiler works... yes
 checking for C compiler default output file name... a.out
 checking for suffix of executables... 
 checking whether we are cross compiling... no
 checking for suffix of object files... o
 checking whether the compiler supports GNU C... yes
 checking whether gcc accepts -g... yes
 checking for gcc option to enable C11 features... none needed
 checking whether gcc understands -c and -o together... yes
 checking whether ln -s works... yes
 checking for ranlib... ranlib
 checking for a BSD-compatible install... /usr/bin/install -c
 checking whether build environment is sane... yes
 checking for a race-free mkdir -p... mkdir -p
 checking for gawk... no
 checking for mawk... no
 checking for nawk... no
 checking for awk... awk
 checking whether make sets $(MAKE)... yes
 checking whether make supports the include directive... yes (GNU style)
 checking whether make supports nested variables... yes
 checking dependency style of gcc... gcc3
 ./configure: line 4303: syntax error near unexpected token `LIBCRYPTO,'
 ./configure: line 4303: `PKG_CHECK_MODULES(LIBCRYPTO, libcrypto)'

So when I try to do a make it ends up with a make: *** No targets specified and no makefile found. Stop. I think this could be because ./configure does not finish successfully. I tried to check for libcrypto in the openssl PATH linked during the export and I can find it there:

 $ cd /usr/local/opt/openssl/lib/pkgconfig
 $ ls
   libcrypto.pc libssl.pc   openssl.pc

I wanted to check if there are some configurations or PATH I might be missing to link libcrypto to openssl to fix the error.