From: Jeff King <peff@peff.net>
To: "Torsten Bögershausen" <tboegi@web.de>
Cc: Junio C Hamano <gitster@pobox.com>, git@vger.kernel.org
Subject: Re: What's cooking in git.git (Feb 2016, #07; Thu, 25)
Date: Mon, 29 Feb 2016 05:18:08 -0500 [thread overview]
Message-ID: <20160229101808.GD2950@sigill.intra.peff.net> (raw)
In-Reply-To: <56D14C56.6070306@web.de>
On Sat, Feb 27, 2016 at 08:12:22AM +0100, Torsten Bögershausen wrote:
> > Torsten, what is the compiler version (I don't have Apple compilers, but
> > it seems plausible that older clang might have the same problem).
>
> That's machine is running Mac OS X 10.6, which is no longer supported
> with updates.
>
> gcc --version
> i686-apple-darwin10-gcc-4.2.1 (GCC) 4.2.1 (Apple Inc. build 5666) (dot 3)
> Copyright (C) 2007 Free Software Foundation, Inc.
> This is free software; see the source for copying conditions. There is NO
> warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
Thanks. Out of curiosity, I tried to reproduce by with a build of gcc
4.2.1, to see if I could bisect. But it seems the toolchain is quite
complex. After much munging, I managed to build a broken compiler (which
I think is due to a much too-new version of bison, but I stopped
digging).
Your suggestion elsewhere in the thread to just use clang instead sounds
good to me. :)
-Peff
next prev parent reply other threads:[~2016-02-29 10:18 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 ` Jeff King [this message]
2016-02-29 16:28 ` What's cooking in git.git (Feb 2016, #07; Thu, 25) Eric Sunshine
2016-02-29 17:17 ` Junio C Hamano
2016-02-29 23:37 ` Eric Sunshine
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=20160229101808.GD2950@sigill.intra.peff.net \
--to=peff@peff.net \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--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 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).