From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: BUG: ARM build failures due to Xen
Date: Tue, 6 Nov 2012 17:57:49 +0000 [thread overview]
Message-ID: <20121106175749.GO28327@n2100.arm.linux.org.uk> (raw)
My build system is giving me the following errors against an OMAP4
randconfig build against the latest Linus' kernel plus arm-soc:
ERROR: "privcmd_call" [drivers/xen/xen-privcmd.ko] undefined!
make[2]: *** [__modpost] Error 1
make[2]: Target `_modpost' not remade because of errors.
make[1]: *** [modules] Error 2
make: *** [sub-make] Error 2
make: Target `uImage' not remade because of errors.
make: Target `modules' not remade because of errors.
Full build results and configuration are here:
http://www.arm.linux.org.uk/developer/build/result.php?type=build&idx=2627
http://www.arm.linux.org.uk/developer/build/file.php?type=config&idx=2627
next reply other threads:[~2012-11-06 17:57 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-06 17:57 Russell King - ARM Linux [this message]
2012-11-08 15:28 ` BUG: ARM build failures due to Xen Arnd Bergmann
2012-11-08 15:40 ` [Xen-devel] " Ian Campbell
2012-11-08 15:48 ` Stefano Stabellini
2012-11-08 15:58 ` Stefano Stabellini
2012-11-08 17:45 ` Arnd Bergmann
2012-11-09 12:50 ` Konrad Rzeszutek Wilk
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=20121106175749.GO28327@n2100.arm.linux.org.uk \
--to=linux@arm.linux.org.uk \
--cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).