From: gb spam <gbofspam@gmail.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Compiling Qemu + Accelerator on FC4
Date: Wed, 19 Oct 2005 19:33:13 -0400 [thread overview]
Message-ID: <6c3f5e6c0510191633q7c9bc051ie50fe833eb1e31@mail.gmail.com> (raw)
In-Reply-To: <435684D8.2050303@psislidell.com>
On 10/19/05, Rich Fought <rfought@psislidell.com> wrote:
> I'm using gcc32 and it gets pretty far, but runs out of luck here:
>
> make[1]: Entering directory `/home/rfought/qemu-0.7.2/kqemu'
> make -C /lib/modules/2.6.11-1.1369_FC4smp/build M=`pwd` modules
> make[2]: Entering directory `/usr/src/kernels/2.6.11-1.1369_FC4-smp-i686'
> CC [M] /home/rfought/qemu-0.7.2/kqemu/kqemu-linux.o
> cc1: invalid option `32'
> cc1: invalid option `arch=i686'
> cc1: invalid option `regparm=3'
> make[3]: *** [/home/rfought/qemu-0.7.2/kqemu/kqemu-linux.o] Error 1
> make[2]: *** [_module_/home/rfought/qemu-0.7.2/kqemu] Error 2
> make[2]: Leaving directory `/usr/src/kernels/2.6.11-1.1369_FC4-smp-i686'
> make[1]: *** [kqemu.ko] Error 2
> make[1]: Leaving directory `/home/rfought/qemu-0.7.2/kqemu'
> make: *** [all] Error 2
I have no problem compiling on FC4. Have never worked out exactly how
to use gcc32 "officially", but would be happy to be enlightened, and
have ended up with a hack, but the following works for me:
tar zxvf qemu-0.7.2.tar.gz
cd qemu-0.7.2
tar zxvf ../kqemu-0.7.2.tar.gz
./configure
perl -pi -e 's/=gcc/=gcc32/g' config-host.mak
make
next prev parent reply other threads:[~2005-10-19 23:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-19 17:39 [Qemu-devel] Compiling Qemu + Accelerator on FC4 Rich Fought
2005-10-19 23:33 ` gb spam [this message]
2005-10-20 16:21 ` Rich Fought
2005-10-20 18:44 ` André Braga
2005-10-20 19:39 ` Rich Fought
2005-10-21 13:07 ` Jan Marten Simons
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=6c3f5e6c0510191633q7c9bc051ie50fe833eb1e31@mail.gmail.com \
--to=gbofspam@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).