From: Eric Grosse <ehg@lucent.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] plan 9 software for unix
Date: Thu, 13 Feb 2003 07:28:31 -0500 [thread overview]
Message-ID: <8896b442195fea6310edc7d718565305@plan9.bell-labs.com> (raw)
In-Reply-To: <d1073f7492521fd20e9276602429ba3f@plan9.bell-labs.com>
[-- Attachment #1: Type: text/plain, Size: 480 bytes --]
In the interests of keeping down the number of versions,
I'm willing to remove the material from netlib and point
to your mit directory, if that makes you editing life
easier. Or we can move it to someplace else on the
Plan 9 web server.
Just to clarify, too: I'm not mandating that there be
a single version. If the difficulties in getting portable
code to compile everywhere pushes us to have a few versions,
so be it. I just have a desire to minimize confusion.
[-- Attachment #2: Type: message/rfc822, Size: 2251 bytes --]
From: "Russ Cox" <rsc@achille.cs.bell-labs.com>
To: 9fans@cse.psu.edu
Subject: [9fans] plan 9 software for unix
Date: Wed, 12 Feb 2003 15:13:16 -0500
Message-ID: <d1073f7492521fd20e9276602429ba3f@plan9.bell-labs.com>
http://pdos.lcs.mit.edu/~rsc/software
has convenient packagings of libfmt,
libbio, libregexp, and mk that should build
on unix systems with minimal efforts.
i wrote freebsd/386 and linux/386 make files
and would welcome others.
the libraries are intended to integrate well
with the native unix c library, so that they
can be used in unix programs (rather than
just ports of plan 9 programs).
they're all in tgz, rpm, and freebsd ports formats.
enjoy.
next prev parent reply other threads:[~2003-02-13 12:28 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-12 20:13 Russ Cox
2003-02-12 20:46 ` northern snowfall
2003-02-12 22:58 ` Dan Cross
2003-02-13 2:33 ` Russ Cox
2003-02-13 0:26 ` Glenn McGuire
2003-02-13 12:28 ` Eric Grosse [this message]
2003-02-13 17:47 ` Jeff Sickel
2003-02-13 17:57 ` Russ Cox
2003-02-13 18:37 ` Russ Cox
2003-02-13 13:19 Eric Grosse
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=8896b442195fea6310edc7d718565305@plan9.bell-labs.com \
--to=ehg@lucent.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).