9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Anant Narayanan <anant@kix.in>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] Kabini or Raspberry Pi?
Date: Wed,  2 Jul 2014 23:15:06 -0700	[thread overview]
Message-ID: <CA+MHcSrN=8JrkFOXdxWmTqAYT1rWxxxa0aqgqwd59GbHHew1Ow@mail.gmail.com> (raw)
In-Reply-To: <e62cafaec3c7242092d5137a43797d83@eonet.ne.jp>

[-- Attachment #1: Type: text/plain, Size: 1108 bytes --]

I found an old thread with a series of steps that called for building the
compilers without runebase first then bringing runebase back into libc
after (https://groups.google.com/forum/#!topic/comp.os.plan9/rjFtp4F82U0) -
the steps didn't work for me though.

What did work was using 5c from /n/9atom (
http://comments.gmane.org/gmane.os.plan9.general/68992)!

-Anant


On Tue, Jul 1, 2014 at 12:37 PM, <kokamoto@hera.eonet.ne.jp> wrote:

> Thanks all.
> I made order the A68N-5000 board yesterday.
> I may have many difficulties to run Plan 9, (UEFI etc),
> in such case I'll run windows on it.☺
>
> By the way, I got attention to arm architecture now.
> I tried to compile raspberry pi on my plan9 machine, and
> got problem.
>
> When to compile runebase.c in the port of libc, I got
> runebase.c: 1255 illegal rune in string, where
> the line is:
>         0xfa6c, 0x242ee,        /* 𤋮 𤋮 */.
>
> Of course ther are many similar error lines, where
> all the line have 5 digit value such as '0x242ee'.
> Is there any limitations arm rune definition?
>
> Kenji
>
>
>

[-- Attachment #2: Type: text/html, Size: 1655 bytes --]

  reply	other threads:[~2014-07-03  6:15 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-01 19:37 kokamoto
2014-07-03  6:15 ` Anant Narayanan [this message]
2014-07-03  6:17   ` erik quanstrom
2014-07-04  2:10     ` kokamoto
2014-07-03  6:16 ` erik quanstrom
2014-07-03  8:16   ` kokamoto
2014-07-03 19:31     ` erik quanstrom
2014-07-04  7:56     ` kokamoto
2014-07-04  8:20       ` fgergo
  -- strict thread matches above, loose matches on Subject: below --
2014-07-01 19:37 Richard Miller
2014-07-01 19:52 ` Skip Tavakkolian
2014-07-01 20:07   ` sl
2014-07-01 20:26     ` Skip Tavakkolian
2014-07-01 21:39     ` Charles Forsyth
2014-07-01 21:46       ` sl
2014-07-01 22:03       ` Skip Tavakkolian
2014-07-01  7:58 Richard Miller
2014-07-01 12:52 ` hiro
2014-07-01 12:54   ` hiro
2014-07-01  0:28 kokamoto
2014-07-01  0:39 ` Shane Morris
2014-07-01  0:40   ` Shane Morris

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='CA+MHcSrN=8JrkFOXdxWmTqAYT1rWxxxa0aqgqwd59GbHHew1Ow@mail.gmail.com' \
    --to=anant@kix.in \
    --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).