From: Jiri Olsa <jolsa@redhat.com>
To: Arnaldo Carvalho de Melo <acme@kernel.org>
Cc: Jiri Olsa <jolsa@kernel.org>, Wang Nan <wangnan0@huawei.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: tools/build: fixdep versus tools/lib/bpf
Date: Wed, 28 Oct 2015 21:13:52 +0100 [thread overview]
Message-ID: <20151028201352.GA14076@krava.brq.redhat.com> (raw)
In-Reply-To: <20151028163040.GA19695@kernel.org>
On Wed, Oct 28, 2015 at 01:30:40PM -0300, Arnaldo Carvalho de Melo wrote:
> Hi Jiri, Wang,
>
> I'm getting these while doing 'make -C tools/perf build-test':
>
> LD fixdep-in.o
> LINK fixdep
> /bin/sh: /home/acme/git/linux/tools/build/fixdep: Permission denied
> make[6]: *** [bpf.o] Error 1
> make[5]: *** [libbpf-in.o] Error 2
> make[4]: *** [/home/acme/git/linux/tools/lib/bpf/libbpf.a] Error 2
> make[4]: *** Waiting for unfinished jobs....
>
>
> It happens at different tests, i.e. seems like a race somewhere in the
> build system, can you take a look? It happens with my perf/ebpf branch.
could not reproduce, but looks like attached patch should help
jirka
---
diff --git a/tools/perf/Makefile.perf b/tools/perf/Makefile.perf
index 1e2e2d1d26b7..0d19d5447d6c 100644
--- a/tools/perf/Makefile.perf
+++ b/tools/perf/Makefile.perf
@@ -430,7 +430,7 @@ $(LIBAPI)-clean:
$(call QUIET_CLEAN, libapi)
$(Q)$(MAKE) -C $(LIB_DIR) O=$(OUTPUT) clean >/dev/null
-$(LIBBPF): FORCE
+$(LIBBPF): fixdep FORCE
$(Q)$(MAKE) -C $(BPF_DIR) O=$(OUTPUT) $(OUTPUT)libbpf.a
$(LIBBPF)-clean:
next prev parent reply other threads:[~2015-10-28 20:13 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-28 16:30 Arnaldo Carvalho de Melo
2015-10-28 20:13 ` Jiri Olsa [this message]
2015-10-28 20:37 ` Arnaldo Carvalho de Melo
2015-10-28 20:44 ` Jiri Olsa
2015-10-28 21:01 ` Arnaldo Carvalho de Melo
2015-10-29 2:39 ` Wangnan (F)
2015-10-30 9:13 ` [tip:perf/core] perf tools: Make sure fixdep is built before libbpf tip-bot for Jiri Olsa
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=20151028201352.GA14076@krava.brq.redhat.com \
--to=jolsa@redhat.com \
--cc=acme@kernel.org \
--cc=jolsa@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=wangnan0@huawei.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
Powered by JetHome