[yocto] libgcrypt building fails for armv6 binaries.

[Yusuke Mitsuki]

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.

By the way, I created the patch for this problem.
But I am not sure, where to send to this patch?
I could not found the guidelines of contributing [meta].
I should send to OE-Core's ML? or  here directly??

And, Would you let me know what strings of options to git send-email I
should to set?

Thanks.