git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Renato Botelho <garga@FreeBSD.org>
To: git@vger.kernel.org
Subject: Re: [bug] 2.5.0 build with NO_PERL is broken
Date: Fri, 14 Aug 2015 16:46:18 +0000 (UTC)	[thread overview]
Message-ID: <loom.20150814T184447-932@post.gmane.org> (raw)
In-Reply-To: loom.20150814T171757-901@post.gmane.org

Renato Botelho <garga <at> FreeBSD.org> writes:

> 
> I was working on update git on FreeBSD ports tree to 2.5.0 and I noted 2.5.0
> is trying to use perl even when it's being built with NO_PERL knob.
> 
> /bin/sh: /usr/bin/perl: not found
> Makefile:1701: recipe for target 'common-cmds.h' failed
> gmake[2]: *** [common-cmds.h] Error 127
> gmake[2]: *** Waiting for unfinished jobs....
> gmake[2]: Leaving directory '/freebsd/ports/head/devel/git/work/git-2.5.0'
> 
> After a quick search, looks like commit 527ec3980b is the culprit since it
> removed generate-cmdlist.sh and introduced generate-cmdlist.perl.
> 
> I just would like to check if it's planned to add perl dependency during
> build time or it happened by accident and will be fixed so NO_PERL can work
> again.

I also found that some commands require perl when NO_PERL is set:

git-submodule
git-request-pull
git-am

Definitely NO_PERL is not working as expected.

  reply	other threads:[~2015-08-14 16:46 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-14 15:41 [bug] 2.5.0 build with NO_PERL is broken Renato Botelho
2015-08-14 16:46 ` Renato Botelho [this message]
2015-08-14 19:59   ` Junio C Hamano
2015-08-14 20:49     ` Eric Sunshine
2015-08-14 21:02       ` Junio C Hamano
2015-08-14 21:15         ` Eric Sunshine
2015-08-14 22:22           ` Junio C Hamano
2015-08-14 22:25             ` Eric Sunshine
2015-08-18 11:05               ` Renato Botelho
2015-08-18 16:42                 ` Eric Sunshine
2015-08-18 18:09                   ` Renato Botelho

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=loom.20150814T184447-932@post.gmane.org \
    --to=garga@freebsd.org \
    --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).