From: Tsunehiko Baba <tsn@crl.hitachi.co.jp>
To: Alan Cox <laughing@shared-source.org>, linux-kernel@vger.kernel.org
Subject: [REPORT] (PPC) Compile Error (Linux 2.4.9-ac[12-16])
Date: Fri, 28 Sep 2001 10:07:54 +0900 [thread overview]
Message-ID: <ktn13gw2ad.wl@niagara.crl8.crl.hitachi.co.jp> (raw)
In-Reply-To: <20010927185107.A17861@lightning.swansea.linux.org.uk>
In-Reply-To: <20010927185107.A17861@lightning.swansea.linux.org.uk>
Hi, Alan and everyone.
I have continued testing Alan's ac-branch kernel but failed because of
following 2 problems.
1. include/asm-ppc/keyboard.h
It's a small problem ,easy to resolve.
If this patch is correct, please apply it.
[compile error Log]
In file included from keyboard.c:42:
/usr/src/v2.4.9/ac16/include/linux/vt_kern.h:35: parse error before `.'
keyboard.c:573: warning: excess elements in array initializer
keyboard.c:573: warning: (near initialization for `ret_diacr')
gmake[3]: *** [keyboard.o] エラー 1
gmake[2]: *** [first_rule] エラー 2
gmake[1]: *** [_subdir_char] エラー 2
gmake: *** [_dir_drivers] エラー 2
[patch]
*** include/asm-ppc/keyboard.h.orig Mon Sep 10 10:07:38 2001
--- include/asm-ppc/keyboard.h Mon Sep 10 10:07:51 2001
***************
*** 75,81 ****
ppc_md.kbd_init_hw();
}
- #define kbd_rate (ppc_md.kbd_rate_fn)
#define kbd_sysrq_xlate (ppc_md.ppc_kbd_sysrq_xlate)
extern unsigned long SYSRQ_KEY;
--- 75,80 ----
2. arch/ppc/kernel/setup.c
This error has occured since -ac12.
I tried to make patch but did't work well.
By comparing same files in each architectures, I think, in func
'get_cpuinfo' `n' is used in mistake for "i"....
Does anyone resolve this error, or advise me?
[compile error log]
setup.c: In function `get_cpuinfo':
setup.c:176: `n' undeclared (first use in this function)
setup.c:176: (Each undeclared identifier is reported only once
setup.c:176: for each function it appears in.)
setup.c:216: `c' undeclared (first use in this function)
setup.c:216: `cpu_data' undeclared (first use in this function)
setup.c:258: break statement not within loop or switch
setup.c:271: break statement not within loop or switch
setup.c:156: warning: unused variable `bogosum'
gmake[1]: *** [setup.o] エラー 1
gmake: *** [_dir_arch/ppc/kernel] エラー 2
Best Regards.
--
Tsunehiko Baba <tsn@crl.hitachi.co.jp>
next prev parent reply other threads:[~2001-09-28 1:13 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-27 17:51 Linux 2.4.9-ac16 Alan Cox
2001-09-27 18:26 ` Udo A. Steinberg
2001-09-27 18:28 ` Rik van Riel
2001-09-27 19:03 ` [PATCH] 2.4.9-ac16 swapoff 2*vfree Hugh Dickins
2001-09-27 19:36 ` Alexander Viro
2001-09-27 19:03 ` Linux 2.4.9-ac16 Tom Rini
2001-09-27 23:06 ` Alan Cox
2001-09-27 23:11 ` Tom Rini
2001-09-27 19:31 ` Kent Borg
2001-09-28 1:07 ` Tsunehiko Baba [this message]
2001-09-28 14:15 ` [REPORT] (PPC) Compile Error (Linux 2.4.9-ac[12-16]) Tom Rini
2001-09-28 14:40 ` Alan Cox
2001-09-28 14:41 ` Tom Rini
2001-09-28 5:21 ` [PATCH] link failur in Linux 2.4.9-ac16 around apm.o and sysrq.o junio
2001-09-28 5:47 ` junio
2001-09-28 15:41 ` Randy.Dunlap
2001-09-28 15:58 ` Crutcher Dunnavant
2001-09-28 15:30 ` Linux 2.4.9-ac16 Stefan Becker
2001-09-28 16:39 ` Rik van Riel
2001-09-28 17:15 ` Tim Connors
2001-09-28 20:52 ` Russell King
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=ktn13gw2ad.wl@niagara.crl8.crl.hitachi.co.jp \
--to=tsn@crl.hitachi.co.jp \
--cc=laughing@shared-source.org \
--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;
as well as URLs for NNTP newsgroup(s).