From: Dan Cross <cross@math.psu.edu>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] sources
Date: Wed, 16 Oct 2002 17:53:44 -0400 [thread overview]
Message-ID: <200210162153.g9GLrii08332@augusta.math.psu.edu> (raw)
In-Reply-To: Your message of "Wed, 16 Oct 2002 16:18:02 EDT." <7aed5425faf6e9a69c50348ae1bbfa60@plan9.bell-labs.com>
> i added nulledf to /sys/src/9/mtx/mkfile.
> you shouldn't be adding devrealtime to
> the mkfile. if you want it, add it to the
> kernel config file. you can build kernels
> without it.
Really? I believe you, but the linker chokes on finding delist without
it. Ahh, I see why; the mkfile has edf in it, which is only used if
devrealtime gets linked in. So perhaps the real solution then is to
remove edf from the mkfile, and specify it, along with devrealtime, in
the kernel config file.
term% diff /n/sources/plan9/sys/src/9/mtx/mkfile mkfile
18d17
< edf.$O\
term% diff -e /n/sources/plan9/sys/src/9/mtx/mkfile mkfile
18d
term%
And similarily with the Alpha:
term% diff /n/sources/plan9/sys/src/9/alphapc/mkfile mkfile
18d17
< edf.$O\
term% diff -e /n/sources/plan9/sys/src/9/alphapc/mkfile mkfile
18d
term%
Could this get updated on sources, please? Or, if it's incorrect,
a similar fix? Thanks.
- Dan C.
next prev parent reply other threads:[~2002-10-16 21:53 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-16 20:18 Russ Cox
2002-10-16 21:53 ` Dan Cross [this message]
-- strict thread matches above, loose matches on Subject: below --
2018-09-19 19:08 Steve Simon
2018-09-19 19:42 ` Sean Hinchee
2007-04-04 20:03 Taj Khattra
2003-12-28 9:33 Lucio De Re
2003-12-28 13:36 ` David Presotto
2003-11-01 18:41 David Presotto
2003-01-03 22:01 Russ Cox
2003-01-03 16:11 Russ Cox
2002-10-16 2:58 Russ Cox
2002-10-16 20:07 ` Dan Cross
2002-10-13 18:28 [9fans] Sources Russ Cox
2002-10-13 19:03 ` John Packer
2002-10-13 18:27 John Packer
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=200210162153.g9GLrii08332@augusta.math.psu.edu \
--to=cross@math.psu.edu \
--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).