From: John Levon <movement@marcelothewonderpenguin.com>
To: linux-kernel@vger.kernel.org
Cc: smithmg@agere.com, kernelnewbies@nl.linux.org
Subject: Re: Unresolved symbol memset
Date: Wed, 5 Dec 2001 18:40:28 +0000 [thread overview]
Message-ID: <20011205184028.A82273@compsoc.man.ac.uk> (raw)
In-Reply-To: <009001c17db9$42aa18b0$4d129c87@agere.com>
In-Reply-To: <009001c17db9$42aa18b0$4d129c87@agere.com>
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.
You need to compile with optimisation turned on.
Btw, your question would be more appropriate on the kernelnewbies list - see
http://www.kernelnewbies.org/
regards
john
--
"Faced with the prospect of rereading this book, I would rather have
my brains ripped out by a plastic fork."
- Charles Cooper on "Business at the Speed of Thought"
next prev parent reply other threads:[~2001-12-05 18:40 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-05 18:18 Unresolved symbol memset Michael Smith
2001-12-05 18:26 ` rddunlap
2001-12-05 18:55 ` Michael Smith
2001-12-05 18:57 ` rddunlap
2001-12-05 19:16 ` Tommy Reynolds
2001-12-05 19:35 ` Michael Smith
2001-12-05 19:34 ` Charles Cazabon
2001-12-05 18:40 ` John Levon [this message]
2001-12-05 18:59 ` Michael Smith
2001-12-05 19:01 ` rddunlap
2001-12-05 19:09 ` Richard B. Johnson
2001-12-05 19:12 ` Michael Smith
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=20011205184028.A82273@compsoc.man.ac.uk \
--to=movement@marcelothewonderpenguin.com \
--cc=kernelnewbies@nl.linux.org \
--cc=linux-kernel@vger.kernel.org \
--cc=smithmg@agere.com \
/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