From: "Randy J. Ray" <rjray@blackperl.com>
To: "Torsten Bögershausen" <tboegi@web.de>, git@vger.kernel.org
Subject: Re: Git's Perl scripts can fail if user is configured for perlbrew
Date: Mon, 29 Dec 2014 15:57:30 -0600 [thread overview]
Message-ID: <54A1CE4A.7020408@blackperl.com> (raw)
In-Reply-To: <54A159D7.5010307@web.de>
On 12/29/14, 7:40 AM, Torsten Bögershausen wrote:
> Having problems with different perl installations is not an unknown problem
> in Git, I would say.
>
> And Git itself is prepared to handle this situation:
>
> In Makefile I can read:
> # Define PERL_PATH to the path of your Perl binary (usually /usr/bin/perl).
>
> (What Git can not decide is which perl it should use, the one pointed out by $PATH or /usr/bin/perl.)
>
> What does
> "type perl" say ?
>
> And what happens when you build and install Git like this:
> PERL_PATH=/XX/YY/perl make install
>
> -----------
> Are you thinking about changing
> ifndef PERL_PATH
> PERL_PATH = /usr/bin/perl
> endif
> -- into --
> ifndef PERL_PATH
> PERL_PATH = $(shell which perl)
> endif
> ---
>
> At first glance that could make sense, at least to me.
The problem in this case is the Perl being used at run-time, not
build-time. The building of git is done by the homebrew project in this
case, so I don't have direct control over it.
Randy
--
"""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""""
Randy J. Ray Sunnyvale, CA http://www.dereferenced.com
rjray@blackperl.com
twitter.com/rjray
Silicon Valley Scale Modelers: http://www.svsm.org
next prev parent reply other threads:[~2014-12-29 21:57 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-28 22:36 Git's Perl scripts can fail if user is configured for perlbrew Randy J. Ray
2014-12-29 13:21 ` Ævar Arnfjörð Bjarmason
2014-12-29 21:07 ` Randy J. Ray
2014-12-29 23:09 ` Kang-min Liu
2014-12-29 13:40 ` Torsten Bögershausen
2014-12-29 21:57 ` Randy J. Ray [this message]
2014-12-29 23:16 ` Ævar Arnfjörð Bjarmason
2015-01-02 3:08 ` Ben Aveling
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=54A1CE4A.7020408@blackperl.com \
--to=rjray@blackperl.com \
--cc=git@vger.kernel.org \
--cc=tboegi@web.de \
/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.