From: eschvoca <eschvoca@gmail.com>
To: Junio C Hamano <junkio@cox.net>
Cc: git@vger.kernel.org
Subject: Re: make install bug?
Date: Fri, 16 Dec 2005 10:06:44 -0500 [thread overview]
Message-ID: <2b05065b0512160706o1a6a3fa5kcc34a108f5149a8f@mail.gmail.com> (raw)
In-Reply-To: <7vzmn6i4kf.fsf@assigned-by-dhcp.cox.net>
You are right, CDPATH is the problem. I am no longer exporting CDPATH.
e
On 12/12/05, Junio C Hamano <junkio@cox.net> wrote:
> eschvoca <eschvoca@gmail.com> writes:
>
> > I can fix the problem by changing templates/Makefile to the following:
> >
> > install: all
> > $(INSTALL) -d -m755 $(call shellquote,$(DESTDIR)$(template_dir))
> > (cd blt && $(TAR) cf - . > /tmp/a.tar) | \
> > (cd $(call shellquote,$(DESTDIR)$(template_dir)) && $(TAR) xf /tmp/a.tar)
>
> Here is my guess. Could you try, from your interactive shell:
>
> $ (unset CDPATH; make install)
>
> first without the above "fix" (your "fixed" pipe does not make
> any sense --- what are the data passed between pipe upstream and
> downstream?)?
>
> If that makes the problem go away, then your environment is
> broken --- my guess is that you are exporting CDPATH to
> non-interactive scripts. Don't do that.
>
> I once googled for "CDPATH" and saw many "guide to unix" type
> webpages talk about "CDPATH environment variable"; they are the
> real culprit to cause this confusion in peoples' .bash_profile.
> CDPATH might be a nice variable for interactive shells, but is a
> horrible one if made environment.
>
>
prev parent reply other threads:[~2005-12-16 15:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-12 15:35 make install bug? eschvoca
2005-12-12 17:54 ` Junio C Hamano
2005-12-16 15:06 ` eschvoca [this message]
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=2b05065b0512160706o1a6a3fa5kcc34a108f5149a8f@mail.gmail.com \
--to=eschvoca@gmail.com \
--cc=git@vger.kernel.org \
--cc=junkio@cox.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox