public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Michael Gerdau <mgd@technosis.de>
To: Ingo Molnar <mingo@elte.hu>
Cc: linux-kernel@vger.kernel.org, linux-rt-users@vger.kernel.org,
	Thomas Gleixner <tglx@linutronix.de>
Subject: Re: v2.6.22.1-rt1
Date: Thu, 12 Jul 2007 16:45:45 +0200	[thread overview]
Message-ID: <200707121645.46206.mgd@technosis.de> (raw)
In-Reply-To: <20070712121355.GA10949@elte.hu>

[-- Attachment #1: Type: text/plain, Size: 2772 bytes --]

[sorry Ingo for the dublicated post]

> to build a 2.6.22.1-rt1 tree, the following patches should be applied:
>  
>    http://kernel.org/pub/linux/kernel/v2.6/linux-2.6.22.1.tar.bz2
>    http://redhat.com/~mingo/realtime-preempt/patch-2.6.22.1-rt1

I get a compile error on my x86_64 dualcore sytem.

mgd@seneca:/usr/src/linux-2.6.22.1-rt1> make
  CHK     include/linux/version.h
  CHK     include/linux/utsrelease.h
  CALL    scripts/checksyscalls.sh
  CHK     include/linux/compile.h
  CC [M]  net/rfkill/rfkill-input.o
net/rfkill/rfkill-input.c: In function ‘rfkill_schedule_toggle’:
net/rfkill/rfkill-input.c:60: error: size of array ‘type name’ is negative
net/rfkill/rfkill-input.c:60: warning: comparison of distinct pointer types lacks a cast
net/rfkill/rfkill-input.c:68: error: size of array ‘type name’ is negative
net/rfkill/rfkill-input.c:68: warning: comparison of distinct pointer types lacks a cast
net/rfkill/rfkill-input.c: At top level:
net/rfkill/rfkill-input.c:82: warning: implicit declaration of function ‘__MUTEX_INITIALIZER’
net/rfkill/rfkill-input.c:82: warning: missing braces around initializer
net/rfkill/rfkill-input.c:82: warning: (near initialization for ‘rfkill_wlan.mutex’)
net/rfkill/rfkill-input.c:82: error: initializer element is not constant
net/rfkill/rfkill-input.c:82: error: (near initialization for ‘rfkill_wlan.mutex.lock.wait_lock.raw_lock.slock’)
net/rfkill/rfkill-input.c:82: error: initializer element is not constant
net/rfkill/rfkill-input.c:82: error: (near initialization for ‘rfkill_wlan.lock’)
net/rfkill/rfkill-input.c:83: warning: missing braces around initializer
net/rfkill/rfkill-input.c:83: warning: (near initialization for ‘rfkill_bt.mutex’)
net/rfkill/rfkill-input.c:83: error: initializer element is not constant
net/rfkill/rfkill-input.c:83: error: (near initialization for ‘rfkill_bt.mutex.lock.wait_lock.raw_lock.slock’)
net/rfkill/rfkill-input.c:83: error: initializer element is not constant
net/rfkill/rfkill-input.c:83: error: (near initialization for ‘rfkill_bt.lock’)
make[2]: *** [net/rfkill/rfkill-input.o] Fehler 1
make[1]: *** [net/rfkill] Fehler 2
make: *** [net] Fehler 2


I used a linux-2.6.22.tar.bz2 and applied patch-2.6.22.1.bz2 followed
by patch-2.6.22.1-rt1

I had copied my .config from my (working) 2.6.22-cfs-v19 directory and
issued a 'make oldconfig' using mostly defaults.

Best,
Michael
-- 
 Technosis GmbH, Geschäftsführer: Michael Gerdau, Tobias Dittmar
 Sitz Hamburg; HRB 89145 Amtsgericht Hamburg
 Vote against SPAM - see http://www.politik-digital.de/spam/
 Michael Gerdau       email: mgd@technosis.de
 GPG-keys available on request or at public keyserver

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

  parent reply	other threads:[~2007-07-12 14:45 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-12 12:13 v2.6.22.1-rt1 Ingo Molnar
2007-07-12 12:20 ` v2.6.22.1-rt1 Jiri Kosina
2007-07-12 14:45 ` Michael Gerdau [this message]
2007-07-12 16:01   ` v2.6.22.1-rt1 Ingo Molnar
2007-07-12 21:31     ` v2.6.22.1-rt1 Michael Gerdau
2007-07-13  0:12 ` v2.6.22.1-rt1 (-rt2) Fernando Lopez-Lezcano

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=200707121645.46206.mgd@technosis.de \
    --to=mgd@technosis.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rt-users@vger.kernel.org \
    --cc=mingo@elte.hu \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox