From: Junio C Hamano <junkio@cox.net>
To: "Bhavesh Davda" <bhavesh@vmware.com>
Cc: git@vger.kernel.org
Subject: Re: [GIT PATCH] Makefile missing git-runstatus in PROGRAMS list
Date: Wed, 15 Nov 2006 10:29:02 -0800 [thread overview]
Message-ID: <7vzmasmump.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: <FE74AC4E0A23124DA52B99F17F44159701A11D6C@PA-EXCH03.vmware.com> (Bhavesh Davda's message of "Wed, 15 Nov 2006 10:08:44 -0800")
"Bhavesh Davda" <bhavesh@vmware.com> writes:
> 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".
next prev parent reply other threads:[~2006-11-15 18:29 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-15 18:08 [GIT PATCH] Makefile missing git-runstatus in PROGRAMS list Bhavesh Davda
2006-11-15 18:29 ` Junio C Hamano [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-11-15 18:42 Bhavesh Davda
2006-11-15 19:04 ` Junio C Hamano
2006-11-15 4:09 Bhavesh Davda
2006-11-15 4:51 ` Junio C Hamano
2006-11-14 20:55 Bhavesh Davda
2006-11-14 22:40 ` Junio C Hamano
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=7vzmasmump.fsf@assigned-by-dhcp.cox.net \
--to=junkio@cox.net \
--cc=bhavesh@vmware.com \
--cc=git@vger.kernel.org \
/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).