From: "Vladimir V. Saveliev" <vs@namesys.com>
To: gimpel <gimpel@sonnenkinder.org>
Cc: reiserfs-list@namesys.com
Subject: Re: reiser4 on 2.6.13-rc6-realtime-preempt
Date: Fri, 12 Aug 2005 13:05:33 +0400 [thread overview]
Message-ID: <42FC665D.4030802@namesys.com> (raw)
In-Reply-To: <20050811224503.7dbd67dd@SiRiUS.home>
Hello
gimpel wrote:
> Hello!
>
> I'm trying to compile a recent 2.6.13-rc6 with realtime-preempt-2.6.13-
> rc4-RT-V0.7.53-02 and want to add reiser4. 2.6.12-rt hardlocked very
> often here.
Which patches did you use?
> I managed to fix up the DEFINE_SPINLOCK and compat_semaphore wait;
> changes by taking a look on the changes between reiser4 for 2.6.12
> and 2.6.12-rt and it first seems to compile fine but ends up with:
>
> ----8<------
>
> CC init/version.o
> LD init/built-in.o
> LD .tmp_vmlinux1
> fs/built-in.o(.text+0x92999): In function `reiser4_put_super':
> : undefined reference to `rcu_barrier'
reiser4 depends on several core kernel patches. I think you did not apply them.
You might want to try to apply this patch
ftp://ftp.namesys.com/pub/reiser4-for-2.6/2.6.12/reiser4-for-2.6.12-realtime-preempt-2.6.12-final-V0.7.51-29.patch.gz
It contains all necessary patches already.
> fs/built-in.o(.text+0x929a9): In function `reiser4_put_super':
> : undefined reference to `rcu_barrier'
> fs/built-in.o(.text+0x97989): In function `_done_sinfo':
> : undefined reference to `rcu_barrier'
> fs/built-in.o(.text+0x97d76): In function `_done_formatted_fake':
> : undefined reference to `rcu_barrier'
> fs/built-in.o(.text+0x97d86): In function `_done_formatted_fake':
> : undefined reference to `rcu_barrier'
> make: *** [.tmp_vmlinux1] Fehler 1
>
> ----->8-----
>
> Maybe some has managed to fix that or knows how to do so and is willing
> to help me. My C knowledge is still too limited...
>
> regards and thanks in advance
> tom
>
next prev parent reply other threads:[~2005-08-12 9:05 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-11 20:45 reiser4 on 2.6.13-rc6-realtime-preempt gimpel
2005-08-12 9:05 ` Vladimir V. Saveliev [this message]
2005-08-12 10:09 ` gimpel
2005-08-12 18:41 ` Valdis.Kletnieks
2005-08-12 18:55 ` David Masover
2005-08-12 20:40 ` gimpel
2005-08-13 10:13 ` Vladimir V. Saveliev
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=42FC665D.4030802@namesys.com \
--to=vs@namesys.com \
--cc=gimpel@sonnenkinder.org \
--cc=reiserfs-list@namesys.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 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.