From: Arthur Haas <cs004@yoda.wg.waii.com>
To: help-gcc@gnu.org
Subject: Re: make error
Date: Thu, 30 Sep 1999 23:56:00 -0000 [thread overview]
Message-ID: <lrk8pc159a.fsf@yoda.wg.waii.com> (raw)
Message-ID: <19990930235600.MOqIfuP3DG_-Fxu0LLPo6NArDWubKtfjgUyE8ImMLyo@z> (raw)
In-Reply-To: <7sohch$s5e$1@news.news-service.com>
Rob <"oostveen"@ReaX-IT.nX (X=l)> writes:
> hi,
> # make
> ...
> make[1]: Entering directory '/tmp/bash-2.03/builtins'
> rm -f libbuiltins.a
> cr libbuiltins.a builtins.o .... <rest of objects> ...
> make[1]: cr: command not found
> make[1]: *** [libbuiltins.a] Error 127
> make[1]: Leaving directory '/tmp/bash-2.03/builtins'
> make: *** [builtins/libbuiltins.a] Error 1
> #
>
> It seems to be missing the cr command... i don't know what it is or what
> it
> does. Anyone have a clue ?
>
You aren't missing the 'cr' command (if it exists), make
can't find 'ar'! The output from make should have looked
like ...
ar cr libbuiltins.a (bunch of '.o' files)
Where is 'ar' on your system? If it is in a strange place, you
might need to do something like ...
# make AR="/why/would/anyone/put/ar/in/this/directory"
or edit the Makefile in the subdirectories to point to
your 'ar'.
Note: If you are building compiling as root, your PATH
may not include where 'ar' is installed. I'm guessing
you can be doing this because your prompt is '#'.
--
###############################
# Art Haas
# (713) 689-2417
###############################
next prev parent reply other threads:[~1999-09-30 23:56 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-09-27 13:44 Rob
1999-09-27 13:21 ` Arthur Haas [this message]
1999-09-30 23:56 ` Arthur Haas
1999-10-01 0:00 ` Arthur Haas
1999-09-27 13:39 ` Paul D. Smith
1999-09-30 23:56 ` Paul D. Smith
1999-10-01 0:00 ` Paul D. Smith
1999-09-30 23:56 ` Rob
1999-10-01 0:00 ` Rob
2000-08-24 8:48 Helfried Tschemmernegg
2000-08-24 20:14 ` Alexandre Oliva
2007-04-27 6:34 q-x jiang
2007-04-28 1:13 ` Michael Eager
2007-04-27 17:35 Timothy C Prince
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=lrk8pc159a.fsf@yoda.wg.waii.com \
--to=cs004@yoda.wg.waii.com \
--cc=help-gcc@gnu.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).