From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: IMX breaking Versatile Express build
Date: Tue, 23 Oct 2012 10:08:05 +0100 [thread overview]
Message-ID: <20121023090805.GQ21164@n2100.arm.linux.org.uk> (raw)
The latest Versatile Express specific build is failing due to:
arch/arm/mach-imx/built-in.o: In function `imx_cpu_die':
platform-imx-dma.c:(.text+0x1624): undefined reference to `imx_enable_cpu'
arch/arm/mach-imx/built-in.o: In function `imx_boot_secondary':
platform-imx-dma.c:(.cpuinit.text+0x14): undefined reference to `imx_set_cpu_jump'
platform-imx-dma.c:(.cpuinit.text+0x20): undefined reference to `imx_enable_cpu'
Config:
http://www.home.arm.linux.org.uk/developer/build/file.php?type=config&idx=2464
This does not seem to have any IMX support selected.
Thanks to the reduced default configuration files, Kconfig is deciding to
select the new MULTI_* options on these target specific Kconfigs, which
may have some reason as to the above.
However, even so, we should _not_ be seeing such build failures. It looks
to me like platform-imx-dma is missing some kind of dependency.
next reply other threads:[~2012-10-23 9:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-23 9:08 Russell King - ARM Linux [this message]
2012-10-23 10:48 ` IMX breaking Versatile Express build Shawn Guo
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=20121023090805.GQ21164@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).