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



On August 28, 2014 at 10:50 AM Jeff King <peff@peff.net> wrote:
> 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.

I figured as much but for the moment I am flailing along towards a nice
working build first and then pray to the gods of complication for some
kindness and simplification.  :-)

Thus far the build process seems to work fine. I have no idea if I
can use SSH protocol as I would need to set up a dummy to test it.
Everything else seems to work. I think. :-\

> > Is there some magic somewhere to use ordinary POSIX tar ?
>
> gmake TAR=tar ?

ha .. yeah I guess.

Actually I found a file called GIT-BUILD-OPTIONS :

# cat GIT-BUILD-OPTIONS
SHELL_PATH='/usr/local/bin/bash'
PERL_PATH='/usr/local/bin/perl'
DIFF='diff'
PYTHON_PATH='/usr/bin/python'
TAR='tar'
NO_CURL=''
USE_LIBPCRE='1'
NO_PERL=''
NO_PYTHON='1'
NO_UNIX_SOCKETS=''
NO_GETTEXT=''
GETTEXT_POISON=''


Funny looking options for NO_foo where I would think that a null
string indicates that in fact I have foo?  Because I do have curl
and perl and most likely UNIX_SOCKETS.  Regardless, I simply edited
that file and three others to stop the search for gtar.

> 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.

Yes, I seem to recall that long long ago there were problems with old
tar on Solaris 2.5.1 back in the 90's and then it carried forwards up
to Solaris 7 or 8.  The ultimate POSIX tar as well as tar that can
archive
or extract anything from anything is Joerg Schilling's star.

   http://sourceforge.net/projects/s-tar/

I use that nearly everywhere that I must ensure all metadata and data
gets taken care of correctly and cross platform.  However, hell will
freeze over before we ever see it included in a distro or UNIX anywhere
so for now tar will suffice.

> > /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?

Yeah .. I saw that after I sent the email.

dev

  reply	other threads:[~2014-08-28 15:09 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
2014-08-28 15:08   ` dev [this message]
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=502287515.26012.1409238536022.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.