From: john cooper <john.cooper@timesys.com>
To: "venkata jagadish.p" <cpvjagadeesh@gmail.com>
Cc: linux-kernel@vger.kernel.org, Ingo Molnar <mingo@elte.hu>,
john cooper <john.cooper@timesys.com>
Subject: Re: RT patched kernel debugging
Date: Wed, 16 Nov 2005 08:40:42 -0500 [thread overview]
Message-ID: <437B36DA.7090404@timesys.com> (raw)
In-Reply-To: <437B5FD3.7020404@gmail.com>
venkata jagadish.p wrote:
> Hi all,
> I am trying to debug the RT patched kernel with UML. But it is showing
> these errors
> My kernel version is 2.6.13 and applied patch-2.6.13-rt14 to this kernel
>
>
> gcc -Wall -Wstrict-prototypes -Wno-trigraphs -fno-strict-aliasing
> -fno-common -ffreestanding -O2 -fno-omit-frame-pointer
> -fno-optimize-sibling-calls -g -D__arch_um__ -DSUBARCH=\"i386\"
> -Iarch/um/include -I/usr/src/linux-2.6.13/arch/um/kernel/tt/include
> -I/usr/src/linux-2.6.13/arch/um/kernel/skas/include -Dvmap=kernel_vmap
> -Derrno=kernel_errno -Dsigprocmask=kernel_sigprocmask
> -fno-unit-at-a-time -U__i386__ -Ui386 -D_LARGEFILE64_SOURCE
> -Wdeclaration-after-statement -Wno-pointer-sign -nostdinc -isystem
> /usr/lib/gcc/i386-redhat-linux/4.0.0/include -D__KERNEL__ -Iinclude -S
> -o arch/um/kernel-offsets.s arch/um/sys-i386/kernel-offsets.c
> In file included from arch/um/sys-i386/kernel-offsets.c:3:
> include/linux/sched.h: In function ‘set_tsk_need_resched_delayed’:
> include/linux/sched.h:1465: error: ‘TIF_NEED_RESCHED_DELAYED’ undeclared
> (first use in this function)
That's odd. Did the patch apply cleanly?
TIF_NEED_RESCHED_DELAYED should be defined in
include/asm-i386/thread_info.h for an i386
target.
-john
--
john.cooper@timesys.com
next prev parent reply other threads:[~2005-11-16 13:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-16 16:35 RT patched kernel debugging venkata jagadish.p
2005-11-16 13:40 ` john cooper [this message]
2005-11-17 9:38 ` venkata jagadish.p
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=437B36DA.7090404@timesys.com \
--to=john.cooper@timesys.com \
--cc=cpvjagadeesh@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
/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