From: Paul Bame <bame@endor.fc.hp.com>
To: BOSCHINI@ICIL64.CILEA.IT
Cc: PARISC-LINUX@thepuffingroup.com, QUATTRONE@cilea.it
Subject: Re: [parisc-linux] Building bin-utils and gcc on HP735...
Date: Tue, 04 Apr 2000 10:25:04 -0600 [thread overview]
Message-ID: <E12cW8W-0006p3-00@endor.fc.hp.com> (raw)
In-Reply-To: Your message of "Fri, 31 Mar 2000 10:51:34 GMT." <01JNOHLGY86Q000XJ1@ICIL64.CILEA.IT>
My guess is your build problems are still based on using some of the
HP tools instead of the GNU ones. Some things to check:
when your build asks for 'sh' it should get 'bash'
when your build asks for 'make' it should get gnu make
flex and bison you already know about.
Aliases aren't passed through makefiles and often not through shell
scripts either, so you'll have to do this with $PATH magic and/or
symbolic links. I built/installed bash, make, flex, bison, binutils,
gcc, and a bunch of other GNU tools (ls, find, tar, gzip, patch) into
/opt/puffin and put /opt/puffin/bin first in my $PATH.
Your difficulties building palo strongly indicate that HP make is
sometimes being used. palo/palo/Makefile and palo/ipl/Makefile
will work with either HP make or GNU make, but palo/Makefile will
only work with GNU make. When you do 'make palo' from linux-2.3,
the master make eventually does 'cd ../palo; make lifimage', and
it appears that perhaps this invocation of make is getting the HP one.
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.
Happy building!
-Paul Bame
next prev parent reply other threads:[~2000-04-04 16:27 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 [this message]
2000-04-04 18:44 ` Steven Pritchard
-- 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=E12cW8W-0006p3-00@endor.fc.hp.com \
--to=bame@endor.fc.hp.com \
--cc=BOSCHINI@ICIL64.CILEA.IT \
--cc=PARISC-LINUX@thepuffingroup.com \
--cc=QUATTRONE@cilea.it \
/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