Linux PARISC architecture development
 help / color / mirror / Atom feed
From: Steven Pritchard <steve@silug.org>
To: parisc-linux@thepuffingroup.com
Subject: Re: [parisc-linux] Building bin-utils and gcc on HP735...
Date: Tue, 4 Apr 2000 13:44:57 -0500 (CDT)	[thread overview]
Message-ID: <200004041844.NAA11438@osiris.silug.org> (raw)
In-Reply-To: <E12cW8W-0006p3-00@endor.fc.hp.com> from Paul Bame at "Apr 4, 2000 10:25:04 am"

Paul Bame said:
> Sooner or later it is probably a good idea to start using GNU versions
> of all the tools referenced in the makefiles and scripts if you have
> the space to do so.

I should note that there are HP-UX 10.20 and 11.0 binary depot
packages of many GNU utilities at

    ftp://puffin.external.hp.com/pub/parisc/binaries/depot/

Everything installs to /usr/local/bin, so you can just put that at the
beginning of your PATH, and everything should be happy.  (Oh, before
installing any of it, you might want to "chmod -R go-w /usr/local".
The default permissions are insane.)

Feel free to send requests for other stuff.  (I'll try to start
building packages for the CVS gcc, binutils, etc. sometime soon.  I'm
still recovering from switching jobs and a move, so I'm way behind on
everything...)

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

  reply	other threads:[~2000-04-04 18:45 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-03-31 10:51 [parisc-linux] Building bin-utils and gcc on HP735 BOSCHINI
2000-03-31 16:52 ` willy
2000-03-31 15:55   ` Nick Cabatoff
2000-03-31 22:27   ` Steven Pritchard
2000-04-01  1:19     ` Steven Pritchard
2000-04-04 16:25 ` Paul Bame
2000-04-04 18:44   ` Steven Pritchard [this message]
  -- strict thread matches above, loose matches on Subject: below --
2000-03-31 17:59 BOSCHINI
2000-03-31 17:26 ` willy

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=200004041844.NAA11438@osiris.silug.org \
    --to=steve@silug.org \
    --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