From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Xen and new venti
Date: Tue, 4 Mar 2008 17:26:17 -0500 [thread overview]
Message-ID: <9e9e76dca260174c8be4d9c2d6c1cd00@quanstro.net> (raw)
In-Reply-To: <25c2223b56be202f15da4a4198616442@hamnavoe.com>
> I can't see why this should have been necessary - libc contains memcpy
> already. I have just updated /n/sources/xen/xen3 so it compiles with
> the current Plan 9 kernel source (using Xen 3.0.2). I made the other
> changes you listed, but I didn't have to do anything about memcpy.
the reason it's necessary is that although the kernel links against the
c library, it does not include libc.h. this is very much on purpose as
not every function in libc is safe for use in the kernel.
in this case, the definition for memcpy was likely not picked up in
portfns.h so the linker couldn't find the proper function.
- erik
next prev parent reply other threads:[~2008-03-04 22:26 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-03 23:15 stella
2008-03-04 0:52 ` erik quanstrom
2008-03-04 21:38 ` stella
2008-03-04 22:18 ` Richard Miller
2008-03-04 22:26 ` erik quanstrom [this message]
2008-03-05 0:18 stella
2008-03-05 0:37 ` erik quanstrom
2008-03-05 8:10 ` stella
2008-03-08 20:11 Richard Miller
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=9e9e76dca260174c8be4d9c2d6c1cd00@quanstro.net \
--to=quanstro@quanstro.net \
--cc=9fans@cse.psu.edu \
/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).