* [ukl:efm32 14/19] io.c:(.text+0x12b8): undefined reference to `unwind_backtrace'
@ 2012-10-17 11:36 Fengguang Wu
2012-10-17 11:54 ` Uwe Kleine-König
2012-10-17 12:02 ` Fengguang Wu
0 siblings, 2 replies; 3+ messages in thread
From: Fengguang Wu @ 2012-10-17 11:36 UTC (permalink / raw)
To: kernel-janitors
Hi Uwe,
FYI, kernel build failed on
tree: git://git.pengutronix.de/git/ukl/linux efm32
head: ace35988f9089852b4d7278442ead682fb1fe7a7
commit: 304b1a8cda3ba8a550a9b2568e027d09bbf65829 [14/19] HACK! make stack dumps provoked by BUG a bit more helpful
config: arm-imx_v6_v7_defconfig # make ARCH=arm imx_v6_v7_defconfig
All error/warnings:
arch/arm/kernel/built-in.o: In function `show_regs':
io.c:(.text+0x12b8): undefined reference to `unwind_backtrace'
---
0-DAY kernel build testing backend Open Source Technology Center
Fengguang Wu, Yuanhan Liu Intel Corporation
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: [ukl:efm32 14/19] io.c:(.text+0x12b8): undefined reference to `unwind_backtrace'
2012-10-17 11:36 [ukl:efm32 14/19] io.c:(.text+0x12b8): undefined reference to `unwind_backtrace' Fengguang Wu
@ 2012-10-17 11:54 ` Uwe Kleine-König
2012-10-17 12:02 ` Fengguang Wu
1 sibling, 0 replies; 3+ messages in thread
From: Uwe Kleine-König @ 2012-10-17 11:54 UTC (permalink / raw)
To: kernel-janitors
Hello,
On Wed, Oct 17, 2012 at 07:36:10PM +0800, Fengguang Wu wrote:
> Hi Uwe,
>
> FYI, kernel build failed on
Thanks for testing.
> tree: git://git.pengutronix.de/git/ukl/linux efm32
> head: ace35988f9089852b4d7278442ead682fb1fe7a7
> commit: 304b1a8cda3ba8a550a9b2568e027d09bbf65829 [14/19] HACK! make stack dumps provoked by BUG a bit more helpful
> config: arm-imx_v6_v7_defconfig # make ARCH=arm imx_v6_v7_defconfig
>
> All error/warnings:
>
> arch/arm/kernel/built-in.o: In function `show_regs':
> io.c:(.text+0x12b8): undefined reference to `unwind_backtrace'
I'm quite aware that commit 304b1a8cd is bad. That's why it's prefixed
with "HACK!". Also even if you can compile a kernel with
e97f732 HACK! ARM: no, we don't enter in ARM
it won't run on anything because it changes how the kernel must be
entered.
I don't know why you picked the efm32 branch of my tree, but note that
obviously it is not meant to be included in mainline as is. If you want
to do some testing, better pick my for-next branch.
Thanks
Uwe
--
Pengutronix e.K. | Uwe Kleine-König |
Industrial Linux Solutions | http://www.pengutronix.de/ |
--
To unsubscribe from this list: send the line "unsubscribe kernel-janitors" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: [ukl:efm32 14/19] io.c:(.text+0x12b8): undefined reference to `unwind_backtrace'
2012-10-17 11:36 [ukl:efm32 14/19] io.c:(.text+0x12b8): undefined reference to `unwind_backtrace' Fengguang Wu
2012-10-17 11:54 ` Uwe Kleine-König
@ 2012-10-17 12:02 ` Fengguang Wu
1 sibling, 0 replies; 3+ messages in thread
From: Fengguang Wu @ 2012-10-17 12:02 UTC (permalink / raw)
To: kernel-janitors
Hi Uwe,
On Wed, Oct 17, 2012 at 01:54:20PM +0200, Uwe Kleine-König wrote:
> Hello,
>
> On Wed, Oct 17, 2012 at 07:36:10PM +0800, Fengguang Wu wrote:
> > Hi Uwe,
> >
> > FYI, kernel build failed on
> Thanks for testing.
>
> > tree: git://git.pengutronix.de/git/ukl/linux efm32
> > head: ace35988f9089852b4d7278442ead682fb1fe7a7
> > commit: 304b1a8cda3ba8a550a9b2568e027d09bbf65829 [14/19] HACK! make stack dumps provoked by BUG a bit more helpful
> > config: arm-imx_v6_v7_defconfig # make ARCH=arm imx_v6_v7_defconfig
> >
> > All error/warnings:
> >
> > arch/arm/kernel/built-in.o: In function `show_regs':
> > io.c:(.text+0x12b8): undefined reference to `unwind_backtrace'
> I'm quite aware that commit 304b1a8cd is bad. That's why it's prefixed
> with "HACK!". Also even if you can compile a kernel with
>
> e97f732 HACK! ARM: no, we don't enter in ARM
>
> it won't run on anything because it changes how the kernel must be
> entered.
Yeah, the title made it obvious that it's not serious. My build system
is just blindly testing every branches in the tree..
> I don't know why you picked the efm32 branch of my tree, but note that
> obviously it is not meant to be included in mainline as is. If you want
> to do some testing, better pick my for-next branch.
OK, I'll limit the tests to your for-next branch.
Thanks,
Fengguang
--
To unsubscribe from this list: send the line "unsubscribe kernel-janitors" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2012-10-17 12:02 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2012-10-17 11:36 [ukl:efm32 14/19] io.c:(.text+0x12b8): undefined reference to `unwind_backtrace' Fengguang Wu
2012-10-17 11:54 ` Uwe Kleine-König
2012-10-17 12:02 ` Fengguang Wu
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).