On Mon, Feb 29, 2016 at 12:17 PM, Junio C Hamano wrote:
> Eric Sunshine 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
Eric Sunshine 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 un
On Mon, Feb 29, 2016 at 5:18 AM, Jeff King wrote:
> 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 run
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
Torsten Bögershausen writes:
> How about something like this as a workaround ?
> (I can send a proper patch, if this is the way forward)
> ...
> Make Git compile under Mac OS X 10.6 by using clang instead of gcc
Given that it is understandable that Apple is no longer interesting
in fixing co
How about something like this as a workaround ?
(I can send a proper patch, if this is the way forward)
commit dcd7d5551d6931e47829c7febbee0877340eb17f
Author: Torsten Bögershausen
Date: Sat Feb 27 15:18:28 2016 +0100
config.mak.uname: Darwin: Use clang for Mac OS X 10.6
Commit
"t
On 27.02.16 04:29, Jeff King wrote:
> On Fri, Feb 26, 2016 at 03:35:10PM -0800, Junio C Hamano wrote:
>
>>> Digging means:
>>> run git bisect and report the commit.
>>> And this makes the compiler happy:
>>> Revert "tree-diff: catch integer overflow in combine_diff_path allocation"
>> So?
>>
>>
On Fri, Feb 26, 2016 at 03:35:10PM -0800, Junio C Hamano wrote:
> > Digging means:
> > run git bisect and report the commit.
> > And this makes the compiler happy:
> > Revert "tree-diff: catch integer overflow in combine_diff_path allocation"
>
> So?
>
> Identifying two versions of the same C
Torsten Bögershausen writes:
> On 2016-02-26 19.29, Junio C Hamano wrote:
>> Torsten Bögershausen writes:
>>
>>> CC combine-diff.o
>>> combine-diff.c: In function ‘diff_tree_combined’:
>>> combine-diff.c:1391: internal compiler error: Segmentation fault
>>> Please submit a full bug report,
>>>
On 2016-02-26 19.29, Junio C Hamano wrote:
> Torsten Bögershausen writes:
>
>> CC combine-diff.o
>> combine-diff.c: In function ‘diff_tree_combined’:
>> combine-diff.c:1391: internal compiler error: Segmentation fault
>> Please submit a full bug report,
>> with preprocessed source if appropriate.
Torsten Bögershausen writes:
> CC combine-diff.o
> combine-diff.c: In function ‘diff_tree_combined’:
> combine-diff.c:1391: internal compiler error: Segmentation fault
> Please submit a full bug report,
> with preprocessed source if appropriate.
> See http://developer.apple.com/bugreporter> for i
> * jk/tighten-alloc (2016-02-22) 22 commits
> (merged to 'next' on 2016-02-24 at 78b3251)
> + ewah: convert to REALLOC_ARRAY, etc
> + convert ewah/bitmap code to use xmalloc
> + diff_populate_gitlink: use a strbuf
> + transport_anonymize_url: use xstrfmt
> + git-compat-util: drop mempcpy c
Here are the topics that have been cooking. Commits prefixed with
'-' are only in 'pu' (proposed updates) while commits prefixed with
'+' are in 'next'. The ones marked with '.' do not appear in any of
the integration branches, but I am still holding onto them.
You can find the changes described
13 matches
Mail list logo
