From: Borislav Petkov <bp@alien8.de>
To: Miaohe Lin <linmiaohe@huawei.com>
Cc: "x86@kernel.org" <x86@kernel.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
"tglx@linutronix.de" <tglx@linutronix.de>,
"mingo@redhat.com" <mingo@redhat.com>,
Dave Hansen <dave.hansen@linux.intel.com>,
hpa@zytor.com
Subject: Re: [BUG Report] undefined reference to `convert_to_fxsr'
Date: Fri, 30 Dec 2022 12:16:38 +0100 [thread overview]
Message-ID: <Y67IlthBqaX69RwN@zn.tnic> (raw)
In-Reply-To: <e041533c-4005-b9bc-3985-02224985aa28@huawei.com>
On Fri, Dec 30, 2022 at 09:49:50AM +0800, Miaohe Lin wrote:
> Many thanks for doing this. :) But it seems it's not the matter of gcc
> version. Somewhat confused...
Put your .config somewhere outside your git repo, clean all build
artifacts and reset it properly by doing:
git reset --hard
git clean -dqfx
and then copy back the .config and see if you can still repro.
--
Regards/Gruss,
Boris.
https://people.kernel.org/tglx/notes-about-netiquette
next prev parent reply other threads:[~2022-12-30 11:16 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-28 12:31 [BUG Report] undefined reference to `convert_to_fxsr' Miaohe Lin
2022-12-28 12:39 ` Borislav Petkov
2022-12-29 1:50 ` Miaohe Lin
2022-12-29 15:17 ` Borislav Petkov
2022-12-30 1:49 ` Miaohe Lin
2022-12-30 11:16 ` Borislav Petkov [this message]
2023-01-03 3:05 ` Miaohe Lin
2023-01-05 23:14 ` Borislav Petkov
2023-01-07 2:10 ` Miaohe Lin
2023-01-07 11:07 ` Borislav Petkov
2023-01-09 1:48 ` Miaohe Lin
2023-01-09 11:49 ` Borislav Petkov
2023-01-09 12:32 ` Miaohe Lin
2023-01-09 17:09 ` Nathan Chancellor
2023-01-10 1:13 ` Miaohe Lin
2022-12-30 12:20 ` Borislav Petkov
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=Y67IlthBqaX69RwN@zn.tnic \
--to=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=hpa@zytor.com \
--cc=linmiaohe@huawei.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=tglx@linutronix.de \
--cc=x86@kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.