From: Ronald G Minnich <rminnich@lanl.gov>
To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: Re: [9fans] plan9ports & macos 10.4 don't like each othere.
Date: Wed, 9 Nov 2005 20:46:42 -0700 [thread overview]
Message-ID: <4372C2A2.1090802@lanl.gov> (raw)
In-Reply-To: <A22C5032-E36E-47C8-B1EC-90CA8443A309@corpus-callosum.com>
Jeff Sickel wrote:
> just build it w/ Russ' INSTALL script. gcc4 works fine, and once mk is
> built, the rest is a piece of cake.
that much I know since I build it about once a day on all sorts of
things. As I said, I can build it fine, as long as I'm not root.
I don't know what the issue is, have not had time to look at it.
ron
next prev parent reply other threads:[~2005-11-10 3:46 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-09 20:19 Ronald G Minnich
2005-11-09 20:28 ` Ben Huntsman
2005-11-09 20:30 ` Russ Cox
2005-11-09 20:50 ` Matt Sottile
2005-11-09 20:52 ` Ronald G Minnich
2005-11-10 2:18 ` Jeff Sickel
2005-11-10 3:46 ` Ronald G Minnich [this message]
2005-11-10 5:25 ` Jeff Sickel
2005-11-10 5:53 ` Russ Cox
2005-11-10 7:30 ` Jeff Sickel
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=4372C2A2.1090802@lanl.gov \
--to=rminnich@lanl.gov \
--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).