From: Kaoru Fukui <k_fukui@highway.ne.jp>
To: MATSUURA Takanori <t-matsuu@protein.osaka-u.ac.jp>
Cc: linuxppc-dev@lists.linuxppc.org
Subject: Re: 2.4.10-pre12 sysrq.c compile error
Date: Thu, 20 Sep 2001 20:13:30 +0900 [thread overview]
Message-ID: <20010920201330.Postino-024975@smtp01.highway.ne.jp> (raw)
In-Reply-To: <20010920.201024.730567552.t-matsuu@protein.osaka-u.ac.jp>
From: MATSUURA Takanori <t-matsuu@protein.osaka-u.ac.jp>
To: linuxppc-dev@lists.linuxppc.org
> > of `wakeup_bdflush'
> > make[3]: *** [sysrq.o] Error 1
> > make[3]: Leaving directory `/usr/src/linuxppc_2_4/drivers/char'
> > make[2]: *** [first_rule] Error 2
> > make[2]: Leaving directory `/usr/src/linuxppc_2_4/drivers/char'
> > make[1]: *** [_subdir_char] Error 2
> > make[1]: Leaving directory `/usr/src/linuxppc_2_4/drivers'
> > make: *** [_dir_drivers] Error 2
>
> `wakeup_bdflush' was defines in two defrent files.
>
> linuxppc_2_4_devel/drivers/char/sysrq.c (line: 35)
> extern void wakeup_bdflush(int);
>
> linuxppc_2_4_devel/include/linux/fs.h (line: 1347)
> extern void wakeup_bdflush(void);
>
if it's same extern , it's no problem.
Different paramenter is no good.
Kaoru
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2001-09-20 11:13 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200109200500.AAA17467@lists.linuxppc.org>
2001-09-20 11:10 ` 2.4.10-pre12 sysrq.c compile error MATSUURA Takanori
2001-09-20 11:13 ` Kaoru Fukui [this message]
2001-09-20 14:52 ` Stefan Jeglinski
2001-09-20 15:09 ` Stefan Jeglinski
2001-09-20 15:19 ` Kaoru Fukui
2001-09-20 15:26 ` Kaoru Fukui
2001-09-21 2:26 ` 2.4.10-pre12 sysrq.c compile error (solved) Stefan Jeglinski
2001-09-19 21:34 2.4.10-pre12 sysrq.c compile error Stefan Jeglinski
2001-09-19 21:58 ` Mike Fedyk
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=20010920201330.Postino-024975@smtp01.highway.ne.jp \
--to=k_fukui@highway.ne.jp \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=t-matsuu@protein.osaka-u.ac.jp \
/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).