From: jmk@plan9.att.com jmk@plan9.att.com
Subject: BUG in a kernel mkfile
Date: Tue, 22 Aug 1995 21:18:08 -0400 [thread overview]
Message-ID: <19950823011808.hHRx0iH5rCdSs2mlUrua6BQwVT9HZZMr7m-aZL5TUjQ@z> (raw)
If this is a bug I don't understand how I've ever been able to make a kernel.
The distributed mkfile works fine for me.
------ original message follows ------
>From cse.psu.edu!9fans-outgoing-owner Tue Aug 22 18:02:40 EDT 1995
Received: by colossus.cse.psu.edu id <45595>; Tue, 22 Aug 1995 17:47:55 -0400
Received: from postman.ncube.com ([134.242.8.47]) by colossus.cse.psu.edu with SMTP id <45610>; Tue, 22 Aug 1995 17:47:34 -0400
Received: from butler.ncube.com by postman.ncube.com (4.1/SMI-4.1)
id AA09554; Tue, 22 Aug 95 14:47:59 PDT
Received: from skynet.ncube.com by butler.ncube.com (5.0/SMI-SVR4)
id AA28205; Tue, 22 Aug 1995 14:47:54 +0800
Date: Tue, 22 Aug 1995 02:47:54 -0400
From: avg@postman.ncube.com (Vadim Antonov)
Message-Id: <9508222147.AA28205@butler.ncube.com>
To: 9fans@cse.psu.edu
Subject: BUG in a kernel mkfile
Content-Length: 308
Sender: owner-9fans@cse.psu.edu
Precedence: bulk
Reply-To: 9fans@cse.psu.edu
In 2.0 distribution:
1. Can't compile kernel
FIX: In file /sys/src/9/boot/mkfile
replace lines
ar uv $LIBRARY $names
rm -f $names
with
eval ar uvc $LIBRARY $names
eval rm -rf $names
(Sorry, i discovered it two weeks ago and forgot to post).
--vadim
next reply other threads:[~1995-08-23 1:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
1995-08-23 1:18 jmk [this message]
-- strict thread matches above, loose matches on Subject: below --
1995-08-23 17:51 bobf
1995-08-23 6:03 Vadim
1995-08-22 6:47 Vadim
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=19950823011808.hHRx0iH5rCdSs2mlUrua6BQwVT9HZZMr7m-aZL5TUjQ@z \
--to=jmk@plan9.att.com \
/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).