From: patchwork-bot+netdevbpf@kernel.org
To: Anton Protopopov <aspsk@isovalent.com>
Cc: bpf@vger.kernel.org, sdf@google.com, quentin@isovalent.com,
jean-philippe@linaro.org
Subject: Re: [PATCH bpf-next v2] bpftool: fix linkage with statically built libllvm
Date: Thu, 22 Dec 2022 19:20:16 +0000 [thread overview]
Message-ID: <167173681646.9636.4275856404037245286.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20221222102627.1643709-1-aspsk@isovalent.com>
Hello:
This patch was applied to bpf/bpf.git (master)
by Daniel Borkmann <daniel@iogearbox.net>:
On Thu, 22 Dec 2022 10:26:27 +0000 you wrote:
> Since the eb9d1acf634b commit ("bpftool: Add LLVM as default library for
> disassembling JIT-ed programs") we might link the bpftool program with the
> libllvm library. This works fine when a shared libllvm library is available,
> but fails if we want to link bpftool with a statically built LLVM:
>
> /usr/bin/ld: /usr/local/lib/libLLVMSupport.a(CrashRecoveryContext.cpp.o): in function `llvm::CrashRecoveryContextCleanup::~CrashRecoveryContextCleanup()':
> CrashRecoveryContext.cpp:(.text._ZN4llvm27CrashRecoveryContextCleanupD0Ev+0x17): undefined reference to `operator delete(void*, unsigned long)'
> /usr/bin/ld: /usr/local/lib/libLLVMSupport.a(CrashRecoveryContext.cpp.o): in function `llvm::CrashRecoveryContext::~CrashRecoveryContext()':
> CrashRecoveryContext.cpp:(.text._ZN4llvm20CrashRecoveryContextD2Ev+0xc8): undefined reference to `operator delete(void*, unsigned long)'
> ...
>
> [...]
Here is the summary with links:
- [bpf-next,v2] bpftool: fix linkage with statically built libllvm
https://git.kernel.org/bpf/bpf/c/55171f2930be
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2022-12-22 19:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-22 10:26 [PATCH bpf-next v2] bpftool: fix linkage with statically built libllvm Anton Protopopov
2022-12-22 17:06 ` sdf
2022-12-22 19:20 ` patchwork-bot+netdevbpf [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=167173681646.9636.4275856404037245286.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=aspsk@isovalent.com \
--cc=bpf@vger.kernel.org \
--cc=jean-philippe@linaro.org \
--cc=quentin@isovalent.com \
--cc=sdf@google.com \
/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