All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pavlos Parissis <pavlos.parissis@gmail.com>
To: namhyung@kernel.org
Cc: stable@vger.kernel.org, dsahern@gmail.com,
	a.p.zijlstra@chello.nl, wangnan0@huawei.com
Subject: Build failure for kernel 4.9.94 for perf
Date: Sun, 15 Apr 2018 14:31:07 +0200	[thread overview]
Message-ID: <ddf4e06c-6b95-cf69-49ef-eefd89e0ffdc@gmail.com> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 1795 bytes --]

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.

Cheers,
Pavlos Parissis




[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

             reply	other threads:[~2018-04-15 12:31 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-15 12:31 Pavlos Parissis [this message]
2018-04-16  8:14 ` Build failure for kernel 4.9.94 for perf Greg KH

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=ddf4e06c-6b95-cf69-49ef-eefd89e0ffdc@gmail.com \
    --to=pavlos.parissis@gmail.com \
    --cc=a.p.zijlstra@chello.nl \
    --cc=dsahern@gmail.com \
    --cc=namhyung@kernel.org \
    --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.