From: Greg KH <greg@kroah.com>
To: Pavlos Parissis <pavlos.parissis@gmail.com>
Cc: stable@vger.kernel.org
Subject: Re: Build failure for Linux 4.14.45
Date: Wed, 30 May 2018 11:36:31 +0200 [thread overview]
Message-ID: <20180530093631.GA16949@kroah.com> (raw)
In-Reply-To: <CABOTfnO9pMV=AdMHbpnj--6oBVjVMyd7QKsL++UyNOXuv=beaA@mail.gmail.com>
On Wed, May 30, 2018 at 10:47:35AM +0200, Pavlos Parissis wrote:
> Hi,
>
> Building kernel version 4.14.45 fails on me with:
>
> DEBUG: builtin-record.c: In function '__cmd_record':
> DEBUG: builtin-record.c:935:6: error: 'data' undeclared (first use in
> this function)
> DEBUG: if (data->is_pipe && rec->evlist->nr_entries == 1)
> DEBUG: ^
> DEBUG: builtin-record.c:935:6: note: each undeclared identifier is
> reported only once for each function it appears in
> DEBUG: CC util/evsel_fprintf.o
> DEBUG: CC builtin-top.o
> DEBUG: CC util/find_bit.o
> DEBUG: CC util/kallsyms.o
> DEBUG: CC builtin-script.o
> DEBUG: CC util/levenshtein.o
> DEBUG: CC util/llvm-utils.o
> DEBUG: mv: cannot stat './.builtin-record.o.tmp': No such file or directory
> DEBUG: make[3]: *** [builtin-record.o] Error 1
> DEBUG: make[3]: *** Waiting for unfinished jobs....
>
> It could be related to f766148e47d7 ("perf record: Fix crash in pipe mode").
> Am I the only seeing this failure?
Ugh, yeah, I can reproduce this. Seems like no one builds perf to check
for breakage there :(
Let me see what needs to be done, thanks for the report...
greg k-h
next prev parent reply other threads:[~2018-05-30 9:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-30 8:47 Build failure for Linux 4.14.45 Pavlos Parissis
2018-05-30 9:36 ` Greg KH [this message]
2018-05-30 9:37 ` Greg KH
2018-05-30 13:56 ` Pavlos Parissis
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=20180530093631.GA16949@kroah.com \
--to=greg@kroah.com \
--cc=pavlos.parissis@gmail.com \
--cc=stable@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.