On Wed, Aug 04 2021 at 17:04, Rong A. Chen wrote:
> On 7/27/2021 10:52 PM, Dave Hansen wrote:
>> On 7/26/21 8:11 PM, kernel test robot wrote:
>>>>> sparc64-linux-gcc: error: unrecognized command-line option '-mxsave'
>>
>> Is there something else funky going on here? All of the "-mxsave" flags
>> that I can find are under checks for x86 builds, like:
>>
>> ifeq ($(CAN_BUILD_I386),1)
>> $(BINARIES_32): CFLAGS += -m32 -mxsave
>> ..
>>
>> I'm confused how we could have a sparc64 compiler (and only a sparc64
>> compiler) that would end up with "-mxsave" in CFLAGS.
>
> Hi Dave,
>
> We can reproduce the error and have no idea too, but we have disabled
> the test for selftests on non-x86 arch.
This smells like a host/target compiler mixup. Can you please make the
kernel build verbose with 'V=1' and provide the full build output?
Thanks,
tglx
