> > > Attached is my attempt at the same command "make > prefix=/var/tmp/ggg clean > > all install" > > > > make install failes for the templates directory, leading to > the entire make > > install failing: > > > > make -C templates DESTDIR='' install > > make[1]: Entering directory `/VMware/kernel/git/git/templates' > > : no custom templates yet > > install -d -m755 '/var/tmp/ggg/share/git-core/templates/' > > (cd blt && tar cf - .) | \ > > (cd '/var/tmp/ggg/share/git-core/templates/' && tar xf -) > > tar: This does not look like a tar archive > > tar: Skipping to next header > > tar: Archive contains obsolescent base-64 headers > > tar: Error exit delayed from previous errors > > I have a feeling that you have CDPATH exported to the > environment, which is a braindamage. It is a fine usability > helper for interactive shells so I do not have problem with > people setting that in shell as shell variables, though. > > In other words, never do "export CDPATH=..." nor "export CDPATH". > > Indeed! I had "export CDPATH=.:$HOME" in my $HOME/.bash_profile. "export -n CDPATH", and now "make install" works, setting up those hard links too. If this is a common gotcha in building and installing git, maybe you should add it near the top of the INSTALL instructions. I haven't run into this issue with other projects. Is there something that can be changed in git's Makefile so it works even if CDPATH is set and exported in people's environments? What about simply not naming the subdir blt for both source and install directories under templates? Thanks! - Bhavesh - To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html