From: Grant Grundler <grundler@puffin.external.hp.com>
To: joel.soete@freebel.net
Cc: aungho <aungho@sina.com>, parisc-linux@lists.parisc-linux.org
Subject: Re: [parisc-linux] RE: RE: about linux for PA_RISC
Date: Tue, 30 Oct 2001 13:14:47 -0700 [thread overview]
Message-ID: <200110302014.NAA15070@puffin.external.hp.com> (raw)
In-Reply-To: Message from joel.soete@freebel.net of "Tue, 30 Oct 2001 09:44:29 +0100." <1004431469.3bde686db73fb@webmail.tiscalinet.be>
joel.soete@freebel.net wrote:
> Quoting aungho <aungho@sina.com>:
> > But other problems:
>
> > 1.can HP_UX 11.11 for pa_risc 2.0 on L2000 gcc complier,we find gcc for
> > HP_ux 11.00 for pa_risc 1.x and HP_UX 10.0 and they work normally,how to
> > get gcc complier for hp_ux 11.11.
I'm pretty sure you can use the same toolchain as on 11.00.
HP has released a CD (and ISO image) with PA20 gcc/binutils
toolchain for HPUX 11. The one I have in front of me is labeled:
"HP-UX 11.0 PA-RISC Open Source Developer Toolkit, Release 000310"
I think I found it's replacement on www.software.hp.com at:
http://www.software.hp.com/cgi-bin/swdepot_parser.cgi/cgi/displayProductInfo.pl?productNumber=B9891AA
> > 2.Linux for pa_risc is only a test version.
>
> You have right. But it seems quiet stable now.
I agree the kernel is stable but:
o not everything on every platform works
o most older servers still not support at all (eg EFGHI/K/T/V-class)
o toolchain and kernel changes aren't fully merged upstream.
It's definitely not a "mature product". But lots of cool
things (eg XF86, iptables, apache, tcpdump, apt-get) do work
on many parisc boxes.
grant
prev parent reply other threads:[~2001-10-30 20:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20011030012552.27471.qmail@sina.com>
2001-10-30 8:44 ` [parisc-linux] RE: RE: about linux for PA_RISC joel.soete
2001-10-30 20:14 ` Grant Grundler [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=200110302014.NAA15070@puffin.external.hp.com \
--to=grundler@puffin.external.hp.com \
--cc=aungho@sina.com \
--cc=joel.soete@freebel.net \
--cc=parisc-linux@lists.parisc-linux.org \
/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