From mboxrd@z Thu Jan  1 00:00:00 1970
Message-ID: <0f789fd77c70e167707867ed283172a9@proxima.alt.za>
To: 9fans@9fans.net
Date: Fri,  3 May 2013 14:55:43 +0200
From: lucio@proxima.alt.za
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Subject: [9fans] Rune update may have broken compilations
Topicbox-Message-UUID: 52b8913c-ead8-11e9-9d60-3106f5b1d025

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