From: Akemi Yagi <toracat@elrepo.org>
To: linux-kernel@vger.kernel.org
Subject: Re: kernel-4.9.94 compile error: 'KMOD_DECOMP_LEN' undeclared
Date: Sat, 14 Apr 2018 17:29:28 +0000 (UTC) [thread overview]
Message-ID: <patdpo$3ej$1@blaine.gmane.org> (raw)
In-Reply-To: CAEwRVpOFS5UsyVHkHr+w_OR0eSpvT-CZGG6b4Vr6gxkc4rwO6g@mail.gmail.com
On Sat, 14 Apr 2018 17:41:13 +0800, Teck Choon Giam wrote:
> Hi,
>
> Compile linux-4.9.94 will have error related to KMOD_DECOMP_LEN
> undeclared. Searching string related to KMOD_DECOMP_LEN in
> linux-4.9.94 and linux-4.15.17 sources as below:
>
> <mock-chroot>sh-4.2# grep -r KMOD_DECOMP_LEN ./linux-4.15.17
> ./linux-4.15.17/tools/perf/tests/code-reading.c: char
> decomp_name[KMOD_DECOMP_LEN];
> ./linux-4.15.17/tools/perf/util/dso.h:#define KMOD_DECOMP_LEN
> sizeof(KMOD_DECOMP_NAME)
> ./linux-4.15.17/tools/perf/util/annotate.c: char tmp[KMOD_DECOMP_LEN];
> ./linux-4.15.17/tools/perf/util/dso.c: char newpath[KMOD_DECOMP_LEN];
> sh-4.2# grep -r KMOD_DECOMP_LEN ./linux-4.9.94
> ./linux-4.9.94/tools/perf/tests/code-reading.c: char
> decomp_name[KMOD_DECOMP_LEN];
> ./linux-4.9.94/tools/perf/util/dso.c: char newpath[KMOD_DECOMP_LEN];
>
> So I guess for linux-4.9.94 has not define KMOD_DECOMP_LEN in
> tools/perf/util/dso.h?
>
> Thanks.
>
> Regards,
> Giam Teck Choon
Just a note to say that we (ELRepo) see the same error when building kernel-4.4.128 on RHEL 6 and RHEL 7. Kernel 4.4.127 built fine.
Akemi
The ELRepo Project
next prev parent reply other threads:[~2018-04-14 17:31 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-14 9:41 kernel-4.9.94 compile error: 'KMOD_DECOMP_LEN' undeclared Teck Choon Giam
2018-04-14 17:29 ` Akemi Yagi [this message]
2018-04-20 9:29 ` Teck Choon Giam
2018-04-27 17:28 ` Randy Dunlap
2018-04-28 5:00 ` Greg Kroah-Hartman
2018-04-28 6:09 ` Randy Dunlap
2018-04-28 8:11 ` Greg Kroah-Hartman
2018-04-28 11:54 ` Teck Choon Giam
2018-04-28 11:58 ` Greg Kroah-Hartman
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='patdpo$3ej$1@blaine.gmane.org' \
--to=toracat@elrepo.org \
--cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox