From: rattan <rattan@cps.cmich.edu>
To: Russ Cox <russcox@gmail.com>,
Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: Re: [9fans] OT: plan9ports update via cvs?
Date: Sun, 17 Jul 2005 21:33:15 -0400 [thread overview]
Message-ID: <Pine.GSO.4.61.0507172131350.21643@cps210> (raw)
In-Reply-To: <Pine.GSO.4.61.0507171337040.15363@cps210>
On Sun, 17 Jul 2005, rattan wrote:
>
>
> On Sun, 17 Jul 2005, Russ Cox wrote:
>
>> There are probably errors earlier on.
>> Run
>>
>> PLAN9=/usr/local/plan9 $PLAN9/dist/isum
>>
>> and see what you get.
>
> Parts of install.log (does show errors shown below,
> redoing the process produces same results..):
>
I tried the compilation under Linux and it compiles
fine. The problem I have mentioned is on Solaris-5.10
SunOS cps210 5.10 Generic sun4u sparc SUNW,Sun-Blade-100
-ishwar
prev parent reply other threads:[~2005-07-18 1:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-16 23:44 rattan
2005-07-17 4:02 ` Russ Cox
2005-07-17 17:42 ` rattan
2005-07-18 1:33 ` rattan [this message]
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=Pine.GSO.4.61.0507172131350.21643@cps210 \
--to=rattan@cps.cmich.edu \
--cc=9fans@cse.psu.edu \
--cc=russcox@gmail.com \
/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).