From: Tadeusz Struk <tadeusz.struk at intel.com>
To: tpm2@lists.01.org
Subject: Re: [tpm2] How to generate the statically linked executable
Date: Thu, 26 Sep 2019 09:44:33 -0700 [thread overview]
Message-ID: <6901331d-e7cf-6922-381d-787a7fd83358@intel.com> (raw)
In-Reply-To: CAAG8Em3Y1OajU5gDiYZSn6vnVs=WLPCHX0naNyeuEj7LSqpPOw@mail.gmail.com
[-- Attachment #1: Type: text/plain, Size: 859 bytes --]
On 9/25/19 6:40 PM, ZhengYu Tsai wrote:
> /usr/local/lib/libtss2-esys.a(src_tss2_esys_libtss2_esys_la-tctildr-dl.o): In function `handle_from_name':
> /home/derek/workdir/tpm2-tss/src/tss2-tcti/tctildr-dl.c:84: warning: Using 'dlopen' in statically linked applications requires at runtime the shared libraries from the glibc version used for linking
> /usr/bin/ld: attempted static link of dynamic object `/usr/lib/i386-linux-gnu/libcurl-gnutls.so'
> collect2: error: ld returned 1 exit status
> Makefile:2170: recipe for target 'tools/tpm2_getekcertificate' failed
> make: *** [tools/tpm2_getekcertificate] Error 1
>
> I also found the tpm2-tss configure *--enable-shared=no,*
> This option is necessary, it will affect the compilation tpm2-tools.
Right, you also need to use --enable_nodl configure option when you build tss.
--
Tadeusz
next reply other threads:[~2019-09-26 16:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-26 16:44 Tadeusz Struk [this message]
-- strict thread matches above, loose matches on Subject: below --
2019-09-27 1:16 [tpm2] How to generate the statically linked executable ZhengYu Tsai
2019-09-27 1:10 ZhengYu Tsai
2019-09-26 1:40 ZhengYu Tsai
2019-09-25 20:55 Tadeusz Struk
2019-09-24 8:50 ZhengYu Tsai
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=6901331d-e7cf-6922-381d-787a7fd83358@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox