From: Quentin Monnet <qmo@kernel.org>
To: Andrii Nakryiko <andrii.nakryiko@gmail.com>
Cc: Mykyta Yatsenko <mykyta.yatsenko5@gmail.com>,
bpf@vger.kernel.org, ast@kernel.org, andrii@kernel.org,
daniel@iogearbox.net, kafai@meta.com, kernel-team@meta.com,
Mykyta Yatsenko <yatsenko@meta.com>
Subject: Re: [PATCH bpf-next v2] bpftool: Allow explicitly skip llvm dependency
Date: Wed, 4 Feb 2026 14:24:06 +0000 [thread overview]
Message-ID: <26fe285f-2504-4ee8-8889-1451bcd64c9b@kernel.org> (raw)
In-Reply-To: <CAEf4BzZ2cxBfCBsTHDPHRqtbWmmN8ksYCOA_ScNiyAcTHdfZTw@mail.gmail.com>
2026-02-03 17:17 UTC-0800 ~ Andrii Nakryiko <andrii.nakryiko@gmail.com>
>> But if really you want to do this, at least let's do it fully and give
>> more control for the disassembler dependencies: I think it shouldn't be
>> just LLVM in this case, there should be a way to opt-out from libbfd as
>> well, which was problematic for other reasons in the first place, and
>> probably some mechanism to tell whether to use libbfd or LLVM for the
>> disassembler when the two are available on the machine.
>
> Yeah, absolutely, that makes sense. Mykyta, do you mind looking in
> what's the most sensible way to do what Quentin asks? Should we just
> have NO_LLVM and NO_BFD switches and take them both into account. If
> LLVM or BFD is not explicitly opted-out-from then we'll just prefere
> LLVM over BFD?
I'd be OK with that
Quentin
prev parent reply other threads:[~2026-02-04 14:24 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-28 23:34 [PATCH bpf-next v2] bpftool: Allow explicitly skip llvm dependency Mykyta Yatsenko
2026-01-29 17:34 ` Quentin Monnet
2026-01-29 17:50 ` Mykyta Yatsenko
2026-01-30 20:46 ` Andrii Nakryiko
2026-01-30 23:48 ` Quentin Monnet
2026-02-04 1:17 ` Andrii Nakryiko
2026-02-04 14:24 ` Quentin Monnet [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=26fe285f-2504-4ee8-8889-1451bcd64c9b@kernel.org \
--to=qmo@kernel.org \
--cc=andrii.nakryiko@gmail.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=kafai@meta.com \
--cc=kernel-team@meta.com \
--cc=mykyta.yatsenko5@gmail.com \
--cc=yatsenko@meta.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