Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Bob Cochran <openembedded@mindchasers.com>
To: openembedded-devel@lists.openembedded.org
Subject: issue about git and XDL_FAST_HASH on big endian (powerpc) machines
Date: Sun, 07 Sep 2014 14:44:04 -0400	[thread overview]
Message-ID: <540CA774.4060908@mindchasers.com> (raw)

Hi,

On my ppc64 e5500, 'git commit' fails with

git: xdiff/xutils.c:358: xdl_hash_record: Assertion `*ptr == '\n'' failed.

I built git with git_2.0.1 on poky / meta master branch: 669c07d60221

I found a related patch on OpenWRT that tracked the bug assertion on big 
endian machines to the inclusion of XDL_FAST_HASH in config.mak.uname. 
They state that XDL_FAST_HASH won't work on big endian machines.

https://dev.openwrt.org/changeset/37239

For my cross compile build, I patched out XDL_FAST_HASH to verify that 
the bug would go away on my target,  which it did.

Would anyone care to comment on how to best create a patch for this?

A quick search showed that there has been activity on patching 
XDL_FAST_HASH for big endian machines, so maybe just patching it out of 
the make file isn't the best course of action for building a big endian 
target.

Thanks,

Bob


                 reply	other threads:[~2014-09-07 18:52 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=540CA774.4060908@mindchasers.com \
    --to=openembedded@mindchasers.com \
    --cc=openembedded-devel@lists.openembedded.org \
    /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