From: Russell King <rmk+lkml@arm.linux.org.uk>
To: Linus Torvalds <torvalds@osdl.org>
Cc: Ralf Baechle <ralf@linux-mips.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Alexey Dobriyan <adobriyan@gmail.com>
Subject: Re: Build breakage ...
Date: Sun, 26 Nov 2006 23:21:29 +0000 [thread overview]
Message-ID: <20061126232128.GC30767@flint.arm.linux.org.uk> (raw)
In-Reply-To: <Pine.LNX.4.64.0611261509330.3483@woody.osdl.org>
On Sun, Nov 26, 2006 at 03:12:54PM -0800, Linus Torvalds wrote:
>
>
> On Sun, 26 Nov 2006, Linus Torvalds wrote:
> >
> > Does the obvious fix (to include <linux/kernel.h> in irqflags.h) fix it
> > for you?
>
> Btw, Alexey, why did you do _both a BUILD_BUG_ON and a "typecheck()"?
>
> If there are any broken users, we shouldn't break the build, but a
> _warning_ is certainly appropriate.
>
> I think I'll just commit this..
>
> Ralf, Russell, does this work for you guys?
Not at all. It creates even more problems for me, with this circular
dependency:
linux/bitops.h -> asm-arm/bitops.h -> asm-arm/system.h
-> linux/irqflags.h -> linux/kernel.h -> linux/bitops.h
We really need, as a priority, to sort out these include files ASAP,
and stop bunging random stuff into unrelated random headers. Shouldn't
stuff like roundup_pow_of_two() and long_log2() live somewhere else
other than such a generic run-of-the-mill include such as linux/kernel.h ?
CHK include/linux/version.h
make[2]: `include/asm-arm/mach-types.h' is up to date.
Using /home/rmk/git/linux-2.6-rmk as source for kernel
GEN /home/rmk/git/build/assabet/Makefile
CHK include/linux/utsrelease.h
CC arch/arm/kernel/asm-offsets.s
In file included from /home/rmk/git/linux-2.6-rmk/include/linux/irqflags.h:14,
from include2/asm/system.h:214,
from include2/asm/bitops.h:23,
from /home/rmk/git/linux-2.6-rmk/include/linux/bitops.h:9,
from /home/rmk/git/linux-2.6-rmk/include/linux/thread_info.h:20,
from /home/rmk/git/linux-2.6-rmk/include/linux/preempt.h:9,
from /home/rmk/git/linux-2.6-rmk/include/linux/spinlock.h:49,
from /home/rmk/git/linux-2.6-rmk/include/linux/capability.h:45,
from /home/rmk/git/linux-2.6-rmk/include/linux/sched.h:46,
from /home/rmk/git/linux-2.6-rmk/arch/arm/kernel/asm-offsets.c:13:
/home/rmk/git/linux-2.6-rmk/include/linux/kernel.h: In function `roundup_pow_of_two':
/home/rmk/git/linux-2.6-rmk/include/linux/kernel.h:169: warning: implicit declaration of function `fls_long'
In file included from /home/rmk/git/linux-2.6-rmk/include/linux/thread_info.h:20,
from /home/rmk/git/linux-2.6-rmk/include/linux/preempt.h:9,
from /home/rmk/git/linux-2.6-rmk/include/linux/spinlock.h:49,
from /home/rmk/git/linux-2.6-rmk/include/linux/capability.h:45,
from /home/rmk/git/linux-2.6-rmk/include/linux/sched.h:46,
from /home/rmk/git/linux-2.6-rmk/arch/arm/kernel/asm-offsets.c:13:
/home/rmk/git/linux-2.6-rmk/include/linux/bitops.h: At top level:
/home/rmk/git/linux-2.6-rmk/include/linux/bitops.h:57: error: conflicting types for 'fls_long'
/home/rmk/git/linux-2.6-rmk/include/linux/kernel.h:169: error: previous implicit declaration of 'fls_long' was here
make[2]: *** [arch/arm/kernel/asm-offsets.s] Error 1
make[1]: *** [prepare0] Error 2
make: *** [_all] Error 2
--
Russell King
Linux kernel 2.6 ARM Linux - http://www.arm.linux.org.uk/
maintainer of:
next prev parent reply other threads:[~2006-11-26 23:21 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-26 22:49 Build breakage Ralf Baechle
2006-11-26 23:05 ` Russell King
2006-11-26 23:09 ` Russell King
2006-11-26 23:06 ` Linus Torvalds
2006-11-26 23:12 ` Linus Torvalds
2006-11-26 23:21 ` Russell King [this message]
2006-11-27 0:29 ` Linus Torvalds
2006-11-27 0:41 ` Russell King
2006-11-27 16:43 ` Ralf Baechle
2006-11-27 19:56 ` Alexey Dobriyan
2006-11-27 0:08 ` Ralf Baechle
2006-11-26 23:47 ` Kyle McMartin
2006-11-26 23:56 ` [PARISC] Fix incorrent type of flags in <asm/semaphore.h> Kyle McMartin
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=20061126232128.GC30767@flint.arm.linux.org.uk \
--to=rmk+lkml@arm.linux.org.uk \
--cc=adobriyan@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=ralf@linux-mips.org \
--cc=torvalds@osdl.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