mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Thomas Gleixner <tglx@linutronix.de>
To: Tim Bird <tim.bird@am.sony.com>
Cc: linux kernel <linux-kernel@vger.kernel.org>,
	Ingo Molnar <mingo@redhat.com>,
	Steven Rostedt <rostedt@goodmis.org>,
	John Cooper <john.cooper@third-harmonic.com>
Subject: Re: rt-preempt: problem compiling rt-preempt 2.6.23.1-rt11 on MIPS
Date: Thu, 15 Nov 2007 01:56:14 +0100 (CET)	[thread overview]
Message-ID: <alpine.LFD.0.9999.0711150143220.3265@localhost.localdomain> (raw)
In-Reply-To: <473B8F91.20704@am.sony.com>

On Wed, 14 Nov 2007, Tim Bird wrote:

Added Steven and John to CC

> 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?

Hm, dunno why the rtc.h include was added.

> 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? :-)

I fear you are the one who is in charge to get mips working again :)
But as always, there are bad news and good news:  As far as I heard
last week John Cooper is looking into this as well.

Thanks,

	tglx

  reply	other threads:[~2007-11-15  0:56 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-15  0:15 Tim Bird
2007-11-15  0:56 ` Thomas Gleixner [this message]
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=alpine.LFD.0.9999.0711150143220.3265@localhost.localdomain \
    --to=tglx@linutronix.de \
    --cc=john.cooper@third-harmonic.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=rostedt@goodmis.org \
    --cc=tim.bird@am.sony.com \
    /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®