From: Kaartic Sivaraam <kaarticsivaraam91196@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: Help needed for solving a few issues with building git
Date: Wed, 05 Jul 2017 22:36:36 +0530 [thread overview]
Message-ID: <1499274396.16389.4.camel@gmail.com> (raw)
In-Reply-To: <1499198419.6428.7.camel@gmail.com>
On Wed, 2017-07-05 at 01:30 +0530, Kaartic Sivaraam wrote:
> I tried pointing it to the installed location, it doesn't seem to be
> working. To elaborate a little on what I did,
>
> * I installed the "libcurl4-openssl-dev" package b
> * I found that the 'include' directory to be present at
> '/usr/include/x86_64-linux-gnu/curl'. I wasn't sure if
> '/usr/lib/x86_64-linux-gnu/' is the corresponding library
> directory.
> * I took the common parent of both '/usr' and ran the
> following
> commands to build 'git'
>
> $ make CURLDIR=/usr prefix=/custom/location
> $ make CURLDIR=/usr install prefix=/custom/location
>
> * The build did succeed but I get an error that "'https'
> helper
> is not found"
>
> Was anything I did, wrong?
>
Ok, at last I was able to build git with https support using 'curl'
built from it's source. Anyways, thanks for the help, folks.
> > This is probably because you are trying to run without installing?
>
> Nope. I'm *installing* git not using the binary wrappers.
>
> > 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?
> >
>
> Obviously, I don't see any 'git-remote-https' binary in the folder to
> which I built git.
>
> > 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).
> >
>
prev parent reply other threads:[~2017-07-05 17:06 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
2017-07-03 20:11 ` Junio C Hamano
2017-07-04 20:00 ` Kaartic Sivaraam
2017-07-05 17:06 ` Kaartic Sivaraam [this message]
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=1499274396.16389.4.camel@gmail.com \
--to=kaarticsivaraam91196@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.