From: willy@thepuffingroup.com
To: Mike Brancato <funnyguy@digitalsmackdown.net>
Cc: parisc-linux@thepuffingroup.com
Subject: Re: [parisc-linux] gcc 2.9
Date: Sun, 26 Mar 2000 19:29:37 -0500 [thread overview]
Message-ID: <20000326192937.C29700@thepuffingroup.com> (raw)
In-Reply-To: <Pine.LNX.4.10.10003261604240.2215-100000@morph.net>; from Mike Brancato on Sun, Mar 26, 2000 at 04:10:17PM -0500
On Sun, Mar 26, 2000 at 04:10:17PM -0500, Mike Brancato wrote:
> I am trying to put Puffin on a 735/125 we have lying around.
erm.... you are aware we're not really ready for end users yet, right?
We don't have a compiler running natively yet (though we may not be too
far away now). In fact, there's no userspace at all except for what
you compile yourself.
> Does anyone
> have a more step-by-step method of ho to put it on the machine? I will
> get HPUX 10.20 or 11.0 (i think only 10.20 supports the 735?)
that's correct, 10.20 is the last supported HPUX on the 735.
> plus. does X compile well on pa-risc linux? can you use the X that comes
> with HPUX in linux? i guess its not necessary to work, people will only be
> able to connect to it thru envizex x stations.
we're about to start discussing X with HP. stay tuned.
next prev parent reply other threads:[~2000-03-26 23:29 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-03-24 12:15 [parisc-linux] Success story on 715/33 and a question Ulrich Strelow
2000-03-24 13:31 ` Philipp Rumpf
2000-03-26 21:27 ` willy
2000-03-25 20:29 ` Paul Bame
2000-03-26 3:10 ` [parisc-linux] gcc 2.9 Mike Brancato
2000-03-26 21:51 ` willy
2000-03-26 21:10 ` Mike Brancato
2000-03-27 0:29 ` willy [this message]
2000-03-28 15:00 ` Brian S. Julin
2000-04-03 15:06 ` [parisc-linux] ALPHA cross compile -- progress Brian S. Julin
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=20000326192937.C29700@thepuffingroup.com \
--to=willy@thepuffingroup.com \
--cc=funnyguy@digitalsmackdown.net \
--cc=parisc-linux@thepuffingroup.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