All of lore.kernel.org
 help / color / mirror / Atom feed
From: Simon Gao <gao-g4dUTk+gKbW4mfPA/iJWtA@public.gmane.org>
To: kvm-devel <kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>
Subject: kvm-31 configure file bug
Date: Sat, 21 Jul 2007 10:52:26 -0700	[thread overview]
Message-ID: <46A247DA.7060503@schrodinger.com> (raw)

Hi,

I found there is a bug with configure file shipped with kvm-31. Here is
the part of configure file:

===============================
target_cpu() {
    if [[ $(uname -m) = i?86 ]]; then
       echo x86_64
    else
        uname -m
    fi
}
===============================

!?86 will match i386, i586 and i686. On my machine,  "uname -m" returns
i686, which is obviously a 32bit kernel. Assigning to x86_64 breaks kvm
and installs qemu-system-x86_64, instead of qemu.


After making a simple change as follow, kvm-31 compiles and installs as
expected on 32bit system.  qemu also woks.

===============================
target_cpu() {
    if [[ $(uname -m) = i?86 ]]; then
       #echo x86_64
       echo i386
    else
        uname -m
    fi
}
===============================

Looks like kvm-31 only compiles when target_cpu is i386 or x86_64. Under
other situations like i486, i585, i686, compiling kvm-31 will fail.  On
many machines, "uname -m" returns i586 or i686.

Simon

-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >>  http://get.splunk.com/

             reply	other threads:[~2007-07-21 17:52 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-21 17:52 Simon Gao [this message]
     [not found] ` <46A247DA.7060503-g4dUTk+gKbW4mfPA/iJWtA@public.gmane.org>
2007-07-22  7:56   ` kvm-31 configure file bug Avi Kivity
     [not found]     ` <46A30D96.5010606-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-07-22 20:19       ` Simon Gao
     [not found]         ` <46A3BBEF.2030400-g4dUTk+gKbW4mfPA/iJWtA@public.gmane.org>
2007-07-23  8:06           ` Avi Kivity
     [not found]             ` <46A46193.2060402-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-07-23 19:36               ` Simon Gao
     [not found]                 ` <46A50352.7060003-g4dUTk+gKbW4mfPA/iJWtA@public.gmane.org>
2007-07-25  3:18                   ` Avi Kivity

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=46A247DA.7060503@schrodinger.com \
    --to=gao-g4dutk+gkbw4mfpa/ijwta@public.gmane.org \
    --cc=kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.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.