From: vrbagal1 <vrbagal1@linux.vnet.ibm.com>
To: linuxppc-dev@lists.ozlabs.org
Cc: sfr@canb.auug.org.au
Subject: Build Failure on linux-next on Power8 machine
Date: Thu, 31 May 2018 16:08:40 +0530 [thread overview]
Message-ID: <d377489b3333eca0951510c19b7d8878@linux.vnet.ibm.com> (raw)
Greetings!!!
I am observing a build failure on linux-next kernel.
Machine: Power8
Platform: PowerNV(Baremetal)
Git Tree:
https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
Below is the build error.
14:20:48 make[1]: *** [kernel/umh.o] Error 1
14:20:48 make[1]: *** [kernel/fork.o] Error 1
14:20:48 In file included from
./arch/powerpc/include/asm/highmem.h:30:0,
14:20:48 from ./include/linux/highmem.h:35,
14:20:48 from ./include/linux/pagemap.h:11,
14:20:48 from security/commoncap.c:19:
14:20:48 ./arch/powerpc/include/asm/fixmap.h:52:2: error: overflow in
enumeration values
14:20:48 FIX_KMAP_BEGIN, /* reserved pte's for temporary kernel
mappings */
14:20:48 ^
14:20:48 make[2]: *** [kernel/sched/swait.o] Error 1
14:20:48 make[1]: *** [mm/page_alloc.o] Error 1
14:20:48 make[1]: *** [kernel/sched] Error 2
14:20:48 make: *** [mm] Error 2
14:20:48 make[1]: *** [kernel/exit.o] Error 1
14:20:48 make[1]: *** [security/commoncap.o] Error 1
14:20:48 make[1]: *** [fs/kernfs] Error 2
14:20:48 make: *** [fs] Error 2
14:20:48 make: *** [arch/powerpc/kernel] Error 2
14:20:48 make: *** [security] Error 2
14:20:48 make: *** [kernel] Error 2
Cheers.
next reply other threads:[~2018-05-31 10:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-31 10:38 vrbagal1 [this message]
2018-05-31 11:14 ` Build Failure on linux-next on Power8 machine Christophe LEROY
2018-05-31 11:28 ` Venkat Rao B
2018-05-31 14:05 ` Michael Ellerman
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=d377489b3333eca0951510c19b7d8878@linux.vnet.ibm.com \
--to=vrbagal1@linux.vnet.ibm.com \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=sfr@canb.auug.org.au \
/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.