From: Mike Haertel mike@cs.uoregon.edu
Subject: Ported U*ix programs to Plan 9?
Date: Sat, 3 Jul 1993 14:53:53 -0400 [thread overview]
Message-ID: <19930703185353.dTJHfWAMbxpAs7z8XJV4Rhp9fK_FWb8aoHarG9aOegU@z> (raw)
The ape library and the associated "pcc" compiler have worked very well
for me for porting a variety of unix programs to plan 9.
The most annoying aspect of the whole process is not porting C code,
but porting makefiles and the associated shell scripts.
To this end, I have ported the almquist /bin/sh from netbsd, and gnu
make. Using these tools I have been able to configure and build a
variety* of gnu software right out of the box. I've also ported the
pbmplus suite of bitmap tools, although that required some small
source changes.
In the process I've found a few bugs in the ape library; most notably
the wait() function does not return exit status correctly. What I
think happened is the kernel recently started putting the string
"<program>:" into the exit status, and the ape library has not been
updated to know this.
I eventually (september or october) will make all this stuff
available to others, but right now my time is limited.
Mike
* sorry, no emacs. :-) It can be done--in 1991, out of sheer masochism,
and to annoy rob, I ported gnu emacs to plan 9. Fortunately, it has
been lost to the mists of time...
next reply other threads:[~1993-07-03 18:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
1993-07-03 18:53 Mike [this message]
-- strict thread matches above, loose matches on Subject: below --
1993-07-05 17:59 forsyth
1993-07-05 17:26 mike
1993-07-05 15:43 Roger
1993-07-05 15:31 rsalz
1993-07-03 17:48 Magnus
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=19930703185353.dTJHfWAMbxpAs7z8XJV4Rhp9fK_FWb8aoHarG9aOegU@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).