From: Ingo Molnar <mingo@elte.hu>
To: art <art@usfltd.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6.14-rt10 compilation error kernel/sched.c: In function ‘__cond_resched_raw_spinlock'
Date: Fri, 11 Nov 2005 22:08:37 +0100 [thread overview]
Message-ID: <20051111210837.GA6215@elte.hu> (raw)
In-Reply-To: <200511111446.AA29884834@usfltd.com>
* art <art@usfltd.com> wrote:
>
> LD arch/i386/mach-default/built-in.o
> LD arch/i386/crypto/built-in.o
> AS [M] arch/i386/crypto/aes-i586-asm.o
> CC [M] arch/i386/crypto/aes.o
> LD [M] arch/i386/crypto/aes-i586.o
> CC kernel/sched.o
> kernel/sched.c: In function ‘__cond_resched_raw_spinlock’:
> kernel/sched.c:4593: error: ‘struct <anonymous>’ has no member named ‘break_lock’
> kernel/sched.c:4593: error: ‘struct <anonymous>’ has no member named ‘break_lock’
> make[1]: *** [kernel/sched.o] Error 1
> make: *** [kernel] Error 2
-rt11 should fix this.
Ingo
prev parent reply other threads:[~2005-11-11 21:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-11 20:46 2.6.14-rt10 compilation error kernel/sched.c: In function ‘__cond_resched_raw_spinlock' art
2005-11-11 21:08 ` Ingo Molnar [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=20051111210837.GA6215@elte.hu \
--to=mingo@elte.hu \
--cc=art@usfltd.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