From: Shanti Katta <katta@csee.wvu.edu>
To: linux-kernel@vger.kernel.org
Cc: sparclinux@vger.kernel.org
Subject: Sparc memory manipulation functions in 2.4.18
Date: 13 Oct 2002 15:58:07 -0400 [thread overview]
Message-ID: <1034539088.16630.20.camel@indus> (raw)
While trying to compile user-mode-linux-2.4.18-22 on Ultra Sparc using
gcc-3.2, I get undefined references to __builtin_memcpy,
__builtin_memset, __memcpy, __memset. I guess implementations to those
functions should be provided by gcc itself. Any ideas on what might be
wrong here?
-Shanti
reply other threads:[~2002-10-13 19:40 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1034539088.16630.20.camel@indus \
--to=katta@csee.wvu.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=sparclinux@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.