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
Kaartic Sivaraam <kaarticsivaraam91196@gmail.com>
Date
Jul 5, 2017, 17:06 UTC
Message-ID
<1499274396.16389.4.camel@gmail.com>
In-Reply-To
<1499198419.6428.7.camel@gmail.com>
On Wed, 2017-07-05 at 01:30 +0530, Kaartic Sivaraam wrote:
Show 21 quoted lines
> 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.

Show 17 quoted lines
> >  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).
> > 
> 
Previous: Kaartic Sivaraam
Message 6 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.