From: arisawa <arisawa@ar.aichi-u.ac.jp>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] 9vx on mountain lion
Date: Mon, 18 Feb 2013 07:57:53 +0900 [thread overview]
Message-ID: <0581E9F6-DC9E-44B5-B3EF-9CB6DECC49A3@ar.aichi-u.ac.jp> (raw)
In-Reply-To: <46365372-1F4F-46C5-9F28-A5E186DA586F@gmail.com>
Thank you, Ярослав.
I installed the patch: rminnich-vx32-17a064eed9c2
However,
-bash$ gnumake
....
9vx/osx/screen.c: In function ‘setcursor’:
9vx/osx/screen.c:547: error: ‘OSXCursor’ undeclared (first use in this function)
9vx/osx/screen.c:547: error: (Each undeclared identifier is reported only once
9vx/osx/screen.c:547: error: for each function it appears in.)
9vx/osx/screen.c:547: error: expected ‘;’ before ‘oc’
9vx/osx/screen.c:552: error: ‘oc’ undeclared (first use in this function)
9vx/osx/screen.c:557: warning: implicit declaration of function ‘SetCursor’
gnumake: *** [9vx/osx/screen.o] Error 1
rm 9vx/factotum.S 9vx/kfs.S 9vx/bzfs.S 9vx/boot.S 9vx/rootfs.S 9vx/venti.S 9vx/fossil.S 9vx/9660srv.S
-bash$
anyone fixed this problem?
Kenji Arisawa
On 2013/02/17, at 17:08, Ярослав Коломієць <yarikos@gmail.com> wrote:
> Try to compile from https://bitbucket.org/rminnich/vx32
>
>> Hello 9fans,
>>
>> my 9vx that was in 9vx-0.12 does not work on mountain lion.
>> that leads to panic with a message:
>>
>> -bash$ 9vx.OSX
>> 71 rio fault 0x8 no segment
>>
>> anyone has newer version or patch?
>>
>> Kenji Arisawa
>>
>>
next prev parent reply other threads:[~2013-02-17 22:57 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-17 6:58 arisawa
2013-02-17 8:08 ` Ярослав Коломієць
2013-02-17 22:57 ` arisawa [this message]
2013-02-17 23:09 ` Benjamin Huntsman
2013-02-18 1:04 ` Jeff Sickel
2013-02-18 7:59 ` arisawa
2013-02-18 10:10 ` lucio
2013-02-18 12:24 ` David du Colombier
2013-02-18 12:51 ` lucio
2013-02-18 16:22 ` Jeff Sickel
2013-02-18 23:38 ` arisawa
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=0581E9F6-DC9E-44B5-B3EF-9CB6DECC49A3@ar.aichi-u.ac.jp \
--to=arisawa@ar.aichi-u.ac.jp \
--cc=9fans@9fans.net \
/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).