From: Sam Ravnborg <sam@ravnborg.org>
To: linux-kbuild@vger.kernel.org
Subject: How to avoid "version generation failed" warning?
Date: Sat, 23 Mar 2024 14:14:07 +0100 [thread overview]
Message-ID: <20240323131407.GA897267@ravnborg.org> (raw)
Hi all.
When building sparc32 allmodconfig I see a lot of warnings like these:
WARNING: modpost: EXPORT symbol "empty_zero_page" [vmlinux] version generation failed, symbol will not be versioned.
Is "empty_zero_page" prototyped in <asm/asm-prototypes.h>?
WARNING: modpost: EXPORT symbol "__udelay" [vmlinux] version generation failed, symbol will not be versioned.
Is "__udelay" prototyped in <asm/asm-prototypes.h>?
WARNING: modpost: EXPORT symbol "__ndelay" [vmlinux] version generation failed, symbol will not be versioned.
Is "__ndelay" prototyped in <asm/asm-prototypes.h>?
WARNING: modpost: EXPORT symbol "__ashldi3" [vmlinux] version generation failed, symbol will not be versioned.
Is "__ashldi3" prototyped in <asm/asm-prototypes.h>?
WARNING: modpost: EXPORT symbol "__ashrdi3" [vmlinux] version generation failed, symbol will not be versioned.
Is "__ashrdi3" prototyped in <asm/asm-prototypes.h>?
WARNING: modpost: EXPORT symbol "__lshrdi3" [vmlinux] version generation failed, symbol will not be versioned.
Is "__lshrdi3" prototyped in <asm/asm-prototypes.h>?
WARNING: modpost: "__udelay" [kernel/locking/locktorture.ko] has no CRC!
WARNING: modpost: "__udelay" [kernel/rcu/rcutorture.ko] has no CRC!
WARNING: modpost: "__udelay" [kernel/rcu/rcuscale.ko] has no CRC!
WARNING: modpost: "__udelay" [kernel/rcu/refscale.ko] has no CRC!
WARNING: modpost: "__ndelay" [kernel/rcu/refscale.ko] has no CRC!
WARNING: modpost: "__udelay" [kernel/time/test_udelay.ko] has no CRC!
WARNING: modpost: "__udelay" [kernel/scftorture.ko] has no CRC!
WARNING: modpost: "__ashrdi3" [fs/quota/quota_tree.ko] has no CRC!
WARNING: modpost: "__ashldi3" [fs/ext4/ext4.ko] has no CRC!
...
I already tried to add the prototypes to asm/asm-prototypes.h - but this
did not have any effect.
Module.symvers extract:
0x00000000 empty_zero_page vmlinux EXPORT_SYMBOL
0xf7370f56 system_state vmlinux EXPORT_SYMBOL
0xbea5ff1e static_key_initialized vmlinux EXPORT_SYMBOL_GPL
0xc2e587d1 reset_devices vmlinux EXPORT_SYMBOL
0xba497f13 loops_per_jiffy vmlinux EXPORT_SYMBOL
0x05cb9b5c init_uts_ns vmlinux EXPORT_SYMBOL_GPL
0xa2b7a1de init_task vmlinux EXPORT_SYMBOL
0x00000000 __udelay vmlinux EXPORT_SYMBOL
0x00000000 __ndelay vmlinux EXPORT_SYMBOL
Any hints what to do to fix these warnings would be appreciated.
My motivation to fix them is to get rid of the noise while doing
allmodconfig builds.
Sam
next reply other threads:[~2024-03-23 13:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-23 13:14 Sam Ravnborg [this message]
2024-03-23 15:03 ` How to avoid "version generation failed" warning? Sam Ravnborg
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=20240323131407.GA897267@ravnborg.org \
--to=sam@ravnborg.org \
--cc=linux-kbuild@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 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.