#include <memory.h>
#include <string.h>
#include "myownheaders.h"
void myfunction( void *a, int len )
{
....
Mymemmove() //used because NdisMoveMemory can not be used
memset( &a->WORD[NUMWORDS-len], 0, len*4);
...
}
-----Original Message-----
From: linux-kernel-owner@vger.kernel.org
[mailto:linux-kernel-owner@vger.kernel.org] On Behalf Of
rddunlap@osdl.org
Sent: Wednesday, December 05, 2001 1:27 PM
To: Michael Smith
Cc: linux-kernel@vger.kernel.org
Subject: Re: Unresolved symbol memset
On Wed, 5 Dec 2001, 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.
| If anyone can clue me in to what this possible can be, it would
greatly
| be appreciated.
um, memset() isn't actually a system call.
However-- does the problem source file have
#include <linux/string.h>
in it? It should.
Or perhaps you could post the problem source file and/or
gcc messages.
-- ~Randy- 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/
- 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/