From: Ian Abbott <abbotti@mev.co.uk>
To: Junio C Hamano <gitster@pobox.com>
Cc: "git@vger.kernel.org" <git@vger.kernel.org>
Subject: Re: Question about PERL_PATH
Date: Fri, 6 May 2011 17:42:19 +0100 [thread overview]
Message-ID: <4DC424EB.6000107@mev.co.uk> (raw)
In-Reply-To: <7v7ha33jd7.fsf@alter.siamese.dyndns.org>
On 06/05/11 17:05, Junio C Hamano wrote:
> Ian Abbott <abbotti@mev.co.uk> writes:
>
>> The Gentoo ebuilds for git have started invoking 'make' with the option
>> 'PERL_PATH=/usr/bin/env perl'. This doesn't seem to cause any problems
>> except when running git instaweb, which outputs an error similar to the
>> following:
>>
>> /usr/libexec/git-core/git-instaweb: line 135: /usr/bin/env perl: No such
>> file or directory
>
> The variable is not PERL_COMMAND_LINE, but is PERL_PATH, so I think it
> should expects the path to the program.
>
> Our testsuite also rely on it being the path to the program by enclosing
> the reference to it inside double quotes, to make sure that PERL_PATH set
> to "/Program Files/Perl/perl.exe" works. Didn't Gentoo folks see any test
> breakage before shipping the ebuild procedure?
Both you and Michael make excellent points and I've submitted a Gentoo
bug report mentioning this thread, so we'll see what happens!
http://bugs.gentoo.org/show_bug.cgi?id=366241
--
-=( Ian Abbott @ MEV Ltd. E-mail: <abbotti@mev.co.uk> )=-
-=( Tel: +44 (0)161 477 1898 FAX: +44 (0)161 718 3587 )=-
next prev parent reply other threads:[~2011-05-06 16:42 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-06 13:30 Question about PERL_PATH Ian Abbott
2011-05-06 15:56 ` Michael J Gruber
2011-05-06 16:05 ` Junio C Hamano
2011-05-06 16:42 ` Ian Abbott [this message]
2011-05-07 18:02 ` Robin H. Johnson
2011-05-08 0:13 ` Jeff King
2011-05-09 14:49 ` Drew Northup
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=4DC424EB.6000107@mev.co.uk \
--to=abbotti@mev.co.uk \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
/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.