git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ben Walton <bwalton@artsci.utoronto.ca>
To: Mark Ashley <mark@ibiblio.org>
Cc: git <git@vger.kernel.org>
Subject: Re: Compiling git on Solaris. Recipe included.
Date: Wed, 09 May 2012 13:58:46 -0400	[thread overview]
Message-ID: <1336586103-sup-4584@pinkfloyd.chass.utoronto.ca> (raw)
In-Reply-To: <CADmdEsnSt5Do+EuJHzfGxNY6aCnGA6AF6fbEETAGpoL6p7Nuwg@mail.gmail.com>

Excerpts from Mark Ashley's message of Tue May 08 23:11:30 -0400 2012:

Hi Mark,

> I'm compiling git on Solaris 10 and 11 SPARC and X86 using the Sun
> Studio 12.x compilers.

I'm building for solaris 9+ at OpenCSW with the studio compilers.

> git doesn't compile out of the box, there are (see below) lots of
> tweaks to have it use open source stuff in /usr/local/* and also to
> pass some of the configure tests for inet_ntop and -lintl.

I use the following patch for -lintl:
https://gar.svn.sourceforge.net/svnroot/gar/csw/mgar/pkg/git/trunk/files/0007-on-solaris-we-need-to-use-lintl-to-allow-the-new-i18.patch

(For some reason, I didn't get around to generalizing it for
submission yet.)

The build recipe I'm using (for our build system GAR) is here:
https://gar.svn.sourceforge.net/svnroot/gar/csw/mgar/pkg/git/trunk/Makefile

(There is some baggage in the recipe that needs cleanup, such as old
patches that are merged or no longer required, but it builds a nice
clean package that passes the test suite.)

Hope that helps.

Thanks
-Ben
--
Ben Walton
Systems Programmer - CHASS
University of Toronto
C:416.407.5610 | W:416.978.4302

      parent reply	other threads:[~2012-05-09 17:58 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-09  3:11 Compiling git on Solaris. Recipe included Mark Ashley
2012-05-09 17:45 ` Junio C Hamano
2012-05-09 17:58 ` Ben Walton [this message]

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=1336586103-sup-4584@pinkfloyd.chass.utoronto.ca \
    --to=bwalton@artsci.utoronto.ca \
    --cc=git@vger.kernel.org \
    --cc=mark@ibiblio.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).