From: Bhaskar Chowdhury <unixbhaskar@gmail.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Chris Clayton <chris2553@googlemail.com>,
LKML <linux-kernel@vger.kernel.org>,
stable@vger.kernel.org
Subject: Re: linux-5.10.11 build failure
Date: Thu, 28 Jan 2021 15:30:08 +0530 [thread overview]
Message-ID: <YBKLKEixoQ0sQ7yE@Slackware> (raw)
In-Reply-To: <YBKFNUp5WYtdg9pE@kroah.com>
[-- Attachment #1: Type: text/plain, Size: 1504 bytes --]
On 10:34 Thu 28 Jan 2021, Greg Kroah-Hartman wrote:
>On Thu, Jan 28, 2021 at 09:17:10AM +0000, Chris Clayton wrote:
>> Hi,
>>
>> Building 5.10.11 fails on my (x86-64) laptop thusly:
>>
>> ..
>>
>> AS arch/x86/entry/thunk_64.o
>> CC arch/x86/entry/vsyscall/vsyscall_64.o
>> AS arch/x86/realmode/rm/header.o
>> CC arch/x86/mm/pat/set_memory.o
>> CC arch/x86/events/amd/core.o
>> CC arch/x86/kernel/fpu/init.o
>> CC arch/x86/entry/vdso/vma.o
>> CC kernel/sched/core.o
>> arch/x86/entry/thunk_64.o: warning: objtool: missing symbol for insn at offset 0x3e
>>
>> AS arch/x86/realmode/rm/trampoline_64.o
>> make[2]: *** [scripts/Makefile.build:360: arch/x86/entry/thunk_64.o] Error 255
>> make[2]: *** Deleting file 'arch/x86/entry/thunk_64.o'
>> make[2]: *** Waiting for unfinished jobs....
>>
>> ..
>>
>> Compiler is latest snapshot of gcc-10.
>>
>> Happy to test the fix but please cc me as I'm not subscribed
>
>Can you do 'git bisect' to track down the offending commit?
>
>And what exact gcc version are you using?
>
>thanks,
>
>greg k-h
Okay, as far as the kernel goes ...I have built the 5.10.11 kernel on 5
different distros (Gentoo, Slackware, Debian, Arch and Opensuse-Tumbleweed)
from yesterday ...simple compile with little option tweak ..nothing breaks.
Probably, good fortune of mine! :)
There is "Pathetically and awfully wrote" mundane bash script do the stuff for
me.
~Bhaskar
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2021-01-28 10:01 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-28 9:17 linux-5.10.11 build failure Chris Clayton
2021-01-28 9:34 ` Greg Kroah-Hartman
2021-01-28 10:00 ` Bhaskar Chowdhury [this message]
2021-01-28 10:05 ` Chris Clayton
-- strict thread matches above, loose matches on Subject: below --
2021-01-28 10:19 torvic9
2021-01-28 11:24 Thomas Backlund
2021-01-28 13:38 ` Chris Clayton
2021-01-28 14:41 ` Greg Kroah-Hartman
2021-01-28 15:36 ` Chris Clayton
2021-01-28 16:00 ` Josh Poimboeuf
[not found] ` <YBPfQXSrz+P3TOZf@kroah.com>
[not found] ` <f9f8e2c9-3690-52f3-8d96-4f2b735dd6bd@googlemail.com>
[not found] ` <YBPtAYK1Nj/WpiTo@kroah.com>
[not found] ` <20210129151423.rsyubljbrzxicleq@treble>
2021-02-01 8:59 ` Chris Clayton
2021-02-01 9:37 ` Greg Kroah-Hartman
2021-01-28 15:52 ` Josh Poimboeuf
2021-01-28 16:03 ` Chris Clayton
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=YBKLKEixoQ0sQ7yE@Slackware \
--to=unixbhaskar@gmail.com \
--cc=chris2553@googlemail.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=stable@vger.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox