From: data <data@uniquemodem.com>
To: linux-mtd@lists.infradead.org
Subject: Problem on building the kernel 2.2.18 with MTD sc520 processor
Date: Thu, 11 Oct 2001 21:09:19 +0800 [thread overview]
Message-ID: <3BC599FF.9ECDA81C@uniquemodem.com> (raw)
Hi,
I would like to put the embedded linux into the sc520cdp processor
board. I follow the document The Linux MTD, JIFFS HOWTO to build the
kernel 2.2.18 with the patch MTD 2.2.18. During the compiling process, I
have encountered the following problem. Have anybody
come across similar problem before? If you do, could you please give me
a hand?
The followings are the installation log for the kernel when compiling
the driver MTD stuffs and I hope you can help me to sort out the
problem.
Thanks and regards,
Jimmy Chun
>Installation log:
>
>otypes -O2 -fomit-frame-pointer
-fno-strict-aliasing -pipe -fno-strength-ed
>uce
>-m386 -DCPU=386 -c -o chipreg.o chipreg.c
>chipreg.c: In function `do_map_probe':
>chipreg.c:67: parse error before `do'
>chipreg.c:63: warning: unused variable `ret'
>chipreg.c:69: warning: control reaches end of
non-void function
>chipreg.c: At top level:
>chipreg.c:73: warning: type defaults to `int'
in declaration of `ret'
>chipreg.c:73: `drv' undeclared here (not in a
function)
>chipreg.c:73: `map' undeclared here (not in a
function)
>chipreg.c:73: warning: data definition has no
type or storage class
>chipreg.c:84: parse error before `if'
>make[4]: *** [chipreg.o] Error 1
>make[4]: Leaving directory
>`/home/dlam/linux-v2.2/linux-2.2.18/drivers/mtd/chips
>'
>make[3]: *** [first_rule] Error 2
>make[3]: Leaving directory
>`/home/dlam/linux-v2.2/linux-2.2.18/drivers/mtd/chips
>'
>make[2]: *** [_subdir_chips] Error 2
>make[2]: Leaving directory
`/home/dlam/linux-v2.2/linux-2.2.18/drivers/mtd'
>make[1]: *** [_subdir_mtd] Error 2
>make[1]: Leaving directory
`/home/dlam/linux-v2.2/linux-2.2.18/drivers'
>make: *** [_dir_drivers] Error 2
reply other threads:[~2001-10-11 12: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=3BC599FF.9ECDA81C@uniquemodem.com \
--to=data@uniquemodem.com \
--cc=linux-mtd@lists.infradead.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