[9fans] Rune update may have broken compilations

[9fans] Rune update may have broken compilations

[lucio]

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

Re: [9fans] Rune update may have broken compilations

[David du Colombier]

The procedure is:

1. remove runebase from /sys/src/libc/port/mkfile
2. cd /sys/src/libc && mk install && mk clean
3. for(i in /sys/src/cmd/8?) {cd $i && mk install && mk clean}
4. add runebase in /sys/src/libc/port/mkfile
5. cd /sys/src/libc && mk install && mk clean
6. cd /sys/src && mk install && mk clean

--
David du Colombier

Re: [9fans] Rune update may have broken compilations

[erik quanstrom]

On Fri May  3 09:31:11 EDT 2013, 0intro@gmail.com wrote:
> The procedure is:
>
> 1. remove runebase from /sys/src/libc/port/mkfile
> 2. cd /sys/src/libc && mk install && mk clean
> 3. for(i in /sys/src/cmd/8?) {cd $i && mk install && mk clean}
> 4. add runebase in /sys/src/libc/port/mkfile
> 5. cd /sys/src/libc && mk install && mk clean
> 6. cd /sys/src && mk install && mk clean

alternately, download /n/atom/plan9/$objtype/bin/$O^c
and goto step 6.

- erik

Re: [9fans] Rune update may have broken compilations

[lucio]

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

Successful for both 386 and arm, thank you, but on condition that
existing object libraries (lib*.a8 and lib*.a5) in the source
directories be removed first.

++L

[-- Attachment #2: Type: message/rfc822, Size: 4565 bytes --]

From: David du Colombier <0intro@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] Rune update may have broken compilations
Date: Fri, 3 May 2013 15:30:14 +0200
Message-ID: <CANUoZoG36_jCoFcVbt3TkN6x4T8Upw2t9rTXw-Gf1x3Cm7kdLw@mail.gmail.com>

The procedure is:

1. remove runebase from /sys/src/libc/port/mkfile
2. cd /sys/src/libc && mk install && mk clean
3. for(i in /sys/src/cmd/8?) {cd $i && mk install && mk clean}
4. add runebase in /sys/src/libc/port/mkfile
5. cd /sys/src/libc && mk install && mk clean
6. cd /sys/src && mk install && mk clean

--
David du Colombier

Re: [9fans] Rune update may have broken compilations

[erik quanstrom]

On Fri May  3 08:56:58 EDT 2013, lucio@proxima.alt.za wrote:
> ...  or I may just be doing something inappropriate.  But right now, I
> get:
>
> 	5c -FTVw runebase.c

one thing not in the sources version of 21-bit runes is the
ability to regenerate the rune tables automaticly from the
official UnicodeData.txt.

the scripts in /n/atom/plan9/sys/src/cmd/runetype give one
that ability.  since i had this same issue during conversion,
the scripts omit characters biggern than Maxrune.

these scripts made the conversions from 5.2 to 6.0 and
from 6.0 to 6.1 a matter of typing "mk".

- erik