All of lore.kernel.org
 help / color / mirror / Atom feed
From: Eric Sunshine <sunshine@sunshineco.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: "Jeff King" <peff@peff.net>,
	"Torsten Bögershausen" <tboegi@web.de>,
	"Git List" <git@vger.kernel.org>
Subject: Re: What's cooking in git.git (Feb 2016, #07; Thu, 25)
Date: Mon, 29 Feb 2016 18:37:40 -0500	[thread overview]
Message-ID: <CAPig+cTAv8eNcTkN6K1kJ5zBcibmbRR59MLV6PCM=qa84HNdDg@mail.gmail.com> (raw)
In-Reply-To: <xmqq37sbe8qr.fsf@gitster.mtv.corp.google.com>

On Mon, Feb 29, 2016 at 12:17 PM, Junio C Hamano <gitster@pobox.com> wrote:
> Eric Sunshine <sunshine@sunshineco.com> writes:
>>> Your suggestion elsewhere in the thread to just use clang instead sounds
>>> good to me. :)
>>
>> If possible, for the moment, I'd prefer to hold off on that
>> sledge-hammer approach of unconditionally making the build use clang.
>> It would be nice to have a more detailed understanding of what exactly
>> is triggering the Apple compiler bug, and I've been trying to find
>> time to check it out on my old Mac.
>
> The (fixed) patch posted was "on OSX 10.6, use clang by default"; I
> think that for majority of the users, that is a reasonable thing to do.
>
> The result of the patch still allows those who want to see how badly
> old Gcc breaks to do so with "make CC=gcc", doesn't it?

I was not able to reproduce the problem on OSX 10.5.8.

Since the patch applies specifically to 10.6 (via -eq) rather than
"10.6 and earlier" (via -le) it happily does not break the build for
older OSX releases (such as 10.5.8) which lack clang. Thanks.

      reply	other threads:[~2016-02-29 23:37 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-25 23:14 What's cooking in git.git (Feb 2016, #07; Thu, 25) Junio C Hamano
2016-02-26 16:10 ` Torsten Bögershausen
2016-02-26 18:29   ` Junio C Hamano
2016-02-26 22:34     ` Torsten Bögershausen
2016-02-26 23:35       ` Junio C Hamano
2016-02-27  3:29         ` Jeff King
2016-02-27  7:12           ` Torsten Bögershausen
2016-02-27 17:39             ` Torsten Bögershausen
2016-02-28 18:21               ` Junio C Hamano
2016-02-28 20:09                 ` [PATCH 1/1] config.mak.uname: Darwin: Use clang for Mac OS X 10.6 tboegi
2016-02-29 10:18             ` What's cooking in git.git (Feb 2016, #07; Thu, 25) Jeff King
2016-02-29 16:28               ` Eric Sunshine
2016-02-29 17:17                 ` Junio C Hamano
2016-02-29 23:37                   ` Eric Sunshine [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='CAPig+cTAv8eNcTkN6K1kJ5zBcibmbRR59MLV6PCM=qa84HNdDg@mail.gmail.com' \
    --to=sunshine@sunshineco.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=peff@peff.net \
    --cc=tboegi@web.de \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.