From: Latchesar Ionkov <lucho@ionkov.net>
To: lucio@proxima.alt.za,
Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] P9P on Lemote Yeeloong
Date: Wed, 13 May 2009 15:24:58 -0600 [thread overview]
Message-ID: <f158dc670905131424l2e99e551u8d9dc64021cb8b5e@mail.gmail.com> (raw)
In-Reply-To: <2b93b6bcf93d8d06edb6ac3a173ade68@proxima.alt.za>
The glibc on your notebook probably doesn't have getcontext
implemented. Google for "glibc mips getcontext".
Thanks,
Lucho
On Wed, May 13, 2009 at 1:57 PM, <lucio@proxima.alt.za> wrote:
> I thought things were running too smoothly. I got P9P to compile on
> the Lemote Yeeloong with only very frequent ocurrences of warnings
> (they seem like compile-time warnings) to the effect that each of
> getcontext, makecontext and swapcontext "is not implemented and will
> always fail".
>
> Now, the Yeeloong is a notebook based on a MIPS cpu and endowed with
> Open Architecture, Open BIOS (called PMON) and Linux (Debian). The
> man page for getcontext() seems to suggest that it exists, but
> executing, say, acme fails with:
>
> "threadalloc getcontext: function not implemented"
>
> So close to getting there, but I must be missing something. Does
> anyone know what?
>
> ++L
>
>
>
next prev parent reply other threads:[~2009-05-13 21:24 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-13 19:57 lucio
2009-05-13 20:28 ` Bakul Shah
2009-05-14 3:17 ` lucio
2009-05-13 21:24 ` Latchesar Ionkov [this message]
2009-05-14 3:38 ` lucio
2009-05-13 22:00 ` Russ Cox
2009-05-14 3:34 ` lucio
2009-05-14 10:03 ` Charles Forsyth
[not found] <3d5064d73b15cd2cbed06e132f419059@terzarima.net>
2009-05-14 18:29 ` lucio
2009-05-14 18:38 ` Steve Simon
2009-05-14 18:53 ` Eric Van Hensbergen
2009-05-14 19:06 ` Steve Simon
2009-05-14 19:33 ` lucio
2009-05-14 23:04 ` Charles Forsyth
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=f158dc670905131424l2e99e551u8d9dc64021cb8b5e@mail.gmail.com \
--to=lucho@ionkov.net \
--cc=9fans@9fans.net \
--cc=lucio@proxima.alt.za \
/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).