From: Stanislav Fomichev <sdf@fomichev.me>
To: Jakub Kicinski <jakub.kicinski@netronome.com>
Cc: Stanislav Fomichev <sdf@google.com>,
netdev@vger.kernel.org, davem@davemloft.net, ast@kernel.org,
daniel@iogearbox.net, quentin.monnet@netronome.com
Subject: Re: [PATCH bpf v2] tools/bpf: properly account for libbfd variations
Date: Tue, 15 Jan 2019 14:00:06 -0800 [thread overview]
Message-ID: <20190115220006.GB726@mini-arch> (raw)
In-Reply-To: <20190115135510.0df374a1@cakuba.netronome.com>
On 01/15, Jakub Kicinski wrote:
> On Tue, 15 Jan 2019 13:52:48 -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.
> >
> > v2 (addressed Jakub's nits):
> > * better syntax for 'else ifeq'
> > * no space between ifeq args
> >
> > Fixes: 29a9c10e4110 ("bpftool: make libbfd optional")
> > Signed-off-by: Stanislav Fomichev <sdf@google.com>
> > ---
> > tools/bpf/bpftool/Makefile | 9 ++++++++-
> > 1 file changed, 8 insertions(+), 1 deletion(-)
> >
> > diff --git a/tools/bpf/bpftool/Makefile b/tools/bpf/bpftool/Makefile
> > index 492f0f24e2d3..fbf7e62a5b86 100644
> > --- a/tools/bpf/bpftool/Makefile
> > +++ b/tools/bpf/bpftool/Makefile
> > @@ -93,9 +93,16 @@ BFD_SRCS = jit_disasm.c
> > SRCS = $(filter-out $(BFD_SRCS),$(wildcard *.c))
> >
> > ifeq ($(feature-libbfd),1)
> > + LIBS += -lbfd -ldl -lopcodes
> > +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
> > +
> > +ifneq ($(filter -lbfd,$(EXTLIBS)),)
>
> Ah, I just noticed now that you use EXTLIBS here, not LIBS, is that on
> purpose?
Nice catch! Should be LIBS, probably copy-pasted it from somewhere :-(
>
> > CFLAGS += -DHAVE_LIBBFD_SUPPORT
> > SRCS += $(BFD_SRCS)
> > -LIBS += -lbfd -lopcodes
> > endif
> >
> > OBJS = $(patsubst %.c,$(OUTPUT)%.o,$(SRCS)) $(OUTPUT)disasm.o
>
next prev parent reply other threads:[~2019-01-15 22:00 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-15 19:59 [PATCH bpf] tools/bpf: properly account for libbfd variations Stanislav Fomichev
2019-01-15 21:38 ` Jakub Kicinski
2019-01-15 21:47 ` Stanislav Fomichev
2019-01-15 21:52 ` [PATCH bpf v2] " Stanislav Fomichev
2019-01-15 21:55 ` Jakub Kicinski
2019-01-15 22:00 ` Stanislav Fomichev [this message]
2019-01-15 22:03 ` [PATCH bpf v3] " Stanislav Fomichev
2019-01-15 22:06 ` Jakub Kicinski
2019-01-15 23:55 ` Daniel Borkmann
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=20190115220006.GB726@mini-arch \
--to=sdf@fomichev.me \
--cc=ast@kernel.org \
--cc=daniel@iogearbox.net \
--cc=davem@davemloft.net \
--cc=jakub.kicinski@netronome.com \
--cc=netdev@vger.kernel.org \
--cc=quentin.monnet@netronome.com \
--cc=sdf@google.com \
/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;
as well as URLs for NNTP newsgroup(s).