From: Starsong Nemo <starsong.nemo@gmail.com>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] Can't build kqemu
Date: Mon, 25 Jul 2005 20:59:26 -0700 [thread overview]
Message-ID: <19ce66b10507252059b46e12c@mail.gmail.com> (raw)
Hi,
I tried to compile the new version of kqemu (0.7.1) and got a strange
message. The system is a brand-new Suse 9.3 install running kernel
2.6.11.4 (smp). Here's the bit that failed (qemu starting directory
is /home/tachyon/qemu/qcvs/qemu-0.7.1):
make[1]: Leaving directory `/home/tachyon/qemu/qcvs/qemu-0.7.1/mips-softmmu'
make -C kqemu
make[1]: Entering directory `/home/tachyon/qemu/qcvs/qemu-0.7.1/kqemu'
make -C /usr/src/linux M=`pwd` modules
make[2]: Entering directory `/usr/src/linux-2.6.11.4-20a'
CC [M] /home/tachyon/qemu/qcvs/qemu-0.7.1/kqemu/kqemu-linux.o
cp /home/tachyon/qemu/qcvs/qemu-0.7.1/kqemu/kqemu-mod-i386.o
/home/tachyon/qemu/qcvs/qemu-0.7.1/kqemu/kqemu-mod.o
LD [M] /home/tachyon/qemu/qcvs/qemu-0.7.1/kqemu/kqemu.o
Building modules, stage 2.
MODPOST
Warning: could not find
/home/tachyon/qemu/qcvs/qemu-0.7.1/kqemu/.kqemu-mod.o.cmd for
/home/tachyon/qemu/qcvs/qemu-0.7.1/kqemu/kqemu-mod.o
*** Warning: "__PAGE_KERNEL_EXEC"
[/home/tachyon/qemu/qcvs/qemu-0.7.1/kqemu/kqemu.ko] undefined!
CC /home/tachyon/qemu/qcvs/qemu-0.7.1/kqemu/kqemu.mod.o
LD [M] /home/tachyon/qemu/qcvs/qemu-0.7.1/kqemu/kqemu.ko
make[2]: Leaving directory `/usr/src/linux-2.6.11.4-20a'
make[1]: Leaving directory `/home/tachyon/qemu/qcvs/qemu-0.7.1/kqemu'
Running "make install" installs the regular qemu fine, but "modprobe
kqemu" results in either "Invalid module format" or "unresolved
symbols." This happens with both the stable (0.7.1 from the website)
and cvs versions.
Any idea what's wrong?
Thanks,
ss
reply other threads:[~2005-07-26 4:04 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=19ce66b10507252059b46e12c@mail.gmail.com \
--to=starsong.nemo@gmail.com \
--cc=qemu-devel@nongnu.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).