From: Remco Treffkorn <remco@rvt.com>
To: <linuxppc-dev@lists.linuxppc.org>
Subject: Symbol versioning problem
Date: Wed, 10 Jul 2002 14:29:39 -0700 [thread overview]
Message-ID: <200207101429.39539.remco@rvt.com> (raw)
I am compiling a recent benh kernel. After the build the depmod against
the System.map does not complain, but then, the symbols in it are not
versioned.
Booting the new kernel and depmodding against /proc/ksyms gives me
lots of unresolved symbols like:
depmod: *** Unresolved symbols in /lib/modules/2.4.19-rc1-ben0/kernel/fs/hfs/hfs.o
depmod: __out_of_line_bug
depmod: *** Unresolved symbols in /lib/modules/2.4.19-rc1-ben0/kernel/fs/smbfs/smbfs.o
depmod: zone_table
depmod: flush_dcache_page
Looking those up in /proc/ksyms gives the following:
c00168e4 __out_of_line_bug_R__ver___out_of_line_bug
c02b3e94 zone_table_R__ver_zone_table
c0011994 flush_dcache_page_R__ver_flush_dcache_page
So, instead of the hash we have the symbol name again.
Only very few symbols have this problem.
A quick look at the include files for versioning gave me a head ache ;-)
I don't have this problem with i386, I have not tried another gcc version, but upped
modutils to the latest. No dice
Here is what I have:
Linux io 2.4.19-rc1-ben0 #59 Wed Jul 10 12:06:33 PDT 2002 ppc unknown
Gnu C 2.95.4
Gnu make 3.79.1
util-linux 2.11f
mount 2.11g
modutils 2.4.16
e2fsprogs 1.26
reiserfsprogs 3.x.1a
PPP 2.4.1
Linux C Library 2.2.5
Dynamic linker (ldd) 2.2.5
Procps 2.0.7
Net-tools 1.60
Console-tools 0.3.3
Sh-utils 2.0.11
Modules Loaded dmasound_pmac i2c-keywest i2c-core dmasound_core soundcore
Cheers,
Remco
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next reply other threads:[~2002-07-10 21:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-10 21:29 Remco Treffkorn [this message]
2002-07-15 9:04 ` Symbol versioning problem Stefan Eletzhofer
2002-07-16 18:21 ` Remco Treffkorn
2002-07-16 19:12 ` Tom Rini
2002-07-16 23:21 ` Remco Treffkorn
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=200207101429.39539.remco@rvt.com \
--to=remco@rvt.com \
--cc=linuxppc-dev@lists.linuxppc.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;
as well as URLs for NNTP newsgroup(s).