From: Catalin Marinas <catalin.marinas@arm•com>
To: Stephen Rothwell <sfr@canb•auug.org.au>
Cc: Russell King <rmk@arm•linux.org.uk>, linux-next@vger•kernel.org
Subject: Re: linux-next: arm tree build failure
Date: Mon, 16 Feb 2009 09:23:26 +0000 [thread overview]
Message-ID: <1234776206.30601.6.camel@pc1117.cambridge.arm.com> (raw)
In-Reply-To: <20090214152755.6f672b37.sfr@canb.auug.org.au>
On Sat, 2009-02-14 at 15:27 +1100, Stephen Rothwell wrote:
> 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
[...]
> Does this require a particular binutils version?
It looks like constructs like below are only supported by newer
binutils:
.macro unwind instr:vararg
\instr
.endm
I'll change it to classic C macros and re-post on the ARM kernel list.
Thanks.
--
Catalin
next prev parent reply other threads:[~2009-02-16 9:23 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-14 4:27 linux-next: arm tree build failure Stephen Rothwell
2009-02-16 9:23 ` Catalin Marinas [this message]
-- 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=1234776206.30601.6.camel@pc1117.cambridge.arm.com \
--to=catalin.marinas@arm$(echo .)com \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=rmk@arm$(echo .)linux.org.uk \
--cc=sfr@canb$(echo .)auug.org.au \
/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