threads / discuss / 46066

2.13.0-rc1 is broken on SPARC

Subject: 2.13.0-rc1 is broken on SPARC

## tl;dr

3 messages between May 29, 2017 and May 30, 2017.

replies: 2people: 2as markdown or json

Liam R. Howlett· May 29, 2017, 02:36 UTC · lore

Hello,

My SPARC build does not function and seg bus terminates on any command. I have worked out the commit is the one that switched the default SHA1 code to sha1dc - commit e6b07da2780f349c29809bd75d3eca6ad3c35d19. I managed to get it working by following the instructions on updating the library in commit 28dc98e343ca4eb370a29ceec4c19beac9b5c01e.

Should I generate & send a patch for this? I would normally do just that, but with an external library, the resulting patch required conflict resolution on the merging so format-patch won't work with the given instructions.

I should note that following the build instructions in commit e6b07da2780f349c29809bd75d3eca6ad3c35d19 to switch back to openssl's SHA1 implementation works fine.

Thanks, Liam

Junio C Hamano· May 29, 2017, 04:11 UTC · re: Liam R. Howlett · lore

Re: 2.13.0-rc1 is broken on SPARC

"Liam R. Howlett" <Liam.Howlett@Oracle.com> writes:

> My SPARC build does not function and seg bus terminates on any command.

Sorry, known issue in the released version 2.13 (we would have appreciated if a bug report for -rc1 came way before the decision to tag the final release).

A fix exists on 'pu' (you can merge or cherry-pick a0103914c2); it was unfortunately held up with an unrelated enthusiasm around an attempt to use submodule to manage this codebase in our project.

I'll try to untangle the fix proper and quickly merge down to the maintenance track.

Thanks for a report.

Liam R. Howlett· May 30, 2017, 15:43 UTC · re: Junio C Hamano · lore

Re: 2.13.0-rc1 is broken on SPARC

* Junio C Hamano <gitster@pobox.com> [170529 00:11]:

Show 16 quoted lines

> "Liam R. Howlett" <Liam.Howlett@Oracle.com> writes:
> 
> > My SPARC build does not function and seg bus terminates on any command.
> 
> Sorry, known issue in the released version 2.13 (we would have
> appreciated if a bug report for -rc1 came way before the decision to
> tag the final release).
> 
> A fix exists on 'pu' (you can merge or cherry-pick a0103914c2); it
> was unfortunately held up with an unrelated enthusiasm around an
> attempt to use submodule to manage this codebase in our project.
> 
> I'll try to untangle the fix proper and quickly merge down to the
> maintenance track.
> 
> Thanks for a report.

Thank you for your prompt response. I appreciate your enthusiasm around submodule code as I've used them extensively in the past. I'm happy to hear you have a fix planned for the stable release branch.

Cheers, Liam