From: Keith Owens <kaos@ocs.com.au>
To: "Miller, Brendan" <Brendan.Miller@dialogic.com>
Cc: "'linux-kernel@vger.kernel.org'" <linux-kernel@vger.kernel.org>
Subject: Re: smp_num_cpus redefined? (compiling 2.2.18 for non-SMP?)
Date: Tue, 06 Feb 2001 17:39:05 +1100 [thread overview]
Message-ID: <1306.981441545@kao2.melbourne.sgi.com> (raw)
In-Reply-To: Your message of "Mon, 05 Feb 2001 19:06:58 CDT." <EFC879D09684D211B9C20060972035B1D4686C@exchange2ca.sv.dialogic.com>
On Mon, 5 Feb 2001 19:06:58 -0500 ,
"Miller, Brendan" <Brendan.Miller@Dialogic.com> wrote:
>I have a problem that would have started out as "I can't compile my device
>driver with 2.2.18". I was compiling my device driver for non-SMP while my
>kernel (and thus /usr/src/linux) was SMP. So I looked at compiling the
>kernel for non-SMP so that my /usr/src/linux would be non-SMP and my device
>driver would match. Well, now just compiling 2.2.18 for non-SMP, I get
>
>In file included from /usr/src/linux-2.2.18/include/linux/modversions.h:16,
> from /usr/src/linux-2.2.18/include/linux/module.h:19,
> from ksyms.c:14:
>/usr/src/linux-2.2.18/include/linux/modules/i386_ksyms.ver:64: warning:
>`cpu_data' redefined
http://www.tux.org/lkml/#s8-8
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2001-02-06 6:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-06 0:06 smp_num_cpus redefined? (compiling 2.2.18 for non-SMP?) Miller, Brendan
2001-02-06 6:39 ` Keith Owens [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-02-06 23:52 Juraj Bednar
2001-02-06 23:59 ` J . A . Magallon
2001-02-07 0:17 Juraj Bednar
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=1306.981441545@kao2.melbourne.sgi.com \
--to=kaos@ocs.com.au \
--cc=Brendan.Miller@dialogic.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