Re: What's cooking in git.git (Feb 2016, #07; Thu, 25)
- From
Jeff King <peff@peff.net>
- Date
- Feb 29, 2016, 10:18 UTC
- Message-ID
- <20160229101808.GD2950@sigill.intra.peff.net>
- In-Reply-To
- <56D14C56.6070306@web.de>
On Sat, Feb 27, 2016 at 08:12:22AM +0100, Torsten Bögershausen wrote:
Show 11 quoted lines
> > 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