From mboxrd@z Thu Jan 1 00:00:00 1970 From: Stanislav Fomichev Subject: Re: [PATCH bpf] tools/bpf: properly account for libbfd variations Date: Tue, 15 Jan 2019 13:47:11 -0800 Message-ID: <20190115214711.GA726@mini-arch> References: <20190115195953.238574-1-sdf@google.com> <20190115133800.658999bd@cakuba.netronome.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: Stanislav Fomichev , netdev@vger.kernel.org, davem@davemloft.net, ast@kernel.org, daniel@iogearbox.net, quentin.monnet@netronome.com To: Jakub Kicinski Return-path: Received: from mail-pl1-f193.google.com ([209.85.214.193]:39253 "EHLO mail-pl1-f193.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1728421AbfAOVrO (ORCPT ); Tue, 15 Jan 2019 16:47:14 -0500 Received: by mail-pl1-f193.google.com with SMTP id 101so1910524pld.6 for ; Tue, 15 Jan 2019 13:47:13 -0800 (PST) Content-Disposition: inline In-Reply-To: <20190115133800.658999bd@cakuba.netronome.com> Sender: netdev-owner@vger.kernel.org List-ID: On 01/15, Jakub Kicinski wrote: > On Tue, 15 Jan 2019 11:59:53 -0800, Stanislav Fomichev wrote: > > On some platforms, in order to link against libbfd, we need to > > link against liberty and even possibly libz. Account for that > > in the bpftool Makefile. We now have proper feature detection > > for each case, so handle each one separately. > > > > See recent commit 14541b1e7e72 ("perf build: Don't unconditionally link the > > libbfd feature test to -liberty and -lz") where I fixed feature > > detection. > > > > Fixes: 29a9c10e4110 ("bpftool: make libbfd optional") > > Signed-off-by: Stanislav Fomichev > > Minor nits below, in any case: > > Acked-by: Jakub Kicinski > > Thanks for making bpftool build! :) > > > diff --git a/tools/bpf/bpftool/Makefile b/tools/bpf/bpftool/Makefile > > index 492f0f24e2d3..af9a25bf480d 100644 > > --- a/tools/bpf/bpftool/Makefile > > +++ b/tools/bpf/bpftool/Makefile > > @@ -92,10 +92,21 @@ BFD_SRCS = jit_disasm.c > > > > SRCS = $(filter-out $(BFD_SRCS),$(wildcard *.c)) > > > > -ifeq ($(feature-libbfd),1) > > +ifeq ($(feature-libbfd), 1) > > nit: no space there is more common > > $ git grep 'ifeq' | grep ',[^ ]' | wc -l > 482 > $ git grep 'ifeq' | grep ', ' | wc -l > 136 > > > > +LIBS += -lbfd -ldl -lopcodes > > nit: should this be indented? > > > +else > > + ifeq ($(feature-libbfd-liberty), 1) > > + LIBS += -lbfd -ldl -lopcodes -liberty > > + else > > + ifeq ($(feature-libbfd-liberty-z), 1) > > + LIBS += -lbfd -ldl -lopcodes -liberty -lz > > + endif > > Would this syntax: > > ifeq ($(feature-libbfd),1) > LIBS += .. > else ifeq ($(feature-libbfd-liberty),1) > LIBS += .. > else ifeq ($(feature-libbfd-liberty-z),1) > LIBS += .. > endif > > Not work? I does seem to work :-) This is the first time I see it being written that way. (but your link indeed shows that this syntax is supported) I'll post v2 shortly with all the nits addressed. Thanks for a quick review! > > https://www.gnu.org/software/make/manual/html_node/Conditional-Syntax.html > > I don't think I've ever tried, but looks more concise.. > > > + endif > > +endif > > + > > +ifneq ($(filter -lbfd,$(EXTLIBS)),) > > CFLAGS += -DHAVE_LIBBFD_SUPPORT > > SRCS += $(BFD_SRCS) > > -LIBS += -lbfd -lopcodes > > endif > > > > OBJS = $(patsubst %.c,$(OUTPUT)%.o,$(SRCS)) $(OUTPUT)disasm.o >