From: paolo pedaletti <paolo.pedaletti@gmail.com>
To: unlisted-recipients:; (no To-header on input)
Cc: kvm@vger.kernel.org
Subject: Re: Fwd: how to compile kvm 64 bit
Date: Fri, 05 Dec 2008 09:27:10 +0100 [thread overview]
Message-ID: <4938E5DE.4040004@gmail.com> (raw)
In-Reply-To: <aa2a0fc0812040841n72b4543lbb2db388c481d4bc@mail.gmail.com>
Ciao Malinka,
> your -mcpu=i686 specifically tells gcc to compile for 32-bit cpu you
> need to use something like
> -march=k8 or -mtune=k8 usually
ok, I can understand it, but I thought that it was enough to run
./compile
to obtain the correct Makefile with the right cpu-option
>> root@kvm1:/usr/src/kvm-79# ./configure
>> Source path /usr/src/kvm-79/qemu
>> C compiler gcc
>> Host C compiler gcc
>> ARCH_CFLAGS -m64
>> make make
>> install install
>> host CPU x86_64
>> host big endian no
>> target list x86_64-softmmu
so ./compile detect the right cpu/options
>> root@kvm1:/usr/src/kvm-79# make
>> make -C libkvm
>> make[1]: Entering directory `/usr/src/kvm-79/libkvm'
>> gcc -march=i686 -mcpu=i686 -malign-functions=4 -O2 -m64
>> -D__x86_64__ -MMD -MF ./.libkvm-x86.d -g -fomit-frame-pointer -Wall
>> -fno-stack-protector -I /usr/src/kvm-79/kernel/include -c -o
>> libkvm-x86.o libkvm-x86.c
but the Makefile is wrong
do I do something wrong?
Is it necessary to do something different?
thank you
--
Paolo Pedaletti
next prev parent reply other threads:[~2008-12-05 8:27 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-04 15:24 how to compile kvm 64 bit paolo pedaletti
2008-12-04 16:31 ` Charles Duffy
2008-12-05 8:15 ` paolo pedaletti
[not found] ` <aa2a0fc0812040839o513aa4edqbb07f8b88d140322@mail.gmail.com>
2008-12-04 16:41 ` Fwd: " Malinka Rellikwodahs
2008-12-05 8:27 ` paolo pedaletti [this message]
2008-12-05 16:09 ` Hollis Blanchard
2008-12-07 0:17 ` Paolo Pedaletti
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=4938E5DE.4040004@gmail.com \
--to=paolo.pedaletti@gmail.com \
--cc=kvm@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.