From: Egan <tony.egan@timesys.com>
To: linux-kernel@vger.kernel.org
Cc: tony.egan@timesys.com
Subject: 2.6.14-rt21 doesn't build for ppc
Date: Tue, 29 Nov 2005 11:57:55 -0500 [thread overview]
Message-ID: <17292.34963.717045.706135@santa.timesys.com> (raw)
2.6.14 with RT21 fails to build for ppc (ibm440gx).
CC kernel/timer.o
/home/egan/downloads/linux-2.6.14/kernel/timer.c: In function `phase_advance':
/home/egan/downloads/linux-2.6.14/kernel/timer.c:991: error: `time_phase' undeclared (first use in this function)
/home/egan/downloads/linux-2.6.14/kernel/timer.c:991: error: (Each undeclared identifier is reported only once
/home/egan/downloads/linux-2.6.14/kernel/timer.c:991: error: for each function it appears in.)
/home/egan/downloads/linux-2.6.14/kernel/timer.c:994: warning: type defaults to `int' in declaration of `__x'
/home/egan/downloads/linux-2.6.14/kernel/timer.c: In function `update_wall_time':
/home/egan/downloads/linux-2.6.14/kernel/timer.c:1050: error: too few arguments to function `phase_advance'
/home/egan/downloads/linux-2.6.14/kernel/timer.c:1040: warning: unused variable `time_phase'
make[2]: *** [kernel/timer.o] Error 1
make[1]: *** [kernel] Error 2
make: *** [zImage] Error 2
Adding config GENERIC_TIME to arch/ppc/Kconfig results in a failure later in
the build.
CC kernel/time/clockevents.o
/home/egan/downloads/linux-2.6.14/kernel/time/clockevents.c:80: error: conflicting types for 'timer_interrupt'
include2/asm/hw_irq.h:12: error: previous declaration of 'timer_interrupt' was here
/home/egan/downloads/linux-2.6.14/kernel/time/clockevents.c:80: error: conflicting types for 'timer_interrupt'
include2/asm/hw_irq.h:12: error: previous declaration of 'timer_interrupt' was here
/home/egan/downloads/linux-2.6.14/kernel/time/clockevents.c: In function `handle_tick_update_profile':
/home/egan/downloads/linux-2.6.14/kernel/time/clockevents.c:126: warning: implicit declaration of function `profile_tick'
/home/egan/downloads/linux-2.6.14/kernel/time/clockevents.c:126: error: `CPU_PROFILING' undeclared (first use in this function)
/home/egan/downloads/linux-2.6.14/kernel/time/clockevents.c:126: error: (Each undeclared identifier is reported only once
/home/egan/downloads/linux-2.6.14/kernel/time/clockevents.c:126: error: for each function it appears in.)
/home/egan/downloads/linux-2.6.14/kernel/time/clockevents.c: In function `handle_update_profile':
/home/egan/downloads/linux-2.6.14/kernel/time/clockevents.c:143: error: `CPU_PROFILING' undeclared (first use in this function)
/home/egan/downloads/linux-2.6.14/kernel/time/clockevents.c: In function `handle_profile':
/home/egan/downloads/linux-2.6.14/kernel/time/clockevents.c:151: error: `CPU_PROFILING' undeclared (first use in this function)
/home/egan/downloads/linux-2.6.14/kernel/time/clockevents.c: In function `setup_event':
/home/egan/downloads/linux-2.6.14/kernel/time/clockevents.c:326: error: `SA_NODELAY' undeclared (first use in this function)
/home/egan/downloads/linux-2.6.14/kernel/time/clockevents.c:329: warning: implicit declaration of function `setup_irq'
make[3]: *** [kernel/time/clockevents.o] Error 1
make[2]: *** [kernel/time] Error 2
make[1]: *** [kernel] Error 2
make: *** [zImage] Error 2
After some research it looks like this breakage was introduced by rt16.
rt15 builds OK.
Please retain my CC in any replies.
Thanks,
Tony
reply other threads:[~2005-11-29 16:57 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=17292.34963.717045.706135@santa.timesys.com \
--to=tony.egan@timesys.com \
--cc=linux-kernel@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
all inboxes | Powered by JetHome®