From: William Josephson <jkw@eecs.harvard.edu>
To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: Re: [9fans] plan9port, NetBSD, sched_yield
Date: Sun, 13 Jun 2004 23:19:29 -0400 [thread overview]
Message-ID: <20040614031929.GA26824@mero.morphisms.net> (raw)
In-Reply-To: <40CD0C63.nailE951M55XK@insolvencyhelp.org>
On Sun, Jun 13, 2004 at 10:24:35PM -0400, Thomas Miller wrote:
> NetBSD aluminum.miller.net 2.0E NetBSD 2.0E (GENERIC) #0:
>
> Would someone please tell me how to fix this error?
Do a NetBSD port :-) I don't think anyone has bothered
to do a NetBSD port since I stopped using NetBSD and that
was several years ago when the Plan 9 port stuff was in
a different (and much less complete) state. Sched_yield
is in libpthread under NetBSD, but I very much doubt that
just linking against is sufficient; it may make the link
error go away, however. If I have time later in the week
I can look into doing a port, but I don't have a NetBSD
box here physically, so I can't test anything that uses
X11.
next prev parent reply other threads:[~2004-06-14 3:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-14 2:24 Thomas Miller
2004-06-14 3:19 ` William Josephson [this message]
2004-06-14 3:14 ` Thomas 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=20040614031929.GA26824@mero.morphisms.net \
--to=jkw@eecs.harvard.edu \
--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).