make install fails because GNU tar needed

make install fails because GNU tar needed

[dev]

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

Re: make install fails because GNU tar needed

[Jeff King]

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

Re: make install fails because GNU tar needed

[dev]

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

Re: make install fails because GNU tar needed

[Matthieu Moy]

dev <dev@cor0.com> writes:

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

That's a generated file (not included by the Makefile, but by some shell
scripts later), don't edit it. Use config.mak for your build
configuration.

-- 
Matthieu Moy
http://www-verimag.imag.fr/~moy/

Re: make install fails because GNU tar needed

[dev]

On August 28, 2014 at 11:26 AM Matthieu Moy
<Matthieu.Moy@grenoble-inp.fr> wrote:
> dev <dev@cor0.com> writes:
>
> > Actually I found a file called GIT-BUILD-OPTIONS :
>
> That's a generated file (not included by the Makefile, but by some
> shell
> scripts later), don't edit it. Use config.mak for your build
> configuration.

good to know .. thanks.