All of lore.kernel.org
 help / color / mirror / Atom feed
From: Miaohe Lin <linmiaohe@huawei.com>
To: Borislav Petkov <bp@alien8.de>
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: Mon, 9 Jan 2023 09:48:50 +0800	[thread overview]
Message-ID: <08115444-73a3-b9b0-dbeb-2a0cf374290e@huawei.com> (raw)
In-Reply-To: <Y7lSZerjPghqllWp@zn.tnic>

On 2023/1/7 19:07, Borislav Petkov wrote:
> On Sat, Jan 07, 2023 at 10:10:18AM +0800, Miaohe Lin wrote:
>> And I cloned the code from https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git. It's a
> 
> No, please read my mail properly:
> 
> "What is that compiler you're using? Where did you get the package from? Does it
> have some out-of-tree patches in it?"
> 
> I'm not asking you about the kernel but the *compiler*!

Oh, sorry, I miss-read that. My compiler is gcc-7.3.0 which contains many in-house codes from our company
in it. That might matters. Thanks a lot for your guidance. :)

Thanks,
Miaohe Lin

  reply	other threads:[~2023-01-09  1:48 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
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 [this message]
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=08115444-73a3-b9b0-dbeb-2a0cf374290e@huawei.com \
    --to=linmiaohe@huawei.com \
    --cc=bp@alien8.de \
    --cc=dave.hansen@linux.intel.com \
    --cc=hpa@zytor.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.