From: Greg KH <greg@kroah.com>
To: Pavlos Parissis <pavlos.parissis@gmail.com>
Cc: namhyung@kernel.org, stable@vger.kernel.org, dsahern@gmail.com,
a.p.zijlstra@chello.nl, wangnan0@huawei.com
Subject: Re: Build failure for kernel 4.9.94 for perf
Date: Mon, 16 Apr 2018 10:14:24 +0200 [thread overview]
Message-ID: <20180416081424.GA31664@kroah.com> (raw)
In-Reply-To: <ddf4e06c-6b95-cf69-49ef-eefd89e0ffdc@gmail.com>
On Sun, Apr 15, 2018 at 02:31:07PM +0200, Pavlos Parissis wrote:
> Hi,
>
> Building 4.9.94 in the same way we have been building previous 4.9 releases yields the following error:
>
> DEBUG: tests/code-reading.c: In function 'read_object_code':
> DEBUG: tests/code-reading.c:228:19: error: 'KMOD_DECOMP_LEN' undeclared (first use in this function)
> DEBUG: char decomp_name[KMOD_DECOMP_LEN];
> DEBUG: ^
> DEBUG: tests/code-reading.c:228:19: note: each undeclared identifier is reported only once for each
> function it appears in
> DEBUG: tests/code-reading.c:291:3: warning: implicit declaration of function
> 'dso__decompress_kmodule_path' [-Wimplicit-function-declaration]
> DEBUG: if (dso__decompress_kmodule_path(al.map->dso, objdump_name,
> DEBUG: ^
> DEBUG: tests/code-reading.c:291:3: warning: nested extern declaration of
> 'dso__decompress_kmodule_path' [-Wnested-externs]
> DEBUG: tests/code-reading.c:228:7: warning: unused variable 'decomp_name' [-Wunused-variable]
> DEBUG: char decomp_name[KMOD_DECOMP_LEN];
> DEBUG: ^
> DEBUG: CC tests/topology.o
> DEBUG: CC tests/cpumap.o
> DEBUG: CC tests/stat.o
> DEBUG: CC tests/event_update.o
> DEBUG: mv: cannot stat 'tests/.code-reading.o.tmp': No such file or directory
> DEBUG: make[3]: *** [tests/code-reading.o] Error 1
> DEBUG: make[3]: *** Waiting for unfinished jobs....
> DEBUG: make[2]: *** [util] Error 2
> DEBUG: make[1]: *** [libperf-in.o] Error 2
> DEBUG: make[1]: *** Waiting for unfinished jobs....
> DEBUG: LD bench/perf-in.o
> DEBUG: make[2]: *** [tests] Error 2
> DEBUG: make[1]: *** [perf-in.o] Error 2
>
> As far as I can see, KMOD_DECOMP_LEN was introduced by 7525a238be8f ("perf tests: Decompress kernel
> module before objdump"), but I have zero deep knowledge in this area so I may be very wrong here.
Yeah, looks like I need to just revert this patch, thanks, I'll do that
for the next release.
greg k-h
prev parent reply other threads:[~2018-04-16 8:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-15 12:31 Build failure for kernel 4.9.94 for perf Pavlos Parissis
2018-04-16 8:14 ` Greg KH [this message]
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=20180416081424.GA31664@kroah.com \
--to=greg@kroah.com \
--cc=a.p.zijlstra@chello.nl \
--cc=dsahern@gmail.com \
--cc=namhyung@kernel.org \
--cc=pavlos.parissis@gmail.com \
--cc=stable@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 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.