public inbox for git@vger.kernel.org 
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox•com>
To: Kaartic Sivaraam <kaarticsivaraam91196@gmail•com>
Cc: git@vger•kernel.org
Subject: Re: Help needed for solving a few issues with building git
Date: Mon, 03 Jul 2017 11:13:52 -0700	[thread overview]
Message-ID: <xmqqshidl76n.fsf@gitster.mtv.corp.google.com> (raw)
In-Reply-To: <1499087898.4156.6.camel@gmail.com> (Kaartic Sivaraam's message of "Mon, 03 Jul 2017 18:48:18 +0530")

Kaartic Sivaraam <kaarticsivaraam91196@gmail•com> writes:

> Hello all,
>
> Building without localization support
> ------------------------------------
> I tried to build git from source without localization support by adding
> the following line to the Makefile,
>
>     NO_GETTEXT=1
>
> It doesn't seem to be working for reasons I'm unable to find. I used
> the following commands to build git.
>
>     make prefix=$CUSTOM_BUILD_LOCATION
>     make install prefix=$CUSTOM_BUILD_LOCATION
>
> While trying to build (without the 'gettext' library that's required
> for localization) I get the following error,
>
>     Manifying 8 pod documents
>         SUBDIR templates
>         MSGFMT po/build/locale/pt_PT/LC_MESSAGES/git.mo
>     /bin/sh: 1: msgfmt: not found
>     Makefile:2179: recipe for target
>     'po/build/locale/pt_PT/LC_MESSAGES/git.mo' failed
>     make: *** [po/build/locale/pt_PT/LC_MESSAGES/git.mo] Error 127
>
>     What could I be missing?

There is

    ifndef NO_GETTEXT
    all:: $(MOFILES)
    endif

which attempts to avoid generating *.mo files, but that does not
seem to be working.

>
>
>     Adding HTTPS support
>     --------------------
>     I tried to add HTTP/HTTPS support to the custom built version for which
>     AFAIK 'git' depends on 'curl'. I tried providing the location of the
>     curl source in the Makefile using the following line after reading the
>     instructions in the Makefile.
>
>     CURLDIR=/path/to/curl/source

Shouldn't this point at an installed location (iow, we do not build
curl from the source while building Git)?

    # Define CURLDIR=/foo/bar if your curl header and library files are in
    # /foo/bar/include and /foo/bar/lib directories.


>     Even after doing this the custom built git errors with the following
>     message when I try to use the 'git fetch' command,
>
>     fatal: Unable to find remote helper for 'https'

This is probably because you are trying to run without installing?
Ask the "git" you built what its --exec-path is, and run "ls" on
that directory to see if you have git-remote-https installed?

Trying a freshly built Git binaries without installing is done by
setting GIT_EXEC_PATH to point at bin-wrappers/ directory at the
top-level of your build tree (that is how our tests can run on an
otherwise virgin box with no Git installed).

  parent reply	other threads:[~2017-07-03 18:13 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-03 13:18 Help needed for solving a few issues with building git Kaartic Sivaraam
2017-07-03 14:14 ` Torsten Bögershausen
2017-07-03 18:13 ` Junio C Hamano [this message]
2017-07-03 20:11   ` Junio C Hamano
2017-07-04 20:00     ` Kaartic Sivaraam
2017-07-05 17:06       ` Kaartic Sivaraam

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=xmqqshidl76n.fsf@gitster.mtv.corp.google.com \
    --to=gitster@pobox$(echo .)com \
    --cc=git@vger$(echo .)kernel.org \
    --cc=kaarticsivaraam91196@gmail$(echo .)com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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