From: Eduard Zingerman <eddyz87@gmail.com>
To: bpf@vger.kernel.org, ast@kernel.org
Cc: andrii@kernel.org, daniel@iogearbox.net, martin.lau@linux.dev,
kernel-team@fb.com, yonghong.song@linux.dev
Subject: Re: [PATCH bpf-next] selftests/bpf: use simply-expanded variables for libpcap flags
Date: Fri, 23 Aug 2024 12:49:57 -0700 [thread overview]
Message-ID: <ca9ffdd75b8e5457264b6ddd567296a0f17dcf31.camel@gmail.com> (raw)
In-Reply-To: <20240823194409.774815-1-eddyz87@gmail.com>
On Fri, 2024-08-23 at 12:44 -0700, Eduard Zingerman wrote:
> Save pkg-config output for libpcap as simply-expanded variables.
> For an obscure reason 'shell' call in LDLIBS/CFLAGS recursively
> expanded variables makes *.test.o files compilation non-parallel
> when make is executed with -j option.
If someone on the mailing list understands why having
`CFLAGS += $(shell ...)` makes make -j non-parallel,
please let me know.
[...]
next prev parent reply other threads:[~2024-08-23 19:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-23 19:44 [PATCH bpf-next] selftests/bpf: use simply-expanded variables for libpcap flags Eduard Zingerman
2024-08-23 19:49 ` Eduard Zingerman [this message]
2024-08-23 22:30 ` 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=ca9ffdd75b8e5457264b6ddd567296a0f17dcf31.camel@gmail.com \
--to=eddyz87@gmail.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=kernel-team@fb.com \
--cc=martin.lau@linux.dev \
--cc=yonghong.song@linux.dev \
/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