Comments on: How to install Git on a shared host

By: laxxy

laxxy — Fri, 18 May 2012 14:48:00 +0000

Looks like it has some dependencies that are not installed by default in my case:
In file included from http.c:1:http.h:6:23: warning: curl/curl.h: No such file or directoryhttp.h:7:23: warning: curl/easy.h: No such file or directoryIn file included from http.c:1:http.h:46: error: expected specifier-qualifier-list before ‘CURLcode’http.h:51: error: expected specifier-qualifier-list before ‘CURL’

(the “curl” command itself worked fine; this is me trying to install 1.7.10.2 on RHEL 6.2; same result with 1.7.10.1

By: Anonymous

Anonymous — Wed, 18 Jan 2012 13:56:00 +0000

Great tutorial ~~
But I got the latest git from the official site. Currently its on 1.7.8.3.

By: Josiah

Josiah — Tue, 06 Dec 2011 17:59:00 +0000

I was having the same issue as Bryan, and this fixed it! Thank you so much!!!

By: FireMouse

FireMouse — Sat, 03 Dec 2011 21:05:00 +0000

I learned so much just from this one brief tutorial!
I’ve never permanently added to the $PATH environment using .bashrc before, and never brought in source and ran a “make” with a compiler before – and never added man pages before. . .
Of course, you have to already know your way around a little bit to handle this, But far too many tutorials are sloppy, inaccurate, and obfuscated with too much unnecessary “fluff”.

Thank you Joe for your excellent, concise and to the point tutorial!

By: Phil

Phil — Tue, 22 Nov 2011 19:24:00 +0000

After a bit of messing around, here’s how to install the man pages assuming your install prefix was $HOME/opt as above (substitute your version number as appropriate below):

cd $HOME/opt/share/man/

curl -LO “http://git-core.googlecode.com/files/git-manpages-1.7.7.4.tar.gz

tar xvfz git-manpages-1.7.7.4.tar.gz

You should now have man1, man5 and man7 directories in $HOME/opt/share/man

The last step is to make sure man finds them (add this to .bashrc):

export MANPATH=$HOME/opt/share/man:$MANPATH

By: Guest

Guest — Wed, 09 Nov 2011 15:10:00 +0000

You need to compile zlib the same way (configure –prefix=$HOME/opt) and provided zlib’s location to git via
./configure –prefix=$HOME/opt –with-zlib=$HOME/opt

By: Joe Maller

Joe Maller — Sat, 29 Oct 2011 19:47:00 +0000

Poke around in the configure file, there are options for specifying alternate file locations for the compiler. Take a look at my linked post about installing Subversion. That was really difficult and I ended up specifying alternate locations for several libraries.

Or you could try compiling Git binaries on a similar machine and then uploading those.

By: Bryan

Bryan — Sat, 29 Oct 2011 07:05:00 +0000

I know this is a fairly old thread, but here goes. I’m connecting to a friend of mine’s box via SSH (no root access and he’s hard to get in touch with to get him to do this for me). Everything was working great up to the first make command, at which time I get this message:

[grndrgn@rtfm git-1.7.7.1]$ make
CC daemon.o
In file included from daemon.c:1:
cache.h:19:18: error: zlib.h: No such file or directory
In file included from daemon.c:1:
cache.h:21: error: expected specifier-qualifier-list before âz_streamâ
make: *** [daemon.o] Error 1
[grndrgn@rtfm git-1.7.7.1]$

Any ideas? One of the lines indicates that it can’t find zlib.h. So I installed a local user copy of zlib. However, I can’t figure out how to tell git’s make program where to find it.