git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: Help needed for solving a few issues with building git

From
Junio C Hamano <gitster@pobox.com>
Date
Jul 3, 2017, 18:13 UTC
Message-ID
<xmqqshidl76n.fsf@gitster.mtv.corp.google.com>
In-Reply-To
<1499087898.4156.6.camel@gmail.com>
Kaartic Sivaraam <kaarticsivaraam91196@gmail.com> writes:
Show 27 quoted lines
> 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.

Show 10 quoted lines
>
>
>     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).

Previous: Torsten BögershausenNext: Junio C Hamano
Message 3 of 6 in “Help needed for solving a few issues with building git”
  1. Kaartic SivaraamJul 3, 2017
  2. Torsten BögershausenJul 3, 2017
  3. Junio C HamanoJul 3, 2017
  4. Junio C HamanoJul 3, 2017
  5. Kaartic SivaraamJul 4, 2017
  6. Kaartic SivaraamJul 5, 2017

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.