From: Shaya Potter <spotter@cs.columbia.edu>
To: "Randy.Dunlap" <rddunlap@osdl.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: using memset in a module
Date: 26 Sep 2002 19:02:26 -0400 [thread overview]
Message-ID: <1033081345.3371.35.camel@zaphod> (raw)
In-Reply-To: <Pine.LNX.4.33L2.0209261550410.32681-100000@dragon.pdx.osdl.net>
On Thu, 2002-09-26 at 18:51, Randy.Dunlap wrote:
> On 26 Sep 2002, Shaya Potter wrote:
>
> | I have a problem using memset in a module.
> |
> | I've tried including <linux/string.h> or <asm/string.h> but whenever I
> | compile with gcc 2.95, the resulting object has memset being an
> | undefined symbol. When I compile with gcc-3.2 it works right as is
> | inline in the code and there's no symbol.
> |
> | has anyone seen this b4? Is this a gcc bug? a kernel header bug? a bug
> | in my coding (i.e. does one have to do anything else besides include
> | <linux or asm/string.h> or have special gcc cmd line options that are
> | different from whats normally needed for a module).
> |
> | if it matters, I'm using the debian gcc's
> |
> | spotter@zaphod:~/cvs/zap/virtualization$ gcc -v
> | Reading specs from /usr/lib/gcc-lib/i386-linux/2.95.4/specs
> | gcc version 2.95.4 20011002 (Debian prerelease)
> |
> | and (cutting the cruft)
> | gcc version 3.2.1 20020924 (Debian prerelease)
>
> What gcc options are you using?
> You need -O2 at least.
> ^ upper-case letter O
yes, using it.
gcc -Wall -DMODULE -DMODVERSIONS -D__KERNEL__ -DLINUX -DEXPORT_SYMTAB
-I/usr/src/linux/include/ -I`pwd`/../migration
-I`pwd`/..//virtualization -O2 -fomit-frame-pointer -pipe
-fno-strength-reduce -malign-loops=2 -malign-jumps=2 -malign-functions=2
-o fs1.o -c virtualizers/fs1.c
next prev parent reply other threads:[~2002-09-26 22:57 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-26 22:49 using memset in a module Shaya Potter
2002-09-26 22:49 ` David S. Miller
2002-09-26 22:58 ` Shaya Potter
2002-09-26 22:51 ` Randy.Dunlap
2002-09-26 23:02 ` Shaya Potter [this message]
2002-09-27 15:20 ` Dan Aloni
2002-09-27 16:59 ` Shaya Potter
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=1033081345.3371.35.camel@zaphod \
--to=spotter@cs.columbia.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=rddunlap@osdl.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;
as well as URLs for NNTP newsgroup(s).