On Fri, Jun 13, 2008 at 10:42, Chris Ridd <chris.ridd@xxxxxxxxx> wrote: > 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@xxxxxxxxxxx> >>>> 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@xxxxxxxxx)? The issue seems to be one of the way bash is treating quotes. It apparently is trying to find the *command* "/usr/bin/env perl" and not executing the command "/usr/bin/env" with a first argument of "perl". See my message to Luciano moments ago. -- Denis -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
