From: Chris Hoogendyk <hoogendyk@bio.umass.edu>
To: "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>
Cc: git mailing list <git@vger.kernel.org>
Subject: Re: building git on Solaris
Date: Wed, 08 Sep 2010 10:46:55 -0400 [thread overview]
Message-ID: <4C87A1DF.1020706@bio.umass.edu> (raw)
In-Reply-To: <AANLkTikvy-wUB-RFLegp7KJa_srqh97nLC03bdZDmru=@mail.gmail.com>
Æ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.
--
---------------
Chris Hoogendyk
-
O__ ---- Systems Administrator
c/ /'_ --- Biology & Geology Departments
(*) \(*) -- 140 Morrill Science Center
~~~~~~~~~~ - University of Massachusetts, Amherst
<hoogendyk@bio.umass.edu>
---------------
Erdös 4
next prev parent reply other threads:[~2010-09-08 14:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-07 21:02 building git on Solaris Chris Hoogendyk
2010-09-07 21:42 ` Ævar Arnfjörð Bjarmason
2010-09-08 14:46 ` Chris Hoogendyk [this message]
2010-09-08 14:55 ` Ben Walton
2010-09-08 15:16 ` Brandon Casey
2010-09-10 20:00 ` Tomas Carnecky
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4C87A1DF.1020706@bio.umass.edu \
--to=hoogendyk@bio.umass.edu \
--cc=avarab@gmail.com \
--cc=git@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).