From: Tim Bird <tim.bird@am.sony.com>
To: linux kernel <linux-kernel@vger.kernel.org>
Cc: Ingo Molnar <mingo@redhat.com>, Thomas Gleixner <tglx@linutronix.de>
Subject: rt-preempt: problem compiling rt-preempt 2.6.23.1-rt11 on MIPS
Date: Wed, 14 Nov 2007 16:15:13 -0800 [thread overview]
Message-ID: <473B8F91.20704@am.sony.com> (raw)
I applied the patches in patch-2.6.23.1-rt11-broken-out.tar.bz2
to a Linux kernel version 2.6.23.1 (along with a few other
board specific patches).
I got the following compilation error:
GEN /home/tbird/work/rt-preempt/build/tx49/Makefile
CHK include/linux/version.h
CHK include/linux/utsrelease.h
CALL /home/tbird/work/rt-preempt/linux-2.6.23.1-rt11/scripts/checksyscalls.sh
CHK include/linux/compile.h
CC kernel/latency_trace.o
/home/tbird/work/rt-preempt/linux-2.6.23.1-rt11/kernel/latency_trace.c:28:21: error: asm/rtc.h: No such file or directory
make[2]: *** [kernel/latency_trace.o] Error 1
make[1]: *** [kernel] Error 2
make: *** [vmlinux] Error 2
Indeed, there is no include/asm-mips/rtc.h.
I commented out the include line in latency_trace.c, and everything
compiled fine. I'm not sure what is needed in an arch-specific rtc.h,
but compiling without it for the mips arch caused no problems.
Should I create a patch with a stub for rtc.h for mips?
As an aside, this has me worried. Is anyone else doing any
RT Preempt testing or work on MIPS platforms, or am I forging
new ground? :-)
-- Tim
=============================
Tim Bird
Architecture Group Chair, CE Linux Forum
Senior Staff Engineer, Sony Corporation of America
=============================
next reply other threads:[~2007-11-15 0:14 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-15 0:15 Tim Bird [this message]
2007-11-15 0:56 ` rt-preempt: problem compiling rt-preempt 2.6.23.1-rt11 on MIPS Thomas Gleixner
2007-11-15 1:06 ` Steven Rostedt
2007-11-15 1:20 ` Tim Bird
2007-11-15 1:27 ` Steven Rostedt
2007-11-15 2:24 ` john cooper
2007-11-15 23:31 ` MIPS RT debug support Tim Bird
2007-11-16 1:00 ` Steven Rostedt
2007-11-16 1:55 ` john cooper
2007-11-16 2:25 ` Steven Rostedt
2007-11-16 11:56 ` john cooper
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=473B8F91.20704@am.sony.com \
--to=tim.bird@am.sony.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=tglx@linutronix.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.