From: Grant Edwards <grant.b.edwards@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] Re: kernel compile error: arch/x86/entry/thunk_64.o: warning
Date: Tue, 2 Nov 2021 17:13:16 -0000 (UTC) [thread overview]
Message-ID: <slrrjc$o4m$1@ciao.gmane.io> (raw)
In-Reply-To: 7bdf7dd7-d282-78c2-0694-791bfcb6990a@sys-concept.com
On 2021-11-02, thelma@sys-concept.com <thelma@sys-concept.com> wrote:
> On 11/2/21 10:52 AM, thelma@sys-concept.com wrote:
>> I'm trying to enable (NFTS) file support in my kernel: 5.4.80
>> Disabled:
>> - [ ] NTFS write support
>>
>> Enabled:
>> <*> FUSE (Filesystem in Userspace) support
>>
>> When I try to compile the kernel I get an error message:
>> ...
>> AS arch/x86/entry/entry_64.o
>> AS arch/x86/entry/thunk_64.o
>> arch/x86/entry/thunk_64.o: warning: objtool: missing symbol table
>> make[2]: *** [scripts/Makefile.build:348: arch/x86/entry/thunk_64.o] Error 1
>> make[2]: *** Deleting file 'arch/x86/entry/thunk_64.o'
>> make[1]: *** [scripts/Makefile.build:500: arch/x86/entry] Error 2
>> make: *** [Makefile:1729: arch/x86] Error 2
>
> It seems to be related to this issue:
> https://lkml.org/lkml/2021/1/28/339
>
> by my kernel is 5.4.80 and I still have same problem
Did you try doing a "make clean" before building the kernel? I believe
I've sometimes had problems in the past with the following sequence:
1. Build kernel from sources
2. Upgrade gcc and/or binutils
3. Make minor change to kernel .config file
4. Do a "make" of the kernel
If you do a make clean between 3 & 4, it seems to avoid problems
caused by doing a build with "mixed" gcc or binutils versions.
--
Grant
next prev parent reply other threads:[~2021-11-02 17:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-02 16:52 [gentoo-user] kernel compile error: arch/x86/entry/thunk_64.o: warning thelma
2021-11-02 17:04 ` thelma
2021-11-02 17:13 ` Grant Edwards [this message]
2021-11-02 17:28 ` [gentoo-user] " thelma
2021-11-02 21:17 ` thelma
2021-11-02 21:20 ` Grant Edwards
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='slrrjc$o4m$1@ciao.gmane.io' \
--to=grant.b.edwards@gmail.com \
--cc=gentoo-user@lists.gentoo.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