public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Norval Watson <norv@longforest.com>
To: linux-kernel@vger.kernel.org
Subject: Re: [patch] Real-Time Preemption, -RT-2.6.12-rc3-V0.7.46-01
Date: Sun, 08 May 2005 13:30:45 +1000	[thread overview]
Message-ID: <1115523045.4132.28.camel@localhost.localdomain> (raw)

I have tried to build 2.6.12-rc3 kernel with Ingo's
realtime-preempt-2.6.12-rc3-V0.7.46-02 on amd64

When I enabled option 4, Complete Realtime, make bzImage failed as
described in Lee Revell's Apr 12 lkml post:
http://lkml.org/lkml/2005/4/12/523

"HOSTCC scripts/bin2c 
CC arch/x86_64/kernel/asm-offsets.s 
CHK include/asm-x86_64/offset.h 
UPD include/asm-x86_64/offset.h 
CC init/main.o 
In file included from include/linux/rwsem.h:38, 
from include/linux/kobject.h:24, 
from include/linux/module.h:19, 
from init/main.c:16: 
include/asm/rwsem.h:55: error: redefinition of `struct rw_semaphore' 
etc etc......"

When I started again with option 3, Low Latency Desktop, the build got a
bit further before hanging: (Full ouput:
http://www.longforest.com/index.php?option=com_content&task=view&id=133&Itemid=2 )

"
  CC      arch/x86_64/kernel/head64.o
  CC      arch/x86_64/kernel/init_task.o
arch/x86_64/kernel/init_task.c:17: warning: implicit declaration of
function `__RWSEM_INITIALIZER'
arch/x86_64/kernel/init_task.c:17: warning: missing braces around
initializer

...etc etc etc...

 constant
arch/x86_64/kernel/init_task.c:17: error: (near initialization for
`init_mm.default_kioctx')
make[1]: *** [arch/x86_64/kernel/init_task.o] Error 1
make: *** [arch/x86_64/kernel] Error 2"

Please CC any advice (or abuse!),
I can supply further info if required
Cheers,
Norv


             reply	other threads:[~2005-05-08  3:21 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-08  3:30 Norval Watson [this message]
  -- strict thread matches above, loose matches on Subject: below --
2005-03-25 14:59 [patch] Real-Time Preemption, -RT-2.6.12-rc1-V0.7.41-10 Ingo Molnar
2005-03-31  8:55 ` [patch] Real-Time Preemption, -RT-2.6.12-rc1-V0.7.41-25 Ingo Molnar
2005-04-01 10:47   ` [patch] Real-Time Preemption, -RT-2.6.12-rc1-V0.7.43-00 Ingo Molnar
2005-04-05  7:19     ` [patch] Real-Time Preemption, -RT-2.6.12-rc2-V0.7.44-00 Ingo Molnar
2005-04-21  7:35       ` [patch] Real-Time Preemption, -RT-2.6.12-rc3-V0.7.46-00 Ingo Molnar
2005-04-22  6:27         ` [patch] Real-Time Preemption, -RT-2.6.12-rc3-V0.7.46-01 Ingo Molnar
2005-04-22  7:34           ` Ingo Molnar
2005-04-22 15:48             ` Daniel Walker
2005-04-22 15:49               ` Ingo Molnar
2005-04-22 15:53                 ` Daniel Walker
2005-04-22 15:55                   ` Ingo Molnar
2005-04-22 15:56                     ` Ingo Molnar
2005-04-26 17:49                     ` Daniel Walker
2005-05-09  7:23                       ` Ingo Molnar
2005-04-22 21:06             ` Inaky Perez-Gonzalez
2005-04-22 21:15               ` Daniel Walker
2005-05-04  8:24                 ` Ingo Molnar
2005-04-22 21:17               ` Daniel Walker
2005-04-30 23:28           ` Lee Revell
2005-05-04  8:22             ` Ingo Molnar
2005-05-04 15:05               ` Lee Revell

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=1115523045.4132.28.camel@localhost.localdomain \
    --to=norv@longforest.com \
    --cc=linux-kernel@vger.kernel.org \
    /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