From: Chris Ridd <chris.ridd@isode.com>
To: Git Mailing List <git@vger.kernel.org>
Subject: Re: git-instaweb portability issue (maybe?)
Date: Fri, 13 Jun 2008 15:42:49 +0100 [thread overview]
Message-ID: <48528769.2000007@isode.com> (raw)
In-Reply-To: <alpine.DEB.1.10.0806131016120.8043@alchemy.localdomain>
Asheesh Laroia wrote:
> On Fri, 13 Jun 2008, Chris Ridd wrote:
>
>> Denis Bueno wrote:
>>> On Fri, Jun 13, 2008 at 09:46, Asheesh Laroia <asheesh@asheesh.org>
>>> wrote:
>>>> Does OS X ship /usr/bin/env?
>>>>
>>>> If you type "/usr/bin/env perl" in a Terminal window, do you get Perl?
>>>
>>> Sorry, I should have made that clear earlier: yes.
>>>
>>> funsat[122] > /usr/bin/env perl --version
>>>
>>> This is perl, v5.8.8 built for darwin-2level
>>
>> MacPorts /tends/ to make ports use stuff from other ports instead of
>> using Apple-installed bits. In this case, maybe git from MacPorts is
>> using perl from MacPorts?
>
> FWIW, the problem seems to be that it's not finding *any* Perl.
That's odd, because the Portfile for git-core (1.5.5.3_0) does the
build, test and destroot install setting:
PERL_PATH="/usr/bin/env perl" NO_FINK=1 NO_DARWIN_PORTS=1
(and some other stuff). Have you pinged the port maintainer
(bryan@larsen.st)?
Cheers,
Chris
next prev parent reply other threads:[~2008-06-13 14:43 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-13 13:26 git-instaweb portability issue (maybe?) Denis Bueno
2008-06-13 13:38 ` Denis Bueno
2008-06-13 13:46 ` Asheesh Laroia
2008-06-13 13:59 ` Denis Bueno
2008-06-13 14:10 ` Chris Ridd
2008-06-13 14:16 ` Asheesh Laroia
2008-06-13 14:42 ` Chris Ridd [this message]
2008-06-13 14:47 ` Denis Bueno
2008-06-13 14:21 ` Luciano Rocha
2008-06-13 14:39 ` Denis Bueno
2008-06-13 15:13 ` Luciano Rocha
2008-06-13 15:32 ` Jakub Narebski
2008-06-13 15:39 ` Luciano Rocha
2008-06-13 14:22 ` Jakub Narebski
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=48528769.2000007@isode.com \
--to=chris.ridd@isode.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).