From: jeff angielski <jeff@theptrgroup.com>
To: linuxppc-dev@ozlabs.org
Subject: 2.6.29-rc6-rt2 fails for powerpc
Date: Mon, 23 Feb 2009 22:28:20 -0500 [thread overview]
Message-ID: <1235446100.23197.28.camel@penguin> (raw)
1. Git clone of the latest 2.6.29-rc6.
2. Applied the 2.6.29-rc6-rt2 patch.
3. Copied XXX config from arch/powerpc/configs to .config
4. make -j2 ARCH=powerpc oldconfig
5. make -j2 ARCH=powerpc
It fails with redefinition errors of the rwsem stuff from
arch/powerpc/include/asm/rwsem.h and include/linux/rt_lock.h.
Anybody else having this problem? Google was not my friend, nor the RT
Wiki...
The detailed compile output is here:
$ make -j2 ARCH=powerpc
scripts/kconfig/conf -s arch/powerpc/Kconfig
CHK include/linux/version.h
CHK include/linux/utsrelease.h
SYMLINK include/asm -> include/asm-powerpc
CC arch/powerpc/kernel/asm-offsets.s
In file included from include/linux/rwsem.h:37,
from include/linux/mm_types.h:11,
from include/linux/sched.h:61,
from arch/powerpc/kernel/asm-offsets.c:17:
/home/jaa/src/linux-2.6/arch/powerpc/include/asm/rwsem.h:24: error: redefinition of 'struct rw_semaphore'
In file included from include/linux/rwsem.h:37,
from include/linux/mm_types.h:11,
from include/linux/sched.h:61,
from arch/powerpc/kernel/asm-offsets.c:17:
/home/jaa/src/linux-2.6/arch/powerpc/include/asm/rwsem.h:46:1: warning: "__RWSEM_INITIALIZER" redefined
In file included from include/linux/spinlock.h:118,
from include/linux/seqlock.h:34,
from include/linux/time.h:8,
from include/linux/timex.h:56,
from include/linux/sched.h:54,
from arch/powerpc/kernel/asm-offsets.c:17:
include/linux/rt_lock.h:191:1: warning: this is the location of the previous definition
In file included from include/linux/rwsem.h:37,
from include/linux/mm_types.h:11,
from include/linux/sched.h:61,
from arch/powerpc/kernel/asm-offsets.c:17:
/home/jaa/src/linux-2.6/arch/powerpc/include/asm/rwsem.h:50:1: warning: "DECLARE_RWSEM" redefined
In file included from include/linux/spinlock.h:118,
from include/linux/seqlock.h:34,
from include/linux/time.h:8,
from include/linux/timex.h:56,
from include/linux/sched.h:54,
from arch/powerpc/kernel/asm-offsets.c:17:
include/linux/rt_lock.h:195:1: warning: this is the location of the previous definition
In file included from include/linux/rwsem.h:37,
from include/linux/mm_types.h:11,
from include/linux/sched.h:61,
from arch/powerpc/kernel/asm-offsets.c:17:
/home/jaa/src/linux-2.6/arch/powerpc/include/asm/rwsem.h:61:1: warning: "init_rwsem" redefined
In file included from include/linux/spinlock.h:118,
from include/linux/seqlock.h:34,
from include/linux/time.h:8,
from include/linux/timex.h:56,
from include/linux/sched.h:54,
from arch/powerpc/kernel/asm-offsets.c:17:
include/linux/rt_lock.h:232:1: warning: this is the location of the previous definition
/home/jaa/src/linux-2.6/arch/powerpc/include/asm/rwsem.h:167: error: expected identifier or '(' before '{' token
make[1]: *** [arch/powerpc/kernel/asm-offsets.s] Error 1
make: *** [prepare0] Error 2
--
Jeff Angielski
The PTR Group
www.theptrgroup.com
reply other threads:[~2009-02-24 3:28 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1235446100.23197.28.camel@penguin \
--to=jeff@theptrgroup.com \
--cc=linuxppc-dev@ozlabs.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).