Skip to contentSkip to conversation

io.c:(.text+0x12b8): undefined reference to `unwind_backtrace'

PATCH In review Fengguang Wu 2 participants 3 messages Oct 17, 2012 Kernel janitors

lore
Share & tools
lore

Fengguang Wu

author
#0 lore raw

PATCH 14/19 io.c:(.text+0x12b8): undefined reference to `unwind_backtrace'

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

#1 lore raw

Hello,

Quoted 3 lines · Fengguang Wu

Hi Uwe,

FYI, kernel build failed on

Thanks for testing.

Quoted 9 lines
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

Signature · 6 lines
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 [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
author
#2 lore raw
In reply to Fengguang Wu

Hi Uwe,

Quoted 17 lines · Uwe Kleine-König

Hello,

Quoted 3 lines · Fengguang Wu

Hi Uwe,

FYI, kernel build failed on

Thanks for testing.

Quoted 9 lines
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'

Quoted 7 lines

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..

Quoted 3 lines

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 [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html