From: Jeff King <peff@peff.net>
To: dev <dev@cor0.com>
Cc: Jonathan Nieder <jrnieder@gmail.com>, git@vger.kernel.org
Subject: Re: make install fails because GNU tar needed
Date: Thu, 28 Aug 2014 10:50:56 -0400 [thread overview]
Message-ID: <20140828145056.GA26855@peff.net> (raw)
In-Reply-To: <267282067.24350.1409235408562.JavaMail.vpopmail@webmail2.networksolutionsemail.com>
On Thu, Aug 28, 2014 at 10:16:48AM -0400, dev wrote:
> # 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 \
As an aside, you may be able to drop some of these defines. For example,
we set NEEDS_SOCKET automatically on Solaris. See the "SunOS" section of
config.mak.uname for the complete set of defaults.
> Is there some magic somewhere to use ordinary POSIX tar ?
gmake TAR=tar ?
The default of gtar for Solaris dates back to 2005. There may have been
a reason then that is no longer valid now, or there may be something
besides "make install" which uses a more advanced feature.
> /bin/sh: gtar: /bin/shnot found
> : gtar: not found
> gmake[1]: *** [install] Error 1
> gmake: *** [install] Error 2
>
> [...]
>
> Also, what is shnot ?
Two messages stepping on each other's toes?
-Peff
next prev parent reply other threads:[~2014-08-28 14:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-28 14:16 make install fails because GNU tar needed dev
2014-08-28 14:50 ` Jeff King [this message]
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=20140828145056.GA26855@peff.net \
--to=peff@peff.net \
--cc=dev@cor0.com \
--cc=git@vger.kernel.org \
--cc=jrnieder@gmail.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 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).