From: bame@riverrock.org
To: Helge Deller <deller@gmx.de>
Cc: kailasr@webcash.com, parisc-linux@thepuffingroup.com
Subject: Re: [parisc-linux] Make palo problem
Date: Thu, 26 Oct 2000 19:28:41 -0600 [thread overview]
Message-ID: <m13oyK8-001Vp3C@chalet> (raw)
In-Reply-To: Your message of "Fri, 27 Oct 2000 03:17:37 +0200." <00102703173703.00370@P100>
= > ipl.a: could not read symbols: Archive has no index; run ranlib to add one
= > make[2]: *** [iplelf] Error 1
= > make[2]: Leaving directory `/cvs/palo/ipl'
= > make[1]: *** [makeipl] Error 2
= > make[1]: Leaving directory `/cvs/palo'
= > make: *** [palo] Error 2
= >
=
= you need to go to /palo/ipl and do "hppa-linux-ranlib ipl.a". Then go back
= to /linux and do a "make palo" again.
=
= This is a common problem, in which I also run every time if /palo changes.
= Matt/Paul: can't we fix this in the Makefile ?
I changed ipl/Makefile to use hppa-linux-ar rather than ar. No
ranlib is required in this case.
Prior to this the native host's ar was being used. Mine
(GNU ar 2.9.5) has always
worked without need of an extra ranlib step but I guess that's not
true for everyone. People using 'ar' which requires a following ranlib
should probably insert a ranlib line into palo/palo/Makefile after
the 'ar' there. Just how likely is it to find this type of ar on
Linux these days?
-P
prev parent reply other threads:[~2000-10-27 1:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-10-27 0:58 [parisc-linux] Make palo problem Kailashnath V Rampure
2000-10-27 1:11 ` Matt Taggart
2000-10-27 1:17 ` Helge Deller
2000-10-27 1:28 ` bame [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=m13oyK8-001Vp3C@chalet \
--to=bame@riverrock.org \
--cc=deller@gmx.de \
--cc=kailasr@webcash.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.