[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20201103055419.GI2408@dhcp-12-153.nay.redhat.com>
Date: Tue, 3 Nov 2020 13:54:19 +0800
From: Hangbin Liu <haliu@...hat.com>
To: David Ahern <dsahern@...il.com>
Cc: Stephen Hemminger <stephen@...workplumber.org>,
Daniel Borkmann <daniel@...earbox.net>,
Alexei Starovoitov <ast@...nel.org>,
Martin KaFai Lau <kafai@...com>,
Song Liu <songliubraving@...com>, Yonghong Song <yhs@...com>,
David Miller <davem@...emloft.net>,
Jesper Dangaard Brouer <brouer@...hat.com>,
netdev@...r.kernel.org, bpf@...r.kernel.org,
Jiri Benc <jbenc@...hat.com>,
Andrii Nakryiko <andrii@...nel.org>,
Toke Høiland-Jørgensen <toke@...hat.com>
Subject: Re: [PATCHv3 iproute2-next 1/5] configure: add check_libbpf() for
later libbpf support
On Mon, Nov 02, 2020 at 08:37:37AM -0700, David Ahern wrote:
> On 10/29/20 9:11 AM, Hangbin Liu wrote:
> > This patch adds a check to see if we support libbpf. By default the
> > system libbpf will be used, but static linking against a custom libbpf
> > version can be achieved by passing LIBBPF_DIR to configure. FORCE_LIBBPF
> > can be set to force configure to abort if no suitable libbpf is found,
> > which is useful for automatic packaging that wants to enforce the
> > dependency.
> >
>
> Add an option to force libbpf off and use of the legacy code. i.e, yes
> it is installed, but don't use it.
>
> configure script really needs a usage to dump options like disabling libbpf.
>
Shouldn't we use libbpf by default if system support? The same like libmnl.
There is no options to force libnml off.
Thanks
Hangbin
Powered by blists - more mailing lists