From mboxrd@z Thu Jan  1 00:00:00 1970
Message-ID: <ba8ab480414ce5c6044bb9fbfe54332e@plan9.bell-labs.com>
From: jmk@plan9.bell-labs.com
To: 9fans@cse.psu.edu
Subject: Re: [9fans] devarch.c mb build errors
In-Reply-To: <3FDE03D4.9080902@cox.net>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Date: Mon, 15 Dec 2003 14:01:54 -0500
Topicbox-Message-UUID: a4f433d6-eacc-11e9-9e20-41e7f4b1d025

On Mon Dec 15 13:57:40 EST 2003, cvanhorne@cox.net wrote:
> After a replica/pull a day or two ago, along with subsequent pulls,
> I've been getting these build errors on pc kernels (pcauth/pcdisk):
>
> <cut>
> 8c -FVw devarch.c
> devarch.c:759 name not declared: mb386
> devarch.c:761 name not declared: mb586
> devarch.c:811 name not declared: mb386
> devarch.c:815 name not declared: mb586
> devarch.c:878 name not declared: mb586
> mk: 8c -FVw devarch.c  : exit status=rc 2033: 8c 2035: error
> <cut>
>
> Any insight as to why this is happening, and or a possible [way to] fix?

Someone updated devarch.c without noticing other files were involved.
Changes to /sys/src/9/pc/fns.h and /sys/src/9/pc/l.s are now on sources.