From: Jim Freeman <jfree@sovereign.org>
To: linux-mips@oss.sgi.com, dhinds@zen.stanford.edu
Subject: mips vs pcmcia - which wins?
Date: Tue, 23 Jan 2001 09:35:23 -0700 [thread overview]
Message-ID: <20010123093523.B4972@sovereign.org> (raw)
The following mips kernel patchlet:
diff -u --new-file --recursive --exclude-from diff.exclude \
linux-2.4.0/include/linux/sched.h \
linux-mips.cvs/include/linux/sched.h
--- linux-2.4.0/include/linux/sched.h Thu Jan 4 15:50:47 2001
+++ linux-mips.cvs/include/linux/sched.h Wed Jan 10 21:52:59 2001
@@ -562,6 +562,8 @@
extern int in_group_p(gid_t);
extern int in_egroup_p(gid_t);
+extern void release(struct task_struct * p);
+
extern void proc_caches_init(void);
extern void flush_signals(struct task_struct *);
extern void flush_signal_handlers(struct task_struct *);
causes i386 builds to fail:
make -C pcmcia modules
make[5]: Entering directory `/autobuild/public_html/project/build/rpmdir/BUILD/linux/drivers/pcmcia'
...
cs.c:93: `release' redeclared as different kind of symbol
/autobuild/public_html/project/build/rpmdir/BUILD/linux/include/linux/sched.h:565: previous declaration of `release'
cs.c:93: warning: `release' was declared `extern' and later `static'
make[5]: *** [cs.o] Error 1
make[5]: Leaving directory `/autobuild/public_html/project/build/rpmdir/BUILD/linux/drivers/pcmcia'
make[4]: *** [_modsubdir_pcmcia] Error 2
with the following i386 config options:
...
CONFIG_HOTPLUG=y
#
# PCMCIA/CardBus support
#
CONFIG_PCMCIA=m
# CONFIG_CARDBUS is not set
# CONFIG_I82365 is not set
# CONFIG_TCIC is not set
...
...jfree
next reply other threads:[~2001-01-23 16:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-23 16:35 Jim Freeman [this message]
2001-01-23 17:07 ` mips vs pcmcia - which wins? Ralf Baechle
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=20010123093523.B4972@sovereign.org \
--to=jfree@sovereign.org \
--cc=dhinds@zen.stanford.edu \
--cc=linux-mips@oss.sgi.com \
/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