[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <60ab339a-3029-42db-97cf-d8574d05e789@daynix.com>
Date: Mon, 16 Oct 2023 20:57:17 +0900
From: Akihiko Odaki <akihiko.odaki@...nix.com>
To: Daniel Borkmann <daniel@...earbox.net>
Cc: Andrii Nakryiko <andrii@...nel.org>,
Mykola Lysenko <mykolal@...com>,
Alexei Starovoitov <ast@...nel.org>,
Martin KaFai Lau <martin.lau@...ux.dev>,
Song Liu <song@...nel.org>,
Yonghong Song <yonghong.song@...ux.dev>,
John Fastabend <john.fastabend@...il.com>,
KP Singh <kpsingh@...nel.org>,
Stanislav Fomichev <sdf@...gle.com>,
Hao Luo <haoluo@...gle.com>, Jiri Olsa <jolsa@...nel.org>,
Shuah Khan <shuah@...nel.org>, Nick Terrell <terrelln@...com>,
bpf@...r.kernel.org, linux-kselftest@...r.kernel.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH bpf-next] selftests/bpf: Use pkg-config to determine ld
flags
On 2023/10/16 20:39, Daniel Borkmann wrote:
> On 10/15/23 3:39 PM, Akihiko Odaki wrote:
>> When linking statically, libraries may require other dependencies to be
>> included to ld flags. In particular, libelf may require libzstd. Use
>> pkg-config to determine such dependencies.
>
> Is this not covered via -lz or is it that the name differs?
libelf may not only be linked with zlib but also with zstandard.
>
> Anyway, this change breaks selftest build for BPF CI (see below), could
> this
> either be made optional or detected differently?
>
> https://github.com/kernel-patches/bpf/actions/runs/6524480596/job/17716170021
I sent v2 (I forgot to add bpf-next to the subject for this).
This version implements a fallback just in the same way done for
HOSTPKG_CONFIG.
Powered by blists - more mailing lists