git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Dennis Stosberg <dennis@stosberg.net>
To: Junio C Hamano <junkio@cox.net>
Cc: Petr Baudis <pasky@suse.cz>, git@vger.kernel.org
Subject: Re: [PATCH] Git.pm: Support for perl/ being built by a different compiler
Date: Mon, 26 Jun 2006 10:24:29 +0200	[thread overview]
Message-ID: <20060626082428.G52c9608e@leonov.stosberg.net> (raw)
In-Reply-To: <7vk676orjy.fsf@assigned-by-dhcp.cox.net>

Junio C Hamano wrote:

> Do things link and work fine if we do not have the GCC specific
> options?

Yes, with this patch I can compile Git with GCC while the Perl module
gets built with Sun CC.  The result even works.

If the git commands written in Perl will be converted to use Git.pm,
Sun CC will become a new dependency for Git on Solaris, unless
people build a separate Perl with GCC or manually edit the generated
Makefile in the perl subdir to build the module with GCC.

> I would question why the rest of git is not built with Sun CC as
> well if that is the case.

Well, GCC comes along with Solaris on the CDs while Sun CC is a
separate product.  And usually it's easier to build free software
with GCC, because many projects use GCC extensions.  Often GCC is
the only compiler installed on Solaris machines.

Until the patch series from Florian Forster removed a lot of GCC'isms
a few days ago it was not possible to build Git with Sun CC.

Yesterday I could build the next branch with Sun CC 5.8 with a few
trivial changes.  I will send four patches in reply to this mail.

Junio, please consider the first two patches for inclusion into the
next branch.  The third patch is on top of Pasky's changes in the pu
branch.  The fourth patch is a strange workaround for a strange
problem of which I think it is an error in Sun's compiler.  That one
should not make its way into Git, but maybe someone on the list has
an idea about the problem.

Regards,
Dennis

  parent reply	other threads:[~2006-06-26  8:24 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-25  1:47 [PATCH] Git.pm: Support for perl/ being built by a different compiler Petr Baudis
2006-06-25  3:14 ` Junio C Hamano
2006-06-25 15:27   ` Petr Baudis
2006-06-26  8:24   ` Dennis Stosberg [this message]
2006-06-26  8:26     ` [PATCH] Solaris needs inclusion of signal.h for signal() Dennis Stosberg
2006-06-26  8:27     ` [PATCH] Fix pkt-line.h to compile with a non-GCC compiler Dennis Stosberg
2006-06-26  8:27     ` [PATCH] "test" in Solaris' /bin/sh does not support -e Dennis Stosberg
2006-06-26  9:19       ` Junio C Hamano
2006-06-26  9:42         ` Dennis Stosberg
2006-06-26 10:04           ` Dennis Stosberg
2006-06-26 17:03             ` Junio C Hamano
2006-06-26 22:21               ` [PATCH] Makefile fix for Solaris Dennis Stosberg
2006-06-26 22:23               ` [PATCH] Add possibility to pass CFLAGS and LDFLAGS specific to the perl subdir Dennis Stosberg
2006-07-01 22:59                 ` Petr Baudis
2006-06-26 22:25               ` [PATCH] "test" in Solaris' /bin/sh does not support -e Dennis Stosberg
2006-06-26  8:29     ` [PATCH] Git.pm: Support for perl/ being built by a different compiler Dennis Stosberg
2006-06-26  8:51       ` Thomas Glanzmann
2006-06-26  9:26     ` Junio C Hamano
2006-06-26  9:32       ` Dennis Stosberg

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=20060626082428.G52c9608e@leonov.stosberg.net \
    --to=dennis@stosberg.net \
    --cc=git@vger.kernel.org \
    --cc=junkio@cox.net \
    --cc=pasky@suse.cz \
    /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).