On 09/20/2010 05:53 PM, Andrew Keller wrote: > On Sep 20, 2010, at 3:12 PM, Brandon Casey wrote: >> You could try >> deleting the config.mak.autogen file that configure creates, and just run >> make by itself. Based on what you've describe, it would look something >> like this: >> >> cd <path-to-git-src> >> rm config.mak.autogen >> cat >config.mak <<EOF >> CC=/usr/local/bin/gcc >> PREFIX=/usr/users/students/ak4390/.local >> PYTHON_PATH=/usr/local/bin/python >> TCL_PATH=/usr/local/bin/tclsh8.4 >> NO_PERL_MAKEMAKER=1 >> EOF >> make >> >> Then add 'install' to the make command line when you are ready. >> >> Notice, I placed all of the make settings in a file named config.mak. This >> file is imported by the main Makefile automatically and is intended to be >> used like this for user settings. If you really need to disable pthreads, >> then you can add NO_PTHREADS=1. Check out the comments at the top of the >> Makefile for a list of all variables that can be set. > > Compiling as described above appears to go down in flames: > > $ make > /bin/sh: curl-config: not found At this point, the above is just a warning that curl-config is not in your path. If curl is not installed on your system, you need to set NO_CURL=1. > CC fast-import.o > In file included from builtin.h:4, > from fast-import.c:147: > git-compat-util.h:140:25: openssl/ssl.h: No such file or directory > git-compat-util.h:141:25: openssl/err.h: No such file or directory <snip other related warnings> Fixed by setting NO_OPENSSL=1. > And, this is the same source tree that just worked a minute ago, when > I used configure/make/make install. I then copied the entire source > folder, with the modified config.mak file, to my laptop running Snow Leopard, > modified the variables in the config.mak file to match the system, and it > compiled and installed just fine. So, this server seems to have a problem > with not running the configure script first. git's configure script is a little different from the configure scripts in other projects. All configure does in git is set variables that are used by the Makefile. Using its rules, it tries to figure out what the best setting is for each variable. Any of these variables can be set manually in the user's config.mak file. Apparently, additional variables need to be modified from their default to handle your system. Once you determine the set of variables that need to be set, they most likely will not need to be changed when compiling future versions of git. The above two variables (NO_CURL, NO_OPENSSL) will likely fix the errors that you reported, but I don't guarantee that more errors will not be produced and will require additional settings. All of the variables are described in the comments at the top of the Makefile. It's an iterative process. You could also use the config.mak.autogen as the baseline for you config.mak file. -Brandon -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html