git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Mark Ashley <mark@ibiblio.org>
Cc: git@vger.kernel.org
Subject: Re: Compiling git on Solaris. Recipe included.
Date: Wed, 09 May 2012 10:45:41 -0700	[thread overview]
Message-ID: <7vd36dtfi2.fsf@alter.siamese.dyndns.org> (raw)
In-Reply-To: <CADmdEsnSt5Do+EuJHzfGxNY6aCnGA6AF6fbEETAGpoL6p7Nuwg@mail.gmail.com> (Mark Ashley's message of "Wed, 9 May 2012 13:11:30 +1000")

Mark Ashley <mark@ibiblio.org> writes:

> I'm compiling git on Solaris 10 and 11 SPARC and X86 using the Sun Studio
> 12.x compilers.
>
> git doesn't compile out of the box, there are (see below) lots of tweaks to

Thanks for an interest in Git, but I am somewhat dissapointed by your
message.  As our Makefiles strive to offer necessary knobs to tweak from
the command line for platform-specific glitches, from "Recipe included" on
the subject, I think people would have expected to see something like:

    gmake   VAR1=VAL1 \
            VAR2=VAL2 \
            VAR3=VAL3 ...

or perhaps:

    cat >config.mak <<-EOF
    VAR1=VAL1
    VAR2=VAL2
    ...
    EOF

and not a sequence of commands to rewrite files in-tree.

Other people have built git on Solaris but probably not many people have
done so recently.  The platform specific knobs in our Makefiles may have
to be extended to accomodate newer version of Solaris.  So the "Recipe"
may not be just the series of make variables, but needs a patch or two to
the Makefile to enhance the tweaks.

See 614dd90 (Makefile: SunOS 5.6 portability fix, 2010-05-14) for an
example of such a patch.

Thanks.

  reply	other threads:[~2012-05-09 17:46 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 [this message]
2012-05-09 17:58 ` Ben Walton

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=7vd36dtfi2.fsf@alter.siamese.dyndns.org \
    --to=gitster@pobox.com \
    --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).