From: tony@atomide.com (Tony Lindgren)
To: linux-arm-kernel@lists.infradead.org
Subject: OMAP* Latest build failures
Date: Wed, 14 Nov 2012 09:17:31 -0800 [thread overview]
Message-ID: <20121114171730.GS6801@atomide.com> (raw)
In-Reply-To: <20121114165947.GR6801@atomide.com>
* Tony Lindgren <tony@atomide.com> [121114 09:02]:
> * Tony Lindgren <tony@atomide.com> [121114 08:50]:
> > * Tomi Valkeinen <tomi.valkeinen@ti.com> [121114 03:47]:
> > > On 2012-11-14 11:26, Russell King - ARM Linux wrote:
> > > > OMAP* allnoconfig fails:
> > > >
> > > > arch/arm/mach-omap2/built-in.o: In function `omap_dss_set_min_bus_tput':
> > > > twl-common.c:(.text+0x1e08): undefined reference to `omap_pm_set_min_bus_tput'
> > > > arch/arm/mach-omap2/built-in.o: In function `omap_hwmod_init_postsetup':
> > > > twl-common.c:(.init.text+0x8f8): undefined reference to `omap_pm_if_early_init'
> > > > arch/arm/mach-omap2/built-in.o: In function `omap_serial_init_port':
> > > > twl-common.c:(.init.text+0x1284): undefined reference to `omap_pm_get_dev_context_loss_count'
> > > > arch/arm/mach-omap2/built-in.o: In function `omap_timer_init':
> > > > twl-common.c:(.init.text+0x1544): undefined reference to `omap_pm_get_dev_context_loss_count'
> > > > arch/arm/mach-omap2/built-in.o: In function `omap2_common_pm_init':
> > > > twl-common.c:(.init.text+0x1af0): undefined reference to `omap_pm_if_init'
> > > > arch/arm/mach-omap2/built-in.o: In function `omap2_gpio_dev_init':
> > > > twl-common.c:(.init.text+0x2168): undefined reference to `omap_pm_get_dev_context_loss_count'
> > > > arch/arm/mach-omap2/built-in.o: In function `omap_display_init':
> > > > twl-common.c:(.init.text+0x25cc): undefined reference to `omap_pm_get_dev_context_loss_count'
> > >
> > > I'm not able to reproduce this. I took v3.7-rc5, and the omap4430-sdp
> > > noconfig
> > > (http://www.arm.linux.org.uk/developer/build/file.php?type=config&idx=2711),
> > > and it builds fine for me.
> >
> > It happens if in arm-soc/for-next and rmk/for-next. Looks like the
> > CONFIG_OMAP_PM_NOOP can't be under CONFIG_PM in the makefile where I moved it
> > in commit 6e740f9a8.
>
> This should say just "It happens in arm-soc/for-next".
>
> > Looks like in my test configs I run make oldnoconfig on Russell's seed
> > config, and I do get CONFIG_PM=y set while Russell's generated config
> > does not have that. No ideas yet why oldnoconfig add CONFIG_PM=y..
Looks like the way to do this not to use oldnoconfig but to do:
$ make KCONFIG_ALLCONFIG=../configs/rmk-omap4430-sdp-noconfig allnoconfig
It seems that oldnoconfig will pick the new options that have default y?
Regards,
Tony
next prev parent reply other threads:[~2012-11-14 17:17 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-14 9:26 OMAP* Latest build failures Russell King - ARM Linux
2012-11-14 10:08 ` Peter Ujfalusi
2012-11-14 10:35 ` Russell King - ARM Linux
2012-11-14 11:45 ` Tomi Valkeinen
2012-11-14 16:48 ` Tony Lindgren
2012-11-14 16:59 ` Tony Lindgren
2012-11-14 17:17 ` Tony Lindgren [this message]
2012-11-14 17:44 ` Russell King - ARM Linux
2012-11-14 17:42 ` Russell King - ARM Linux
2012-11-17 9:33 ` Russell King - ARM Linux
2012-11-20 17:57 ` Tony Lindgren
2012-11-20 23:00 ` Jon Hunter
2012-11-28 15:18 ` Russell King - ARM Linux
2012-11-28 21:43 ` Jon Hunter
2012-11-28 14:04 ` Eduardo Valentin
2012-11-28 15:16 ` Russell King - ARM Linux
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=20121114171730.GS6801@atomide.com \
--to=tony@atomide.com \
--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).