From: Turbo Fredriksson <turbo@bayour.com>
To: linux-kernel@vger.kernel.org
Subject: Compile fails on SPARC64 - include/linux/sched.h:1171: request for member `break_lock' in something not a structure or union
Date: Mon, 28 Mar 2005 14:41:34 +0200 [thread overview]
Message-ID: <87d5tk2b9d.fsf@pumba.bayour.com> (raw)
Tried 2.6.11.6, 2.6.11.6-bk1 and 2.6.12-rc1.
----- s n i p -----
CHROOT Aurora/Woody-devel# make
CHK include/linux/version.h
CC init/main.o
In file included from include/linux/module.h:10,
from init/main.c:16:
include/linux/sched.h: In function `lock_need_resched':
include/linux/sched.h:1171: request for member `break_lock' in something not a structure or union
make[1]: *** [init/main.o] Error 1
make: *** [init] Error 2
----- s n i p -----
rgrep'ing in include/ shows that it's defined in all
but 'include/asm-sparc64/spinlock.h':
----- s n i p -----
CHROOT Aurora/Woody-devel# rgrep break_lock include | sort | uniq
include/asm-alpha/spinlock.h: unsigned int break_lock;
include/asm-arm/spinlock.h: unsigned int break_lock;
include/asm-i386/spinlock.h: unsigned int break_lock;
include/asm-ia64/spinlock.h: unsigned int break_lock;
include/asm-m32r/spinlock.h: unsigned int break_lock;
include/asm-mips/spinlock.h: unsigned int break_lock;
include/asm-parisc/spinlock.h: unsigned int break_lock;
include/asm-parisc/system.h: unsigned int break_lock;
include/asm-ppc/spinlock.h: unsigned int break_lock;
include/asm-ppc64/spinlock.h: unsigned int break_lock;
include/asm-s390/spinlock.h: unsigned int break_lock;
include/asm-sh/spinlock.h: unsigned int break_lock;
include/asm-sparc/spinlock.h: unsigned int break_lock;
include/asm-x86_64/spinlock.h: unsigned int break_lock;
include/linux/sched.h:# define need_lockbreak(lock) ((lock)->break_lock)
----- s n i p -----
Kernel config can be found at http://www.bayour.com/config-2.6.12-rc1.txt.
next reply other threads:[~2005-03-28 12:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-28 12:41 Turbo Fredriksson [this message]
2005-03-28 12:56 ` Willy Tarreau
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=87d5tk2b9d.fsf@pumba.bayour.com \
--to=turbo@bayour.com \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®