All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dragan Noveski <perodog@gmx.net>
To: Ingo Molnar <mingo@elte.hu>, linux-rt-users@vger.kernel.org
Subject: Re: 2.6.21.5-rt14 wont'compile here
Date: Sun, 17 Jun 2007 15:44:24 +0200	[thread overview]
Message-ID: <46753AB8.6070305@gmx.net> (raw)
In-Reply-To: <20070617131041.GD18095@elte.hu>

Ingo Molnar wrote:
> * Dragan Noveski <perodog@gmx.net> wrote:
>
>   
>> hi list,
>> since i am trying to compile 2.6.24/25 kernel with the rt-patches, no 
>> one version will compile here and i always get the same output.
>> this is how it looks like while trying to compile 2.6.21.4-rt13, but it 
>> looks the same for 2.6.21.5-rt14 :
>>     
>
>   
>>  LD      .tmp_vmlinux1
>> kernel/built-in.o:(.data+0x5d8): undefined reference to 
>> `preempt_mark_thresh'
>> make: *** [.tmp_vmlinux1] Fehler 1
>>     
>
> does the patch below fix this?
>
> 	Ingo
>
> Index: linux-rt.q/kernel/sysctl.c
> ===================================================================
> --- linux-rt.q.orig/kernel/sysctl.c
> +++ linux-rt.q/kernel/sysctl.c
> @@ -382,6 +382,8 @@ static ctl_table kern_table[] = {
>  		.mode		= 0644,
>  		.proc_handler	= &proc_doulongvec_minmax,
>  	},
> +#endif
> +#ifdef CONFIG_EVENT_TRACE
>  	{
>  		.ctl_name	= CTL_UNNUMBERED,
>  		.procname	= "preempt_mark_thresh",
> @@ -390,8 +392,6 @@ static ctl_table kern_table[] = {
>  		.mode		= 0644,
>  		.proc_handler	= &proc_doulongvec_minmax,
>  	},
> -#endif
> -#ifdef CONFIG_EVENT_TRACE
>  	{
>  		.ctl_name	= CTL_UNNUMBERED,
>  		.procname	= "trace_enabled",
>
>   
hi ingo, very much thanks for the patch, it is fixing the issue here.
i applied it to the 2.6.21.5-rt14 with '- p1' and the kernel just 
compiled successfully!

i am hurrying to do a reboot and check the performance now -thanks again!

cheers,
doc

      reply	other threads:[~2007-06-17 13:45 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-17 12:37 2.6.21.5-rt14 wont'compile here Dragan Noveski
2007-06-17 13:10 ` Ingo Molnar
2007-06-17 13:44   ` Dragan Noveski [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=46753AB8.6070305@gmx.net \
    --to=perodog@gmx.net \
    --cc=linux-rt-users@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 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.