* Build failure for Linux 4.14.45
@ 2018-05-30 8:47 Pavlos Parissis
2018-05-30 9:36 ` Greg KH
2018-05-30 9:37 ` Greg KH
0 siblings, 2 replies; 4+ messages in thread
From: Pavlos Parissis @ 2018-05-30 8:47 UTC (permalink / raw)
To: stable
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?
Cheers,
Pavlos
^ permalink raw reply [flat|nested] 4+ messages in thread* Re: Build failure for Linux 4.14.45
2018-05-30 8:47 Build failure for Linux 4.14.45 Pavlos Parissis
@ 2018-05-30 9:36 ` Greg KH
2018-05-30 9:37 ` Greg KH
1 sibling, 0 replies; 4+ messages in thread
From: Greg KH @ 2018-05-30 9:36 UTC (permalink / raw)
To: Pavlos Parissis; +Cc: stable
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
^ permalink raw reply [flat|nested] 4+ messages in thread* Re: Build failure for Linux 4.14.45
2018-05-30 8:47 Build failure for Linux 4.14.45 Pavlos Parissis
2018-05-30 9:36 ` Greg KH
@ 2018-05-30 9:37 ` Greg KH
2018-05-30 13:56 ` Pavlos Parissis
1 sibling, 1 reply; 4+ messages in thread
From: Greg KH @ 2018-05-30 9:37 UTC (permalink / raw)
To: Pavlos Parissis; +Cc: stable
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?
Yes, reverting that patch fixes it for me. Let me go push out a .46
release with that fix in it, thanks for the quick report.
greg k-h
^ permalink raw reply [flat|nested] 4+ messages in thread* Re: Build failure for Linux 4.14.45
2018-05-30 9:37 ` Greg KH
@ 2018-05-30 13:56 ` Pavlos Parissis
0 siblings, 0 replies; 4+ messages in thread
From: Pavlos Parissis @ 2018-05-30 13:56 UTC (permalink / raw)
To: Greg KH; +Cc: stable
On 30 May 2018 at 11:37, Greg KH <greg@kroah.com> wrote:
> 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?
>
> Yes, reverting that patch fixes it for me. Let me go push out a .46
> release with that fix in it, thanks for the quick report.
>
> greg k-h
Thanks a lot for this very fast response and resolution. I can confirm
that kernel version 4.14.46 builds fine in my environment.
Cheers,
Pavlos
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2018-05-30 13:56 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2018-05-30 8:47 Build failure for Linux 4.14.45 Pavlos Parissis
2018-05-30 9:36 ` Greg KH
2018-05-30 9:37 ` Greg KH
2018-05-30 13:56 ` Pavlos Parissis
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).