From: "Daniel Rosenthal" <danielrosenthal@acm.org>
To: "Grant Coady" <gcoady.lk@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: linux object file containing all kernel symbols and suitable for userspace linking?
Date: Sun, 28 Sep 2008 03:22:48 -0400 [thread overview]
Message-ID: <4b6fba110809280022x4e10a068s479dd3d2fd67e9ba@mail.gmail.com> (raw)
In-Reply-To: <4httd4pt37d715nqfvge2fau7nahbq6u3a@4ax.com>
On Sat, Sep 27, 2008 at 11:13 PM, Grant Coady wrote:
> There's a vmlinux.o in top-level directory after a kernel compile, is
> that what you're after?
It's looks close, but it seems to be missing some symbols. Below is
an excerpt of some of the some of the error messages that come up when
trying to link vmlinux.o to another object file. It looks like all
the binary layout related symbols are missing, and jiffies also.
How/when are these symbols normally linked into the final kernel
image?
Daniel
...
/usr/src/linux/vmlinux.o: In function `sched_clock':
/usr/src/linux/kernel/sched.c:80: undefined reference to `jiffies'
/usr/src/linux/vmlinux.o: In function `__might_sleep':
/usr/src/linux/kernel/sched.c:7478: undefined reference to `jiffies'
/usr/src/linux/kernel/sched.c:7480: undefined reference to `jiffies'
/usr/src/linux/vmlinux.o: In function `in_sched_functions':
/usr/src/linux/kernel/sched.c:7289: undefined reference to `__sched_text_start'
/usr/src/linux/kernel/sched.c:7289: undefined reference to `__sched_text_end'
/usr/src/linux/vmlinux.o: In function `print_cpu':
/usr/src/linux/kernel/sched_debug.c:174: undefined reference to `jiffies'
/usr/src/linux/kernel/sched_debug.c:174: undefined reference to `jiffies'
/usr/src/linux/vmlinux.o: In function `printk_timed_ratelimit':
/usr/src/linux/kernel/printk.c:1343: undefined reference to `jiffies'
/usr/src/linux/kernel/printk.c:1344: undefined reference to `jiffies'
/usr/src/linux/vmlinux.o: In function `zap_locks':
/usr/src/linux/kernel/printk.c:550: undefined reference to `jiffies'
/usr/src/linux/vmlinux.o:/usr/src/linux/kernel/printk.c:550: more
undefined references to `jiffies' follow
...
/usr/src/linux/vmlinux.o: In function `mem_init':
/usr/src/linux/arch/x86/mm/init_32.c:603: undefined reference to `_text'
/usr/src/linux/arch/x86/mm/init_32.c:605: undefined reference to `__init_end'
/usr/src/linux/arch/x86/mm/init_32.c:605: undefined reference to `__init_begin'
/usr/src/linux/arch/x86/mm/init_32.c:623: undefined reference to `_text'
/usr/src/linux/arch/x86/mm/init_32.c:623: undefined reference to `__init_end'
/usr/src/linux/arch/x86/mm/init_32.c:623: undefined reference to `__init_begin'
/usr/src/linux/vmlinux.o: In function `is_kernel_text':
/usr/src/linux/arch/x86/mm/init_32.c:147: undefined reference to `__init_end'
/usr/src/linux/arch/x86/mm/init_32.c:147: undefined reference to `__init_end'
/usr/src/linux/vmlinux.o: In function `kernel_physical_mapping_init':
/usr/src/linux/arch/x86/mm/init_32.c:207: undefined reference to `__init_end'
/usr/src/linux/vmlinux.o: In function `page_writeback_init':
/usr/src/linux/mm/page-writeback.c:773: undefined reference to `jiffies'
...
next prev parent reply other threads:[~2008-09-28 7:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-28 2:57 Daniel Rosenthal
2008-09-28 3:13 ` Grant Coady
2008-09-28 7:22 ` Daniel Rosenthal [this message]
2008-09-28 14:06 ` Jeff Dike
2008-09-29 6:18 ` Daniel Rosenthal
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=4b6fba110809280022x4e10a068s479dd3d2fd67e9ba@mail.gmail.com \
--to=danielrosenthal@acm.org \
--cc=gcoady.lk@gmail.com \
--cc=linux-kernel@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
Powered by JetHome