From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Russell King <rmk@arm•linux.org.uk>
Cc: linux-next@vger•kernel.org, Catalin Marinas <catalin.marinas@arm•com>
Subject: linux-next: arm tree build failure
Date: Sat, 14 Feb 2009 15:27:55 +1100 [thread overview]
Message-ID: <20090214152755.6f672b37.sfr@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 3205 bytes --]
Hi Russell,
Today's linux-next build (arm versatile_defconfig and many other configs)
failed like this:
AS usr/initramfs_data.o
arch/arm/include/asm/unwind.h: Assembler messages:
arch/arm/include/asm/unwind.h:68: Error: Bad macro parameter list
arch/arm/include/asm/unwind.h: Assembler messages:
arch/arm/include/asm/unwind.h:68: Error: arch/arm/kernel/entry-common.S:26: Error: bad instruction `unwind .fnstart'
arch/arm/kernel/entry-common.S:27: Error: Bad macro parameter listbad instruction `unwind .cantunwind'
arch/arm/kernel/entry-common.S:44: Error: bad instruction `unwind .fnend'
arch/arm/kernel/entry-armv.S:158: Error: bad instruction `unwind .fnstart'
arch/arm/kernel/entry-armv.S:158: Error: bad instruction `unwind .save{r0-pc}'
arch/arm/kernel/entry-armv.S:202: Error: bad instruction `unwind .fnend'
arch/arm/kernel/entry-armv.S:207: Error: bad instruction `unwind .fnstart'
arch/arm/kernel/entry-armv.S:207: Error: bad instruction `unwind .save{r0-pc}'
arch/arm/kernel/entry-armv.S:235: Error: bad instruction `unwind .fnend'
arch/arm/kernel/entry-armv.S:258: Error: bad instruction `unwind .fnstart'
arch/arm/kernel/entry-armv.S:258: Error: bad instruction `unwind .save{r0-pc}'
arch/arm/kernel/entry-armv.S:286: Error: bad instruction `unwind .fnend'
arch/arm/kernel/entry-armv.S:291: Error: bad instruction `unwind .fnstart'
arch/arm/kernel/entry-armv.S:291: Error: bad instruction `unwind .save{r0-pc}'
arch/arm/kernel/entry-armv.S:329: Error: bad instruction `unwind .fnend'
arch/arm/kernel/entry-armv.S:405: Error: bad instruction `unwind .fnstart'
arch/arm/kernel/entry-armv.S:405: Error: bad instruction `unwind .cantunwind'
arch/arm/kernel/entry-armv.S:432: Error: bad instruction `unwind .fnend'
arch/arm/kernel/entry-armv.S:437: Error: bad instruction `unwind .fnstart'
arch/arm/kernel/entry-armv.S:437: Error: bad instruction `unwind .cantunwind'
arch/arm/kernel/entry-armv.S:463: Error: bad instruction `unwind .fnend'
arch/arm/kernel/entry-armv.S:470: Error: bad instruction `unwind .fnstart'
arch/arm/kernel/entry-armv.S:470: Error: bad instruction `unwind .cantunwind'
arch/arm/kernel/entry-armv.S:498: Error: bad instruction `unwind .fnend'
arch/arm/kernel/entry-armv.S:673: Error: bad instruction `unwind .fnstart'
arch/arm/kernel/entry-armv.S:673: Error: bad instruction `unwind .cantunwind'
arch/arm/kernel/entry-armv.S:686: Error: bad instruction `unwind .fnend'
arch/arm/kernel/entry-armv.S:692: Error: bad instruction `unwind .fnstart'
arch/arm/kernel/entry-armv.S:693: Error: bad instruction `unwind .cantunwind'
arch/arm/kernel/entry-armv.S:697: Error: bad instruction `unwind .fnend'
arch/arm/kernel/entry-armv.S:707: Error: bad instruction `unwind .fnstart'
arch/arm/kernel/entry-armv.S:708: Error: bad instruction `unwind .cantunwind'
arch/arm/kernel/entry-armv.S:738: Error: bad instruction `unwind .fnend'
Presumably caused by commit 7e4e372df35c93e8f2693fd37010cec05c57ff47
("[ARM] 5383/1: unwind: Add core support for ARM stack unwinding").
Does this require a particular binutils version?
--
Cheers,
Stephen Rothwell sfr@canb•auug.org.au
http://www.canb.auug.org.au/~sfr/
[-- Attachment #2: Type: application/pgp-signature, Size: 197 bytes --]
next reply other threads:[~2009-02-14 4:28 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-14 4:27 Stephen Rothwell [this message]
2009-02-16 9:23 ` linux-next: arm tree build failure Catalin Marinas
-- strict thread matches above, loose matches on Subject: below --
2010-01-28 23:38 Stephen Rothwell
2010-01-29 23:45 ` Russell King
2010-01-30 1:27 ` Stephen Rothwell
2009-09-10 4:59 Stephen Rothwell
2009-09-14 8:20 ` Russell King
2009-04-14 7:48 Stephen Rothwell
2009-04-14 17:09 ` Russell King
2008-09-18 18:09 Stephen Rothwell
2008-09-18 18:26 ` Eric Miao
2008-09-18 18:33 ` Eric Miao
2008-09-18 22:04 ` Russell King
2008-09-18 22:28 ` Eric Miao
2008-08-19 5:53 Stephen Rothwell
2008-08-19 11:16 ` Marek Vasut
2008-08-19 11:21 ` Takashi Iwai
2008-08-19 16:06 ` Russell King
2008-08-19 16:32 ` Takashi Iwai
2008-08-20 0:01 ` Stephen Rothwell
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=20090214152755.6f672b37.sfr@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=catalin.marinas@arm$(echo .)com \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=rmk@arm$(echo .)linux.org.uk \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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