We just have a botched build with a broken systab.h.
Sounds like it should be removed on mk clean as it is generated
(Though it rarely should be regenerated :-\ )


Notes:
Mon Aug 22 07:04:42 EDT 2005 rsc
    I'd rather not do this, because then if you are
    running mk install; mk clean in different subdirectories
    simultaneously, the clean in one could remove systab.h
    before the other is done with it (but after it has considered
    regenerating it).
    


Reference: /n/sources/patch/sorry/kbuild-rmsystab.h
Date: Sun Aug 21 13:42:47 CES 2005
Reviewed-by: rsc

--- /sys/src/9/port/portmkfile	Sun Aug 21 13:40:29 2005
+++ /sys/src/9/port/portmkfile	Sun Aug 21 13:40:26 2005
@@ -30,7 +30,7 @@
 		mk 'CONF='$i
 
 clean:V:
-	rm -f *.[$OS] *.root.s *.rootc.c cfs.h fs.h init.h conf.h *.out *.m
+	rm -f ../port/systab.h *.[$OS] *.root.s *.rootc.c cfs.h fs.h init.h conf.h *.out *.m
 	for(i in $CONFLIST)
 		mk $i.clean