On 08/19/2011 05:42 PM, Junio C Hamano wrote: > Sorin Sbarnea <sorin.sbarnea@xxxxxxxxx> writes: > >> On Fri, Aug 19, 2011 at 23:19, Brandon Casey >>> Probably MakeMaker. >>> >>> Setting NO_PERL_MAKEMAKER may help: >>> >>> rm perl/perl.mak >>> make NO_PERL_MAKEMAKER=1 >>> >> I confirm that this workaround solved the problem. Now the question is >> what should be changed so git will be installed (and build) without >> problems by homebrew? > > If the user's distro does not have packaged makemaker, or if the user > chooses not to install it, then the build procedure of git can be told to > avoid using it, which is what you did. So there is nothing to fix there. > > If you are not going to tell git to avoid makemaker, in other words, if > you want to use makemaker, then installing it before starting the build > procedure would help, too. But that is outside the scope of git project. I got the impression that his system did have makemaker, and that it created the perl.mak file, but then building git failed because some header files were missing from his perl installation. Earlier he said: >> The only files existing in >> /System/Library/Perl/5.12/darwin-thread-multi-2level/CORE/ are >> libperl.dylib andperl.h. I don't have access to a mac, but on my system I have many header files in .../x86_64-linux-thread-multi/CORE/ including config.h. These files are part of the base perl installation rpm (i.e. not some -devel rpm). But like you said, there is nothing to fix on the git side of things. -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