git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jeff King <peff@peff.net>
To: Eldon Nelson <eldon_nelson@ieee.org>
Cc: git@vger.kernel.org
Subject: Re: Compile Error on Git 2.0.1 on Redhat 5.9 with Fix
Date: Wed, 2 Jul 2014 12:29:47 -0400	[thread overview]
Message-ID: <20140702162947.GA14404@sigill.intra.peff.net> (raw)
In-Reply-To: <CAH5EwqY8D=CGxB+rZvwPH5115r9qmRCBBvJMG_o0962d4Uquxw@mail.gmail.com>

On Wed, Jul 02, 2014 at 10:56:25AM -0500, Eldon Nelson wrote:

> When compiling Git 2.0.1 on RedHat 5.9 as a non-root user I get the
> following error:
> 
> BUILD ERROR
> 
> ```
> make prefix=/home/eldon/local all doc info
> ...
>     CC zlib.o
>     CC unix-socket.o
>     CC thread-utils.o
>     CC compat/strlcpy.o
>     AR libgit.a
> /bin/sh: gar: command not found
> make: *** [libgit.a] Error 127
> ```

The Makefile defines AR as:

  $ git grep ^AR Makefile
  Makefile:AR = ar

so it should already do what you want by default.  But that make
variable can be overridden. Can you show us the contents of your
config.mak and config.mak.autogen files (if either exists)?

It's also possible that you have AR set in your environment (show us
"echo $AR"), but that would usually not override the Makefile unless
"make -e" is used (and that is not in your command-line above, but it's
possible that make is a shell alias or something).

> My fix was to make a symlink below:
> 
> SYMLINK
> 
> ```
> gar -> /usr/bin/ar
> ```

A simpler workaround is probably:

  make AR=ar ...

but probably the "right" solution is to eliminate whatever is providing
the bogus override in the first place.

-Peff

  parent reply	other threads:[~2014-07-02 16:29 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-02 15:56 Compile Error on Git 2.0.1 on Redhat 5.9 with Fix Eldon Nelson
2014-07-02 16:25 ` Matthieu Moy
2014-07-02 16:29 ` Jeff King [this message]
2014-07-03 20:13 ` Eldon Nelson

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=20140702162947.GA14404@sigill.intra.peff.net \
    --to=peff@peff.net \
    --cc=eldon_nelson@ieee.org \
    --cc=git@vger.kernel.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 NNTP newsgroup(s).