From: Iratxo Pichel Ortiz <ipichel@albentia.com>
To: linux-rt-users@vger.kernel.org
Cc: David Garcia <dgarcia@albentia.com>
Subject: Compilation fails
Date: Wed, 20 Jun 2012 19:57:50 +0200 [thread overview]
Message-ID: <4FE20F1E.3010306@albentia.com> (raw)
Hi all!
We have detected a compilation error in the following scenario:
1. kernel linux-3.4.3
2. patch-3.4.3-rt11.patch
3. make mpc85xx_defconfig
4. Select full preemption.
After make you get:
$ make
scripts/kconfig/conf --silentoldconfig Kconfig
#
# configuration written to .config
#
CHK include/linux/version.h
CHK include/generated/utsrelease.h
CC arch/powerpc/kernel/asm-offsets.s
In file included from include/linux/spinlock.h:273:0,
from include/linux/seqlock.h:29,
from include/linux/time.h:8,
from include/linux/timex.h:56,
from include/linux/sched.h:57,
from arch/powerpc/kernel/asm-offsets.c:17:
include/linux/spinlock_rt.h: In function 'assert_spin_locked':
include/linux/spinlock_rt.h:161:2: error: implicit declaration of
function 'BUG_ON' [-Werror=implicit-function-declaration]
cc1: some warnings being treated as errors
A quick and dirt solution is to add the line:
#include <asm/bug.h>
just before the definition of the function:
static inline void assert_spin_locked(spinlock_t *lock)
in the file: include/linux/spinlock_rt.h
I assume that there is a missing include somewhere in the include path,
but I cannot find it so far. I hope this information helps.
Regards,
Iratxo.
--
Iratxo Pichel Ortiz
CTO
Albentia Systems S.A.
http://www.albentia.com
Mobile: +34 658588745
C\Margarita Salas 22
Parque Tecnológico de Leganés
Leganés (28918)
Madrid
Spain
--
To unsubscribe from this list: send the line "unsubscribe linux-rt-users" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next reply other threads:[~2012-06-20 18:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-20 17:57 Iratxo Pichel Ortiz [this message]
2012-06-21 6:25 ` Compilation fails leroy christophe
2012-06-21 12:47 ` 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=4FE20F1E.3010306@albentia.com \
--to=ipichel@albentia.com \
--cc=dgarcia@albentia.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 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.