From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: Error in head-common.S file while ARM Linux booting
Date: Wed, 11 May 2011 20:58:30 +0100 [thread overview]
Message-ID: <20110511195830.GL5315@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <BANLkTikQHho9o+3dzbB-0Tq-ai2R5AAc5w@mail.gmail.com>
On Thu, May 05, 2011 at 12:54:11PM +0530, Madhavi Manchala wrote:
> <stdin>:46:0: warning: "__IGNORE_migrate_pages" redefined
> /home/openwrt-s3c2510/trunk/build_dir/linux-s3c2510/linux-2.6.36/arch/arm/include/asm/unistd.h:476:0: note: this is the location of the previous definition
> CHK include/generated/compile.h
> AS arch/arm/kernel/debug.o
> In file included from include/linux/cache.h:4:0,
> from include/linux/time.h:7,
> from include/linux/stat.h:60,
> from include/linux/module.h:10,
> from arch/arm/mach-s3c2510/include/mach/debug-macro.S:16,
> from arch/arm/kernel/debug.S:130:
> include/linux/kernel.h:42:0: warning: "ALIGN" redefined
> include/linux/linkage.h:61:0: note: this is the location of the previous definition
> include/linux/stddef.h: Assembler messages:
> include/linux/stddef.h:15: Error: bad instruction `enum {'
> include/linux/stddef.h:16: Error: junk at end of line, first unrecognized character is `,'
> include/linux/stddef.h:18: Error: junk at end of line, first unrecognized character is `}'
Looks to me like you're trying to include header files which contain C
constructs into an assembly file. There's nothing much more than "don't
do that" to be said about this.
Eg, you certainly shouldn't be including linux/module.h into
debug-macro.S.
prev parent reply other threads:[~2011-05-11 19:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-21 10:31 Error in head-common.S file while ARM Linux booting Madhavi Manchala
2011-04-21 20:22 ` Nicolas Pitre
2011-05-05 7:24 ` Madhavi Manchala
2011-05-11 19:58 ` Russell King - ARM Linux [this message]
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=20110511195830.GL5315@n2100.arm.linux.org.uk \
--to=linux@arm.linux.org.uk \
--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).