From: Bodo Stroesser <bstroesser@fujitsu-siemens.com>
To: user-mode-linux-devel@lists.sourceforge.net
Cc: Jeff Dike <jdike@addtoit.com>, BlaisorBlade <blaisorblade_spam@yahoo.it>
Subject: [uml-devel] Unknown symbols
Date: Fri, 22 Oct 2004 21:16:07 +0200 [thread overview]
Message-ID: <41795C77.1070101@fujitsu-siemens.com> (raw)
Building 2.6.9 with vsyscall, I got problems with unknown symbols, e.g:
ext3: Unknown symbol vsyscall_end
ext3: Unknown symbol vsyscall_ehdr
for (almost) all modules, my current config uses.
The same problem exists for "end_iomem", but in the modules xfs.ko and ntfs.ko only.
I tried to fix that for the vsyscall_xxx in arch/um/os-Linux/elf_aux.c. I inserted
EXPORT_SYMBOLS for them, but it failed to compile, because it's not possible to
include "linux/module.h" in this user-code module.
What should I do to fix this? Move the variables to a kernel-source-file?
Or moving the EXPORTs only? To what file do you think that it should be moved?
For end_iomem inserting a EXPORT_SYMBOLS in arch/um/kernel/um_arch.c seems to be
enough.
Bodo
-------------------------------------------------------
This SF.net email is sponsored by: IT Product Guide on ITManagersJournal
Use IT products in your business? Tell us what you think of them. Give us
Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more
http://productguide.itmanagersjournal.com/guidepromo.tmpl
_______________________________________________
User-mode-linux-devel mailing list
User-mode-linux-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel
next reply other threads:[~2004-10-22 19:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-22 19:16 Bodo Stroesser [this message]
2004-10-23 1:16 ` [uml-devel] Re: Unknown symbols BlaisorBlade
2004-10-23 3:09 ` Jeff Dike
2004-10-25 14:10 ` Bodo Stroesser
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=41795C77.1070101@fujitsu-siemens.com \
--to=bstroesser@fujitsu-siemens.com \
--cc=blaisorblade_spam@yahoo.it \
--cc=jdike@addtoit.com \
--cc=user-mode-linux-devel@lists.sourceforge.net \
/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