From: Luther Huffman lutherh@infinet.com
Subject: mothra boddles on plan9.bell-labs.com
Date: Thu, 4 Jul 1996 21:24:21 +0100 [thread overview]
Message-ID: <19960704202421.MIP0Wty13utYS6TNVKgQlAGuW-_IArLY9eg0poTUyNo@z> (raw)
At 03:59 PM 7/4/96 -0400, you wrote:
>I just tried. Two things are misssing. First, the mkfile in
>/sys/src/fb wants a subdirectory dpic. Without that, the mk fails,
>even with the -k flag. Second, a number of things use the stdargs
>interface, which the second edition doesn't support.
Actually, it does support stdarg; it's hidden in /$objtype/include. I'm
always forgetting to look for things there myself. I think the problem is
<stdarg.h> isn't included in mothra.h (assuming that's where Tom wants it.)
>
>That said, after hacking around those two things, the new mothra looks
>pretty good.
Sure does. It apparently will finally give us ftp:// support. Just in time,
because I'm writing the Plan 9 Perl web page even as I'm typing this. I've
emailed Tom asking him to come up with a "Mothra Enhanced" logo so my page
would be the first one to bear it. :-)
>
>| For example, the argument list of dial(.,.,.,.) has changed
>| since the distribution, but I don't know if an update has been
>| sent out. If not, remove the last argument.
>
>That was fixed in a previous update.
Oops, I missed that. And after I finished trimming args off csgetval(). Oh,
well. Such is life.
---
Luther Huffman lutherh@stratcom.com
Strategic Computer Solutions, Inc.
http://www.stratcom.com/
next reply other threads:[~1996-07-04 20:24 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
1996-07-04 20:24 Luther [this message]
-- strict thread matches above, loose matches on Subject: below --
1996-07-06 3:40 Scott
1996-07-05 18:23 Scott
1996-07-05 3:37 td
1996-07-04 19:59 Scott
1996-07-04 12:18 td
1996-07-04 12:16 td
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=19960704202421.MIP0Wty13utYS6TNVKgQlAGuW-_IArLY9eg0poTUyNo@z \
--to=9fans@9fans.net \
/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).