9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: lucio@proxima.alt.za
To: 9fans@9fans.net
Subject: [9fans] Rune update may have broken compilations
Date: Fri,  3 May 2013 14:55:43 +0200	[thread overview]
Message-ID: <0f789fd77c70e167707867ed283172a9@proxima.alt.za> (raw)

...  or I may just be doing something inappropriate.  But right now, I
get:

	5c -FTVw runebase.c
	 f0 a4 8b
	 ae 20
	 f0 a2 a1
	 8a 20
	 f0 a2 a1
	 84 20
	 f0 a3 8f
	 95 20
	 f0 a5 89
	 89 20
	runebase.c:1255 illegal rune in string
	runebase.c:1255 illegal rune in string
	runebase.c:1352 illegal rune in string
	runebase.c:1352 illegal rune in string
	runebase.c:1353 illegal rune in string
	runebase.c:1353 illegal rune in string
	runebase.c:1354 illegal rune in string
	runebase.c:1354 illegal rune in string
	runebase.c:1358 illegal rune in string
	runebase.c:1358 illegal rune in string
	runebase.c:1359 illegal rune in string
	too many errors
	mk: 5c -FTVw runebase.c  : exit status=rc 137119: 5c 137121: error
	mk: for(i in 9sys ...  : exit status=rc 136165: rc 136939: mk 136941: error
	mk: date for (i ...  : exit status=rc 135760: rc 136100: mk 136164: error

when compiling libc, whether for the 386 or the arm.

I'd appreciate suggestions on how to get out of this trouble.  I've
already made sure both 8c and 5c match the versions in sources.

++L




             reply	other threads:[~2013-05-03 12:55 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-03 12:55 lucio [this message]
2013-05-03 13:30 ` David du Colombier
2013-05-03 13:33   ` erik quanstrom
2013-05-04 15:32   ` lucio
2013-05-03 13:43 ` erik quanstrom

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=0f789fd77c70e167707867ed283172a9@proxima.alt.za \
    --to=lucio@proxima.alt.za \
    --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).