From: Arnaldo Carvalho de Melo <acme@redhat.com>
To: Peter Foley <pefoley2@pefoley.com>
Cc: Jiri Olsa <jolsa@redhat.com>, LKML <linux-kernel@vger.kernel.org>,
wangnan0@huawei.com
Subject: Re: [PATCH v2] Fix objtool with clang
Date: Mon, 28 Nov 2016 17:35:49 -0200 [thread overview]
Message-ID: <20161128193549.GA2361@redhat.com> (raw)
In-Reply-To: <CAOFdcFN5AbMU=861S5bw+cSQQSzuGwYbWm5zyfak14NcUCjUZg@mail.gmail.com>
Em Mon, Nov 28, 2016 at 07:25:53AM -0800, Peter Foley escreveu:
> On Mon, Nov 28, 2016 at 7:00 AM, Arnaldo Carvalho de Melo
> <acme@redhat.com> wrote:
> > After I applied this I started getting this:
> >
> > CC /tmp/build/perf/tests/sw-clock.o
> > /tmp/build/perf/.plugin_jbd2.o.cmd:3: *** empty variable name. Stop.
> > Makefile:192: recipe for target '/tmp/build/perf/plugin_jbd2-in.o' failed
> > make[2]: *** [/tmp/build/perf/plugin_jbd2-in.o] Error 2
> > Makefile.perf:591: recipe for target '/tmp/build/perf/libtraceevent-dynamic-list' failed
> > make[1]: *** [/tmp/build/perf/libtraceevent-dynamic-list] Error 2
> > make[1]: *** Waiting for unfinished jobs....
> > CC /tmp/build/perf/tests/mmap-thread-lookup.o
>
> Odd, I can't reproduce that...
> Mind sending your gcc version + the output of make V=1 + the contents
> of the .cmd file causing the error?
I just updated to f25, lemme see if this still happens...
- Arnaldo
next prev parent reply other threads:[~2016-11-28 19:36 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-26 22:20 [PATCH] Fix objtool with clang Peter Foley
2016-11-27 16:14 ` Jiri Olsa
2016-11-28 2:43 ` [PATCH v2] " Peter Foley
2016-11-28 11:39 ` Jiri Olsa
2016-11-28 15:00 ` Arnaldo Carvalho de Melo
2016-11-28 15:25 ` Peter Foley
2016-11-28 16:58 ` Jiri Olsa
2016-11-28 19:40 ` Arnaldo Carvalho de Melo
2016-11-28 20:08 ` Jiri Olsa
2016-11-29 9:32 ` Jiri Olsa
2016-11-29 9:58 ` Jiri Olsa
2016-11-29 14:28 ` Jiri Olsa
2016-11-29 14:33 ` Arnaldo Carvalho de Melo
2016-11-29 14:39 ` Jiri Olsa
2016-11-29 14:49 ` Arnaldo Carvalho de Melo
2016-11-29 15:24 ` Jiri Olsa
2016-12-01 13:00 ` [PATCHv3] tools build: Make fixdep parsing wait for last target Jiri Olsa
2016-12-01 17:48 ` Peter Foley
2016-12-01 18:53 ` Arnaldo Carvalho de Melo
2016-12-02 8:49 ` Jiri Olsa
2016-12-02 9:15 ` Jiri Olsa
2016-12-02 15:10 ` Arnaldo Carvalho de Melo
2016-12-06 8:20 ` [tip:perf/core] " tip-bot for Jiri Olsa
2016-11-28 19:35 ` Arnaldo Carvalho de Melo [this message]
2016-12-06 8:20 ` [tip:perf/core] tools build: Fix objtool build with clang tip-bot for Peter Foley
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=20161128193549.GA2361@redhat.com \
--to=acme@redhat.com \
--cc=jolsa@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pefoley2@pefoley.com \
--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;
as well as URLs for NNTP newsgroup(s).