From: Steven Pritchard <steve@silug.org>
To: Alan Modra <alan@linuxcare.com.au>
Cc: "SOETE Jo�l" <JSO@EUROPAY.COM>, parisc-linux@thepuffingroup.com
Subject: Re: [parisc-linux] hpux11 build problems.
Date: Sat, 10 Jun 2000 22:29:35 -0500 (CDT) [thread overview]
Message-ID: <200006110329.WAA05054@osiris.silug.org> (raw)
In-Reply-To: <Pine.LNX.4.21.0006101047110.5101-100000@front.linuxcare.com.au> "from Alan Modra at Jun 10, 2000 11:20:55 am"
Alan Modra said:
> > > Would it be better to work with gcc-2.8.1-1 (on Software Porting And
> > > Archive Center for HPUX (http://hpux.connect.org.uk/) it was no more
> > > available) or to prefer HPUX 10.20? Or is it requested to install also
> > > egcs-1.1.2-1?
>
> You may be better off using the puffin gcc.
More specifically, I'd *avoid* the gcc in
puffin.external.hp.com/pub/parisc/binaries/depot/. That's really only
there because a) I packaged it, and b) I thought it might be useful
for getting a better toolchain compiled. It seemed to work for me,
but I never really tested it all that well. I mostly used the egcs
that's also there to compile everything, although I'm pretty sure that
neither is suitable for compiling the kernel...
I guess I really need to get the CVS gcc packaged up for everyone...
Is it in a reasonably stable state at the moment?
Steve
--
steve@silug.org | Linux Users of Central Illinois
(618)398-7320 | Meetings the 4th Tuesday of every month
Steven Pritchard | http://www.luci.org/ for more info
next prev parent reply other threads:[~2000-06-11 3:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <A4A5E4C468B5D11190220001FA6835DD04DD8627@epixch003>
2000-06-10 1:20 ` [parisc-linux] hpux11 build problems Alan Modra
2000-06-11 3:29 ` Steven Pritchard [this message]
2000-06-12 3:27 ` John David Anglin
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=200006110329.WAA05054@osiris.silug.org \
--to=steve@silug.org \
--cc=JSO@EUROPAY.COM \
--cc=alan@linuxcare.com.au \
--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