All of lore.kernel.org
 help / color / mirror / Atom feed
From: dev <dev@cor0.com>
To: Jonathan Nieder <jrnieder@gmail.com>
Cc: Jeff King <peff@peff.net>, git@vger.kernel.org
Subject: make install fails because GNU tar needed
Date: Thu, 28 Aug 2014 10:16:48 -0400 (EDT)	[thread overview]
Message-ID: <267282067.24350.1409235408562.JavaMail.vpopmail@webmail2.networksolutionsemail.com> (raw)



Well I am making progress in that I have what looks like a
successful build.

what fails next on the non-linux world is the next requirement for
GNU tar for some reason :

# gmake CFLAGS="$CFLAGS" LDFLAGS="$LD_OPTIONS" NEEDS_LIBICONV=Yes \
> SHELL_PATH=/usr/local/bin/bash \
> SANE_TOOL_PATH=/usr/local/bin \
> USE_LIBPCRE=1 LIBPCREDIR=/usr/local CURLDIR=/usr/local \
> EXPATDIR=/usr/local NEEDS_LIBINTL_BEFORE_LIBICONV=1 \
> NEEDS_SOCKET=1 NEEDS_RESOLV=1 USE_NSEC=1 \
> PERL_PATH=/usr/local/bin/perl \
> NO_PYTHON=1 DEFAULT_PAGER=/usr/xpg4/bin/more \
> DEFAULT_EDITOR=/usr/local/bin/vim DEFAULT_HELP_FORMAT=man \
> prefix=/usr/local install >
> ../git-2.0.4_SunOS5.10_sparcv9.006.install.log
    * new build flags
"read-cache.c", line 780: warning: statement not reached
"xdiff/xutils.c", line 180: warning: statement not reached
Writing perl.mak for Git
Writing MYMETA.yml and MYMETA.json
/bin/sh: gtar: /bin/shnot found
: gtar: not found
gmake[1]: *** [install] Error 1
gmake: *** [install] Error 2


Well that is maddening.

Is there some magic somewhere to use ordinary POSIX tar ?

Also, what is shnot ?

dev

             reply	other threads:[~2014-08-28 14:17 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-28 14:16 dev [this message]
2014-08-28 14:50 ` make install fails because GNU tar needed Jeff King
2014-08-28 15:08   ` dev
2014-08-28 15:26     ` Matthieu Moy
2014-08-30 15:26       ` dev

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=267282067.24350.1409235408562.JavaMail.vpopmail@webmail2.networksolutionsemail.com \
    --to=dev@cor0.com \
    --cc=git@vger.kernel.org \
    --cc=jrnieder@gmail.com \
    --cc=peff@peff.net \
    /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.