From: "Richard B. Johnson" <root@chaos.analogic.com>
To: Bart Samwel <bart@samwel.tk>
Cc: Ashish sddf <buff_boulder@yahoo.com>, linux-kernel@vger.kernel.org
Subject: Re: Compiling C++ kernel module + Makefile
Date: Mon, 19 Jan 2004 08:46:54 -0500 (EST) [thread overview]
Message-ID: <Pine.LNX.4.53.0401190839310.6496@chaos> (raw)
In-Reply-To: <200401171359.20381.bart@samwel.tk>
On Sat, 17 Jan 2004, Bart Samwel wrote:
> On Friday 16 January 2004 23:07, Richard B. Johnson wrote:
> > If somebody actually got a module, written in C++, to compile and
> > work on linux-2.4.nn, as you state, it works only by fiat, i.e., was
> > declared to work. There is no C++ runtime support in the kernel for
> > C++. Are you sure this is a module and not an application? Many
> > network processes (daemons) are applications and they don't require
> > any knowledge of kernel internals except what's provided by the
> > normal C/C++ include-files.
>
> Rest assured, ;) this is definitely a module. It includes a kernel patch that
> makes it possible to include a lot of the kernel headers into C++, stuff like
> changing asm :: to asm : : (note the space, :: is an operator in C++) and
> renaming "struct namespace" to something containing less C++ keywords. The
> module also includes rudimentary C++ runtime support code, so that the C++
> code will run inside the kernel. I'm afraid that the task of compiling it for
> 2.6 is going to be pretty tough -- the kernel needs loads of patches to make
> it work within a C++ extern "C" clause, and it probably completely different
> patches from those needed by 2.4. Getting the build system to work is the
> least of the concerns.
>
> -- Bart
>
I can't imagine why anybody would even attempt to write a kernel
module in C++. Next thing it'll be Visual BASIC, then Java. The
kernel is written in C and assembly. The tools are provided. It
can only be arrogance because this whole C v.s. C++ thing was
hashed-over many times. Somebody apparently wrote something to
"prove" that it can be done. I'd suggest that you spend some
time converting it to C if you need that "module". The conversion
will surely take less time than going through the kernel headers
looking for "::".
Cheers,
Dick Johnson
Penguin : Linux version 2.4.24 on an i686 machine (797.90 BogoMips).
Note 96.31% of all statistics are fiction.
next prev parent reply other threads:[~2004-01-19 13:45 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-16 21:09 Ashish sddf
2004-01-16 22:07 ` Richard B. Johnson
2004-01-17 12:59 ` Bart Samwel
2004-01-19 13:46 ` Richard B. Johnson [this message]
2004-01-19 17:40 ` Bart Samwel
2004-01-19 18:39 ` Richard B. Johnson
2004-01-19 20:02 ` Bart Samwel
2004-01-19 20:37 ` Richard B. Johnson
2004-01-19 21:24 ` Bart Samwel
2004-01-20 15:20 ` Richard B. Johnson
2004-01-20 17:34 ` Zan Lynx
2004-01-20 18:10 ` Richard B. Johnson
2004-01-20 13:38 ` Thomas Lahoda
2004-01-21 2:24 ` Michael Clark
2004-01-20 18:16 ` Chris Friesen
2004-01-21 17:01 ` Giuliano Pochini
2004-01-21 17:16 ` Bart Samwel
2004-01-20 0:59 ` Robin Rosenberg
2004-01-20 6:46 ` Linus Torvalds
2004-01-20 7:32 ` Robin Rosenberg
2004-01-20 10:46 ` Bart Samwel
2004-01-20 5:29 ` Valdis.Kletnieks
2004-01-20 9:48 ` Bart Samwel
2004-01-16 22:40 ` Sam Ravnborg
2004-01-19 13:21 Petr Vandrovec
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=Pine.LNX.4.53.0401190839310.6496@chaos \
--to=root@chaos.analogic.com \
--cc=bart@samwel.tk \
--cc=buff_boulder@yahoo.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
all inboxes | Powered by JetHome®