9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Don Bailey <don.bailey@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: [9fans] runebase.c illegal rune in string
Date: Tue, 29 Aug 2023 21:22:17 -0400	[thread overview]
Message-ID: <CAL_X0tACdGE72ErMhLjoyHjKJckF=7U-qyJqMBb+VxWj7pZeRg@mail.gmail.com> (raw)

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

Hi All,

When attempting to build an ARM binary, I am getting an error in
libc/port/runebase.c on several lines (such as 1255). The error is "illegal
rune in string". Can anyone tell me how to patch this? If I "pull" from
this plan9 image, nothing updates, even after changing the sources to 9p.io

Thank you,

9fans: 9fans
Permalink: https://9fans.topicbox.com/groups/9fans/T364342ae6137187d-Ma7b09b4f6a5e136f1967c0b4
Delivery options: https://9fans.topicbox.com/groups/9fans/subscription

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

             reply	other threads:[~2023-08-30  1:22 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-30  1:22 Don Bailey [this message]
2023-08-30  2:35 ` [9fans] " Don Bailey

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAL_X0tACdGE72ErMhLjoyHjKJckF=7U-qyJqMBb+VxWj7pZeRg@mail.gmail.com' \
    --to=don.bailey@gmail.com \
    --cc=9fans@9fans.net \


* 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).