From: Dominic Mason <dominic@opusvl.com>
To: buildroot@busybox.net
Subject: [Buildroot] ARCH=mips and linux-2.6.30.2
Date: Thu, 24 Sep 2009 17:27:06 +0100 [thread overview]
Message-ID: <1253809626.16645.27.camel@xd-02.opusvl.com> (raw)
Hi
Whilst building mips (mipsel) for an Alchemy AU1100 based system, I got
the following error whilst building the kernel:
CC arch/mips/lib/delay.o
arch/mips/lib/delay.c: In function '__udelay':
arch/mips/lib/delay.c:46: warning: right shift count >= width of type
arch/mips/lib/delay.c: In function '__ndelay':
arch/mips/lib/delay.c:54: error: 'us' undeclared (first use in this
function)
arch/mips/lib/delay.c:54: error: (Each undeclared identifier is reported
only once
arch/mips/lib/delay.c:54: error: for each function it appears in.)
make[1]: *** [arch/mips/lib/delay.o] Error 1
make: *** [arch/mips/lib] Error 2
This is using buildroot-2009-08 with kernel 2.6.30.2
For what it's worth, if you copy arch/mips/lib/delay.c
from a vanilla 2.6.30.4 kernel, then the error disappears.
However, the patch appears to have been missed from the 2.6.30.5 kernel,
where it re-appears.
The relevant lines in arch/mips/lib/delay.c should be:
__delay((us * 0x000010c7ull * HZ * lpj) >> 32);
and
__delay((ns * 0x00000005ull * HZ * lpj) >> 32);
which should replace
__delay((us * 0x000010c7 * HZ * lpj) >> 32);
and
__delay((us * 0x00000005 * HZ * lpj) >> 32);
Apologies for not being proficient enough to supply this as a patch.
It would appear that the above change exists in the vanilla linux-2.6.31
kernel from www.kernel.org
So this is really for information only, for anyone who gets this error
trying to compile a mips system using the 2.6.30.2 and 2.6.30.5 kernel.
--
Dominic Mason <dominic@opusvl.com>
Opus VL
next reply other threads:[~2009-09-24 16:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-24 16:27 Dominic Mason [this message]
2009-09-25 7:57 ` [Buildroot] ARCH=mips and linux-2.6.30.2 Peter Korsgaard
2009-09-25 16:41 ` Dominic Mason
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=1253809626.16645.27.camel@xd-02.opusvl.com \
--to=dominic@opusvl.com \
--cc=buildroot@busybox.net \
/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