From: Scott Dudley <scott@telesoft.com>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] Redhat 9, 2.6.5 Kernel, and kqemu
Date: Mon, 31 Oct 2005 11:17:03 -0700 [thread overview]
Message-ID: <43665F9F.7020502@telesoft.com> (raw)
I'm trying to build/install kqemu on Redhat 9 running a 2.6.5 kernel.
Grabbed latest sources (0.7.2) for qemu and kqemu. Build doesn't appear
to generate the .ko module.
Here's my config:
scottspc.sunbelt.com: /usr/local/src/qemu-0.7.2 # sh CONFIGURE
Install prefix /usr/local
BIOS directory /usr/local/share/qemu
binary directory /usr/local/bin
Manual directory /usr/local/share/man
ELF interp prefix /usr/gnemul/qemu-%M
Source path /usr/local/src/qemu-0.7.2
C compiler gcc
Host C compiler gcc
make make
host CPU i386
host big endian no
target list i386-user
gprof enabled no
static build no
SDL support yes
SDL static link yes
mingw32 support no
Adlib support no
FMOD support no
kqemu support yes
KQEMU Linux module configuration:
kernel sources /usr/src/linux-2.6.5
kbuild type 2.6
Here's the output of the make:
scottspc.sunbelt.com: /usr/local/src/qemu-0.7.2 # make install
for d in i386-user; do \
make -C $d all || exit 1 ; \
done
make[1]: Entering directory `/usr/local/src/qemu-0.7.2/i386-user'
make[1]: Nothing to be done for `all'.
make[1]: Leaving directory `/usr/local/src/qemu-0.7.2/i386-user'
make -C kqemu
make[1]: Entering directory `/usr/local/src/qemu-0.7.2/kqemu'
make -C /usr/src/linux-2.6.5 M=`pwd` modules
make[2]: Entering directory `/usr/src/linux-2.6.5'
make[3]: `arch/i386/kernel/asm-offsets.s' is up to date.
CHK include/asm-i386/asm_offsets.h
Building modules, stage 2.
MODPOST
make[2]: Leaving directory `/usr/src/linux-2.6.5'
make[1]: Leaving directory `/usr/local/src/qemu-0.7.2/kqemu'
mkdir -p "/usr/local/bin"
install -m 755 -s qemu-img "/usr/local/bin"
mkdir -p "/usr/local/share/qemu"
install -m 644 pc-bios/bios.bin pc-bios/vgabios.bin \
pc-bios/vgabios-cirrus.bin \
pc-bios/ppc_rom.bin pc-bios/video.x \
pc-bios/proll.elf \
pc-bios/linux_boot.bin "/usr/local/share/qemu"
mkdir -p "/usr/local/share/doc/qemu"
install -m 644 qemu-doc.html qemu-tech.html "/usr/local/share/doc/qemu"
mkdir -p "/usr/local/share/man/man1"
install qemu.1 qemu-img.1 "/usr/local/share/man/man1"
mkdir -p "/usr/local/share/qemu/keymaps"
install -m 644 keymaps/da keymaps/en-gb keymaps/et keymaps/fr
keymaps/fr-ch keymaps/is keymaps/lt keymaps/modifiers keymaps/no
keymaps/pt-br keymaps/sv keymaps/ar keymaps/de keymaps/en-us
keymaps/fi keymaps/fr-be keymaps/hr keymaps/it keymaps/lv keymaps/nl
keymaps/pl keymaps/ru keymaps/th keymaps/common keymaps/de-ch
keymaps/es keymaps/fo keymaps/fr-ca keymaps/hu keymaps/ja keymaps/mk
keymaps/nl-be keymaps/pt keymaps/sl keymaps/tr
"/usr/local/share/qemu/keymaps"
for d in i386-user; do \
make -C $d install || exit 1 ; \
done
make[1]: Entering directory `/usr/local/src/qemu-0.7.2/i386-user'
install -m 755 -s qemu-i386 "/usr/local/bin"
make[1]: Leaving directory `/usr/local/src/qemu-0.7.2/i386-user'
cd kqemu ; ./install.sh
cp: cannot stat `kqemu.o': No such file or directory
What am I missing?
--
Regards,
Scott Dudley
next reply other threads:[~2005-10-31 18:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-31 18:17 Scott Dudley [this message]
2005-11-01 2:32 ` [Qemu-devel] Redhat 9, 2.6.5 Kernel, and kqemu Mulyadi Santosa
2005-11-04 0:05 ` Scott Dudley
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=43665F9F.7020502@telesoft.com \
--to=scott@telesoft.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).