From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: OMAP4 randconfig failure: Zynq
Date: Thu, 24 Jan 2013 16:06:09 +0000 [thread overview]
Message-ID: <20130124160609.GW23505@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <20130124155704.GJ11970@beefymiracle.amer.corp.natinst.com>
On Thu, Jan 24, 2013 at 09:57:04AM -0600, Josh Cartwright wrote:
> On Thu, Jan 24, 2013 at 11:11:17AM +0000, Russell King - ARM Linux wrote:
> > The OMAP4 randconfig build last night failed with this error:
> >
> > arch/arm/mach-zynq/common.c:99:14: error: 'irqchip_init' undeclared here (not in a function)
> >
> > Full details at the usual place -
> > http://www.arm.linux.org.uk/developer/build/
>
> Curious. This doesn't look like a valid config to me.
I think you're wrong.
> In particular, both ARCH_MULTIPLATFORM and ARCH_OMAP are selected, even
> though those selections should be mutually exclusive, since they fall
> under the same:
>
> choice
> prompt "ARM system type"
> default ARCH_MULTIPLATFORM
>
> Perhaps it's because CONFIG_ARCH_OMAP=y was setup in the seed?
ARCH_OMAP2PLUS selects ARCH_OMAP, and ARCH_OMAP2PLUS must be enabled
to produce a configuration including any OMAP code.
> oldconfig seems to complain, too:
>
> .config:340:warning: override: ARCH_OMAP changes choice state
Err, nope, don't get that warning.
$ mkdir /tmp/build
$ wget -O /tmp/build/.config 'http://www.arm.linux.org.uk/developer/build/file.php?type=config&idx=3562'
$ emake -j2 O=/tmp/build/ oldconfig
GEN /tmp/build/Makefile
HOSTCC scripts/basic/fixdep
HOSTCC scripts/kconfig/conf.o
SHIPPED scripts/kconfig/zconf.tab.c
SHIPPED scripts/kconfig/zconf.lex.c
SHIPPED scripts/kconfig/zconf.hash.c
HOSTCC scripts/kconfig/zconf.tab.o
HOSTLD scripts/kconfig/conf
scripts/kconfig/conf --oldconfig Kconfig
#
# configuration written to .config
#
So, the config system produced this configuration, and the config system
believes it to be correct. The problem lies elsewhere.
Clearly from the error, for a configuration for an OMAP platform to be
errored out by a Zynq error, that means there's something that Zynq is
missing.
next prev parent reply other threads:[~2013-01-24 16:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-24 11:11 OMAP4 randconfig failure: Zynq Russell King - ARM Linux
2013-01-24 15:57 ` Josh Cartwright
2013-01-24 16:06 ` Russell King - ARM Linux [this message]
2013-01-24 16:12 ` Russell King - ARM Linux
2013-01-24 17:08 ` Josh Cartwright
2013-01-24 17:27 ` Rob Herring
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=20130124160609.GW23505@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).