Note, this is still happening. Using meta-mingw w/ gatesgarth to build, and
including libgcrypt I get the same failure. The failure resolves with
"--disable-amd64-as-feature-detection".
Looking at the code, I don't really understand it, but there are some lines
after that which may be more indicative of the actual error:
../../libgcrypt-1.8.6/cipher/rijndael.c: In function 'do_encrypt':
../../libgcrypt-1.8.6/cipher/rijndael-tables.h:103:24: error: expected ']'
before '.' token
103 | #define encT enc_tables.T
| ^
../../libgcrypt-1.8.6/cipher/rijndael.c:775:20: note: in expansion of macro
'encT'
775 | [encT] "r" (encT)
| ^~~~
../../libgcrypt-1.8.6/cipher/rijndael.c:776:17: error: undefined named operand
'encT'
776 | : "cc", "memory", "r8", "r9", "r10", "r11");
| ^
I can't find any difference in generated content anywhere, only that the
function (.c) that is failing seems to have a comments it's loading something
for use w/ a SysV style function:
# else
/* Call SystemV ABI function without storing non-volatile XMM registers,
* as target function does not use vector instruction sets. */
const void *key = ctx->keyschenc;
uintptr_t rounds = ctx->rounds;
uintptr_t ret;
asm volatile ("movq %[encT], %%r8\n\t"
"callq *%[ret]\n\t"
: [ret] "=a" (ret),
"+D" (key),
"+S" (bx),
"+d" (ax),
"+c" (rounds)
: "0" (_gcry_aes_amd64_encrypt_block),
As far as my configuration (all gatesgarth):
conf/bblayers.conf:
BBLAYERS ?= " \
/scratch2/mhatle/2021/sources/poky/meta \
/scratch2/mhatle/2021/sources/poky/meta-poky \
/scratch2/mhatle/2021/sources/meta-mingw \
/scratch2/mhatle/2021/sources/poky/../meta-xilinx/meta-xilinx-bsp \
/scratch2/mhatle/2021/sources/poky/../meta-xilinx-tools \
/scratch2/mhatle/2021/sources/poky/../meta-openembedded/meta-python \
/scratch2/mhatle/2021/sources/poky/../meta-openembedded/meta-oe \
"
DISTRO=nodistro MACHINE=zynqmp-generic SDKMACHINE=x86_64-mingw32 bitbake
nativesdk-libgcrypt
On 3/3/20 9:19 AM, Joshua Watt wrote:
>
> On 2/25/20 1:32 PM, Mark Hatle wrote:
>>
>> On 2/25/20 12:36 PM, Adrian Bunk wrote:
>>> On Tue, Feb 25, 2020 at 12:02:14PM -0600, Mark Hatle wrote:
>>>> amd64 optimization when using with mingw32 sometimes results in:
>>>>
>>>> | ../../libgcrypt-1.8.4/cipher/rijndael-tables.h:103:24: error: expected
>>>> ']' before '.' token
>>>> | 103 | #define encT enc_tables.T
>>>> ...
>>> Please send a complete build log, this looks like a parallel build
>>> failure where some .c is compiled before some header it uses is
>>> fully generated (or something similar).
>> I'll reply with a private email to where you can get a copy of the build
>> directory.
>>
>>>> --- a/recipes-support/libgcrypt/libgcrypt_%.bbappend
>>>> +++ b/recipes-support/libgcrypt/libgcrypt_%.bbappend
>>>> @@ -1,3 +1,4 @@
>>>> +EXTRA_OECONF_append_mingw32 = " --disable-amd64-as-feature-detection"
>>>> ...
>>> I assume PARALLEL_MAKE = "" would also work instead?
>> I tried this and it didn't appear to make a difference. I only see the
>> problem
>> when building for mingw32.
>
> Did we ever figure out what was causing this? It does appear to be some
> sort of race condition at the moment, and I'm surprised we haven't seen
> it on the autobuilder (we have pretty good test coverage for meta-mingw
> there).
>
>>
>> I've never seen any issues for any other SDK target.
>>
>> --Mark
>>
>>> cu
>>> Adrian
>>>
>>>
>>>
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#51796): https://lists.yoctoproject.org/g/yocto/message/51796
Mute This Topic: https://lists.yoctoproject.org/mt/71538286/21656
Group Owner: [email protected]
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub
[[email protected]]
-=-=-=-=-=-=-=-=-=-=-=-
