[yocto] libgcrypt building fails for armv6 binaries.

[akuster]

On 09/22/2017 09:15 PM, Yusuke Mitsuki wrote:
> Hello yocto
>
> libgcrypt has problem that build for armv6.
> bitbake said error messages at do_compile as follows:
> ...(snip)...
> | ../../libgcrypt-1.8.0/cipher/rijndael-armv8-aarch32-ce.S: Assembler messages:
> | ../../libgcrypt-1.8.0/cipher/rijndael-armv8-aarch32-ce.S:1165:
> Error: selected processor does not support `rbit r8,lr' in ARM mode
> | ../../libgcrypt-1.8.0/cipher/rijndael-armv8-aarch32-ce.S:1165:
> Error: selected processor does not support `rbit r9,r9' in ARM mode
> | ../../libgcrypt-1.8.0/cipher/rijndael-armv8-aarch32-ce.S:1165:
> Error: selected processor does not support `rbit r10,r10' in ARM mode
> | ../../libgcrypt-1.8.0/cipher/rijndael-armv8-aarch32-ce.S:1165:
> Error: selected processor does not support `rbit r11,r11' in ARM mode
> | ../../libgcrypt-1.8.0/cipher/rijndael-armv8-aarch32-ce.S:1165:
> Error: selected processor does not support `rbit r8,lr' in ARM mode
> | ../../libgcrypt-1.8.0/cipher/rijndael-armv8-aarch32-ce.S:1166:
> Error: selected processor does not support `rbit r8,lr' in ARM mode
> | ../../libgcrypt-1.8.0/cipher/rijndael-armv8-aarch32-ce.S:1166:
> Error: selected processor does not support `rbit r9,r9' in ARM mode
> | ../../libgcrypt-1.8.0/cipher/rijndael-armv8-aarch32-ce.S:1166:
> Error: selected processor does not support `rbit r10,r10' in ARM mode
> | ../../libgcrypt-1.8.0/cipher/rijndael-armv8-aarch32-ce.S:1166:
> Error: selected processor does not support `rbit r11,r11' in ARM mode
> | ../../libgcrypt-1.8.0/cipher/rijndael-armv8-aarch32-ce.S:1166:
> Error: selected processor does not support `rbit r8,lr' in ARM mode
> | ../../libgcrypt-1.8.0/cipher/rijndael-armv8-aarch32-ce.S:1167:
> Error: selected processor does not support `rbit r8,lr' in ARM mode
> | ../../libgcrypt-1.8.0/cipher/rijndael-armv8-aarch32-ce.S:1167:
> Error: selected processor does not support `rbit r9,r9' in ARM mode
> ...(snip)...
>
> I googled about this problem then I found the clue at here.
> https://mail-index.netbsd.org/pkgsrc-bugs/2017/08/01/msg062410.html
>
> I thought it fixed at libcrypt_1.8.1.
>
> I tried update to 1.8.1. It seems fine.
> So I suggest the libgcrypt updating for 1.8.1.
It may be too late to update  as we are in the stabilization phase of
the next release.
>
> By the way, I created the patch for this problem.
The is great and much appreciated.

> But I am not sure, where to send to this patch?
Yes it is a bit confusing and we should revisit the documentation.
> I could not found the guidelines of contributing [meta].
> I should send to OE-Core's ML? or  here directly?

The oe-core ML is the appropriate place.


>
> And, Would you let me know what strings of options to git send-email I
> should to set?
if you want to us git send mail, I use the following.

git send-email -1 -M --to  openembedded-core at lists.openembedded.org
--subject-prefix=PATCH

regards,
Armin

> Thanks.