From: Clark Williams <williams@redhat.com>
To: Tomas Glozar <tglozar@redhat.com>
Cc: Wander Lairson Costa <wander@redhat.com>,
linux-rt-users@vger.kernel.org,
Derek Barbosa <debarbos@redhat.com>,
John Kacur <jkacur@redhat.com>,
Juri Lelli <juri.lelli@redhat.com>,
Chunsheng Luo <luochunsheng@ustc.edu>
Subject: Re: [PATCH] Makefile: Make BPF compilation verbose
Date: Mon, 27 Oct 2025 11:28:48 -0500 [thread overview]
Message-ID: <aP-dwB-ziszcenTp@lysander> (raw)
In-Reply-To: <CAP4=nvTHb566uAjuVm_gvBO3t9r0=o2MAKR7dfh6ZWRp0dvDmw@mail.gmail.com>
On Mon, Oct 27, 2025 at 08:32:25AM +0100, Tomas Glozar wrote:
> pá 24. 10. 2025 v 19:22 odesílatel Wander Lairson Costa
> <wander@redhat.com> napsal:
> >
> > Remove the '@' prefix from the CLANG and LLVM_STRIP commands in the
> > Makefile. This makes the build system print the commands to the console
> > during the BPF compilation process. This increased verbosity is useful
> > for debugging build issues.
> >
>
> This makes sense, since the BPF program compilation can fail, in that
> case, it is not clear where the error is coming from:
>
I'm good with this change.
I would ask in the future if we could add 'stalld' to the subject line
text for easy filtering.
Clark
--
The United States Coast Guard
Ruining Natural Selection since 1790
next prev parent reply other threads:[~2025-10-27 16:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-24 17:21 [PATCH] Makefile: Make BPF compilation verbose Wander Lairson Costa
2025-10-27 7:32 ` Tomas Glozar
2025-10-27 16:28 ` Clark Williams [this message]
[not found] ` <CAMLffL-16SO1oue7o8Jhb+Cz-PTauAnNtFAjE=B9V8qpS+dY+g@mail.gmail.com>
2025-11-03 20:56 ` Wander Lairson Costa
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=aP-dwB-ziszcenTp@lysander \
--to=williams@redhat.com \
--cc=debarbos@redhat.com \
--cc=jkacur@redhat.com \
--cc=juri.lelli@redhat.com \
--cc=linux-rt-users@vger.kernel.org \
--cc=luochunsheng@ustc.edu \
--cc=tglozar@redhat.com \
--cc=wander@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