From: Manu Bretelle <chantra@meta.com>
To: Jakub Kicinski <kuba@kernel.org>
Cc: Daniel Borkmann <daniel@iogearbox.net>,
"davem@davemloft.net" <davem@davemloft.net>,
"pabeni@redhat.com" <pabeni@redhat.com>,
"edumazet@google.com" <edumazet@google.com>,
Alexei Starovoitov <ast@kernel.org>,
Andrii Nakryiko <andrii@kernel.org>,
Martin KaFai Lau <martin.lau@linux.dev>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"bpf@vger.kernel.org" <bpf@vger.kernel.org>
Subject: Re: pull-request: bpf 2024-07-25
Date: Thu, 25 Jul 2024 19:47:04 +0000 [thread overview]
Message-ID: <804E813B-9F16-486F-9E92-EB8B3F84C5CB@meta.com> (raw)
In-Reply-To: <20240725114040.26c1f483@kernel.org>
> On Jul 25, 2024, at 11:40 AM, Jakub Kicinski <kuba@kernel.org> wrote:
>
>
>
> On the LLVM19 I see this in all outputs:
> ar: libLLVM.so.19.0: cannot open shared object file: No such file or directory
>
> But presumably that's harmless, then.
Oh I see. It seems this is only affecting gcc builds.
Seem that nm/ar are not affected:
# ldd /usr/bin/ar /usr/bin/nm
/usr/bin/ar:
linux-vdso.so.1 (0x00007fffa7376000)
libbfd-2.34-system.so => /lib/x86_64-linux-gnu/libbfd-2.34-system.so (0x00007f6e90609000)
libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007f6e90417000)
libz.so.1 => /lib/x86_64-linux-gnu/libz.so.1 (0x00007f6e903fb000)
libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x00007f6e903f5000)
/lib64/ld-linux-x86-64.so.2 (0x00007f6e9076e000)
/usr/bin/nm:
linux-vdso.so.1 (0x00007ffd817ad000)
libbfd-2.34-system.so => /lib/x86_64-linux-gnu/libbfd-2.34-system.so (0x00007f09dc4ab000)
libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007f09dc2b9000)
libz.so.1 => /lib/x86_64-linux-gnu/libz.so.1 (0x00007f09dc29d000)
libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x00007f09dc297000)
/lib64/ld-linux-x86-64.so.2 (0x00007f09dc60c000)
but the “llvm” versions are:
# ldd /usr/bin/llvm-ar /usr/bin/llvm-nm
/usr/bin/llvm-ar:
linux-vdso.so.1 (0x00007ffd675b2000)
libLLVM.so.19.0 => not found
libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 (0x00007fe0ba21d000)
libstdc++.so.6 => /lib/x86_64-linux-gnu/libstdc++.so.6 (0x00007fe0ba03b000)
libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x00007fe0b9eec000)
libgcc_s.so.1 => /lib/x86_64-linux-gnu/libgcc_s.so.1 (0x00007fe0b9ed1000)
libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007fe0b9cdf000)
/lib64/ld-linux-x86-64.so.2 (0x00007fe0ba260000)
/usr/bin/llvm-nm:
linux-vdso.so.1 (0x00007ffecd6ea000)
libLLVM.so.19.0 => not found
libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 (0x00007ffadeb05000)
libstdc++.so.6 => /lib/x86_64-linux-gnu/libstdc++.so.6 (0x00007ffade923000)
libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x00007ffade7d4000)
libgcc_s.so.1 => /lib/x86_64-linux-gnu/libgcc_s.so.1 (0x00007ffade7b9000)
libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007ffade5c7000)
/lib64/ld-linux-x86-64.so.2 (0x00007ffadeb5a000)
Seems the llvm package rom llvm repo shadows the one from the repo, installing libllvm19 as a side effect but not updating the ld conf path .
# dpkg -l | grep llvm
ii libllvm19:amd64 1:19~++20240722052718+f2eb7c7344a5-1~exp1~20240722172839.1099 amd64 Modular compiler and toolchain technologies, runtime library
ii llvm 1:19.0-58~exp2+0~20240303102334.17~1.gbp3b61b3 amd64 Low-Level Virtual Machine (LLVM)
ii llvm-19 1:19~++20240722052718+f2eb7c7344a5-1~exp1~20240722172839.1099 amd64 Modular compiler and toolchain technologies
ii llvm-19-dev 1:19~++20240722052718+f2eb7c7344a5-1~exp1~20240722172839.1099 amd64 Modular compiler and toolchain technologies, libraries and headers
ii llvm-19-linker-tools 1:19~++20240722052718+f2eb7c7344a5-1~exp1~20240722172839.1099 amd64 Modular compiler and toolchain technologies - Plugins
ii llvm-19-runtime 1:19~++20240722052718+f2eb7c7344a5-1~exp1~20240722172839.1099 amd64 Modular compiler and toolchain technologies, IR interpreter
ii llvm-19-tools 1:19~++20240722052718+f2eb7c7344a5-1~exp1~20240722172839.1099 amd64 Modular compiler and toolchain technologies, tools
ii llvm-runtime:amd64 1:19.0-58~exp2+0~20240303102334.17~1.gbp3b61b3 amd64 Low-Level Virtual Machine (LLVM), bytecode interpreter
Seems everything works so far. Going to cross fingers that it holds.
Manu
next prev parent reply other threads:[~2024-07-25 19:47 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-25 11:43 pull-request: bpf 2024-07-25 Daniel Borkmann
2024-07-25 13:30 ` Jakub Kicinski
2024-07-25 14:13 ` Daniel Borkmann
2024-07-25 14:16 ` Jakub Kicinski
2024-07-25 18:30 ` Manu Bretelle
2024-07-25 18:40 ` Jakub Kicinski
2024-07-25 19:47 ` Manu Bretelle [this message]
2024-07-25 14:50 ` patchwork-bot+netdevbpf
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=804E813B-9F16-486F-9E92-EB8B3F84C5CB@meta.com \
--to=chantra@meta.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=martin.lau@linux.dev \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.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