Re: building git on Solaris

From: Brandon Casey <brandon.casey.ctr@nrlssc.navy.mil>
Date: Sep 8, 2010, 15:16 UTC
Message-ID: <nMrBbfBjISeakrCCpr3u3goqKMFMLUPCXiAa8ohZrHAmY1k660aYdA@cipher.nrlssc.navy.mil>
In-Reply-To: <4C87A1DF.1020706@bio.umass.edu>

On 09/08/2010 09:46 AM, Chris Hoogendyk wrote:

Show 16 quoted lines

> Ævar Arnfjörð Bjarmason wrote:
>> On Tue, Sep 7, 2010 at 21:02, Chris Hoogendyk <hoogendyk@bio.umass.edu> wrote:
>>  
>>> Does anyone have any guidance or clues as to where I should look from here?
>>> Or how to fix this?
>>>     
>>
>> Call make as gmake?
> 
> magical.
> 
> I did an `ln -s /usr/local/bin/make /usr/local/bin/gmake` and then referenced gmake rather than make. For some reason, that got over the hump. I have no clue why calling make would initially work and later in the process revert to /usr/ccs/bin/make, but calling the same code via the symlink name gmake works.
> 
> Anyway, now I'm in the normal build debugging mode. Got all the way through to building the Documentation, at which stage I now need to get asciidoc and python. I don't really like bloating my minimal server systems with python, but it seems I'm finally stuck, since I have faculty who really want to use git.
> 
> Thanks for the clue.

There is a quick-install-doc make target.

It extracts prebuilt documentation from a branch named origin/man in your repository. Junio keeps this up-to-date with the Documentation on master. You can use it instead of trying to build the documentation from scratch.

-Brandon