public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: Michal Schmidt <xschmi00@stud.feec.vutbr.cz>
Cc: Parag Warudkar <kernel-stuff@comcast.net>, linux-kernel@vger.kernel.org
Subject: Re: RT patch breaks X86_64 build
Date: Wed, 1 Jun 2005 11:13:44 +0200	[thread overview]
Message-ID: <20050601091344.GB11703@elte.hu> (raw)
In-Reply-To: <429C530E.70704@stud.feec.vutbr.cz>


* Michal Schmidt <xschmi00@stud.feec.vutbr.cz> wrote:

> Parag Warudkar wrote:
> >  CC      kernel/latency.o
> >kernel/latency.c:854: error: `NR_syscalls' undeclared here (not in a 
> >function)
> >
> >x86_64 doesn't seem to be defining NR_syscalls anywhere.. Shouldn't it be 
> >part of unistd.h as other arches do?
> 
> I noticed that error too. AFAIK this is not a new error in -RT, 
> latency.o never compiled on x86_64 for me. For now just disable 
> Latency tracing (CONFIG_LATENCY_TRACE).

indeed it was broken - i fixed x64 LATENCY_TRACE in the -47-16 kernel.

	Ingo

  reply	other threads:[~2005-06-01  9:14 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-31  1:41 RT patch breaks X86_64 build Parag Warudkar
2005-05-31  2:01 ` Parag Warudkar
2005-05-31  6:08   ` Michal Schmidt
2005-05-31 11:53     ` Parag Warudkar
2005-05-31 12:05       ` Michal Schmidt
2005-06-01  9:13         ` Ingo Molnar [this message]
2005-06-02 12:28           ` Michal Schmidt
2005-06-02 12:39             ` Ingo Molnar
2005-06-02 14:13               ` Michal Schmidt
2005-06-02 15:55                 ` Michal Schmidt
2005-06-02 16:17                 ` Ingo Molnar
2005-06-02 16:37                   ` Michal Schmidt
2005-06-02 18:04               ` Michal Schmidt
2005-06-02 18:33                 ` Ingo Molnar
2005-06-02 22:45                   ` Michal Schmidt
2005-06-03  5:18                     ` Ingo Molnar
2005-06-03 11:03                       ` Michal Schmidt
2005-06-02 12:31           ` Michal Schmidt
2005-06-02 12:37             ` Ingo Molnar

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=20050601091344.GB11703@elte.hu \
    --to=mingo@elte.hu \
    --cc=kernel-stuff@comcast.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=xschmi00@stud.feec.vutbr.cz \
    /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