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 16:59:43 +0900 [thread overview]
Message-ID: <BAC29F61-B873-4B4E-8468-E554B708183A@ar.aichi-u.ac.jp> (raw)
In-Reply-To: <5587B7FE-6F51-4612-88EF-475F4A9525C2@corpus-callosum.com>
Hello,
Thanks for the information.
it was bothersome to apply cocoa-screen.m in p9p to screen.c in vx32.
The problem comes from the function setcursor() in screen.c.
so, for the temporally, I made the function dummy.
it seems the compiled 9vx is stable without serious problems.
remaining problems are:
(a) cursor shape keeps same as that of Mac
(b) initial back ground color is white. that should be dark grey.
both are bearable for me.
thanks for all.
Kenji Arisawa
On 2013/02/18, at 10:04, Jeff Sickel <jas@corpus-callosum.com> wrote:
> It's the long ago announced (over five years ago) and finally enacted removal of Carbon APIs that are biting you. At some point someone can pull in the changes from darwin-cocoa or recent p9p devdraw/cocoa-screen.m to get 9vx to build and run on OSX 10.8+.
>
> -jas
>
>
>
> On Feb 17, 2013, at 5:09 PM, Benjamin Huntsman <BHuntsman@mail2.cu-portland.edu> wrote:
>
>> Nice... I was just getting that same error a few days ago when I tried to build it too.
>> I chalked it up to some earlier posts that said something along the lines of "use a binary from Snow Leopard"... and didn't want to ask around to see if it's been fixed.
>>
>> Glad to see I'm not alone...
>>
>> -Ben
>>
>
>
next prev parent reply other threads:[~2013-02-18 7:59 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
2013-02-17 23:09 ` Benjamin Huntsman
2013-02-18 1:04 ` Jeff Sickel
2013-02-18 7:59 ` arisawa [this message]
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=BAC29F61-B873-4B4E-8468-E554B708183A@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).