RE: Unresolved symbol memset

rddunlap@osdl.org
Wed, 5 Dec 2001 11:01:02 -0800 (PST)


On Wed, 5 Dec 2001, Michael Smith wrote:

| I have optimization turned. Using -02 in the makefile.

That's a capital (upper case) 'O', not a zero (0).

And you should be #include-ing <linux/string.h>, _not_ <string.h>.

~Randy

| I am new to the linux kernel but not kernel development. If you still
| think this is the wrong list, I will post on the other one. Sorry if it
| is the wrong list
|
|
| -----Original Message-----
| From: linux-kernel-owner@vger.kernel.org
| [mailto:linux-kernel-owner@vger.kernel.org] On Behalf Of John Levon
| Sent: Wednesday, December 05, 2001 1:40 PM
| To: linux-kernel@vger.kernel.org
| Cc: smithmg@agere.com; kernelnewbies@nl.linux.org
| Subject: Re: Unresolved symbol memset
|
| On Wed, Dec 05, 2001 at 01:18:37PM -0500, Michael Smith wrote:
|
| > Hello all,
| > I am new the Linux world and have a problem which is somewhat
| > confusing. I am using the system call memset() in kernel code written
| > for Red Hat 7.1(kernel 2.4). I needed to make this code compatible
| with
| > Red Hat 6.2(kernel 2.2) and seem to be getting a unresolved symbol.
| > This is only happening in one place of the code in one file. I am
| using
| > memset() in other areas of the code which does not lead to the
| problem.

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/