From: Dmitry Lysenko <dvl36.ripe.nick@gmail.com>
To: linux-rt-users@vger.kernel.org
Subject: Build failure. Typo in the 3.2.43-rt63 patch?
Date: Sat, 20 Apr 2013 12:09:39 +0300 [thread overview]
Message-ID: <51725B53.2030204@gmail.com> (raw)
Hi,
After applying rt63 patch to fresh 3.2.43 I got:
....
CC kernel/rcutiny.o
In file included from kernel/rcutiny.c:54:0:
kernel/rcutiny_plugin.h: In function 'invoke_rcu_callbacks':
kernel/rcutiny_plugin.h:886:2: error: implicit declaration of function
'swake_up' [-Werror=implicit-function-declaration]
cc1: some warnings being treated as errors
make[2]: *** [kernel/rcutiny.o] Error 1
make[1]: *** [kernel] Error 2
make[1]: Leaving directory `/root/linux-3.2.43'
make: *** [debian/stamp/build/kernel] Error 2
--------
Then I tried this:
-------
root@debian:~/linux-3.2.43# grep -R swake_up
kernel/rcutiny_plugin.h: swake_up(&rcu_kthread_wq);
patch-3.2.43-rt63.patch:+ swake_up(&rcu_kthread_wq);
root@debian:~/linux-3.2.43#
-------
Finally I manualy changed swake_up to swait_wake in rcutiny_plugin.h
(line 886).
(don't know is it right), but kernel is builded now.
Dmitry.
P.S. Marvell Kirkwood native build.
next reply other threads:[~2013-04-20 9:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-20 9:09 Dmitry Lysenko [this message]
2013-05-01 13:38 ` Build failure. Typo in the 3.2.43-rt63 patch? Steven Rostedt
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=51725B53.2030204@gmail.com \
--to=dvl36.ripe.nick@gmail.com \
--cc=linux-rt-users@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;
as well as URLs for NNTP newsgroup(s).