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
