From: jmk@plan9.bell-labs.com
To: 9fans@cse.psu.edu
Subject: Re: [9fans] devarch.c mb build errors
Date: Mon, 15 Dec 2003 14:01:54 -0500 [thread overview]
Message-ID: <ba8ab480414ce5c6044bb9fbfe54332e@plan9.bell-labs.com> (raw)
In-Reply-To: <3FDE03D4.9080902@cox.net>
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.
next prev parent reply other threads:[~2003-12-15 19:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-15 18:56 Chris Van Horne
2003-12-15 19:01 ` jmk [this message]
2003-12-15 19:06 ` Charles Forsyth
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=ba8ab480414ce5c6044bb9fbfe54332e@plan9.bell-labs.com \
--to=jmk@plan9.bell-labs.com \
--cc=9fans@cse.psu.edu \
/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).