From: Kaartic Sivaraam <kaarticsivaraam91196@gmail.com>
To: git@vger.kernel.org
Subject: Help needed for solving a few issues with building git
Date: Mon, 03 Jul 2017 18:48:18 +0530 [thread overview]
Message-ID: <1499087898.4156.6.camel@gmail.com> (raw)
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?
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
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'
Any thing I'm missing?
Note: In case you were wondering, I was able to build 'git' after
installing the dependant package which I find useless as I don't
require any localization messages.
--
Kaartic
next reply other threads:[~2017-07-03 13:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-03 13:18 Kaartic Sivaraam [this message]
2017-07-03 14:14 ` Help needed for solving a few issues with building git Torsten Bögershausen
2017-07-03 18:13 ` Junio C Hamano
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=1499087898.4156.6.camel@gmail.com \
--to=kaarticsivaraam91196@gmail.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).