kvm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Avi Kivity <avi@redhat.com>
To: Maik Hentsche <maik.hentsche@amd.com>
Cc: kvm@vger.kernel.org, Joerg Roedel <joerg.roedel@amd.com>
Subject: Re: [PATCH] kvm-userspace: fix module build with --kerneldir
Date: Wed, 26 Nov 2008 13:14:13 +0200	[thread overview]
Message-ID: <492D2F85.5050004@redhat.com> (raw)
In-Reply-To: <20081126115915.4cf3308d@siegfried>

Maik Hentsche wrote:
> Avi Kivity <avi@redhat.com> wrote:
>
>   
>> Can't the version be determined directly from kernedir itself?  e.g. 
>> kerneldir is /lib/modules/$version/build?
>>     
>
> How do you get $version if you are crosscompiling? In this case the
> usual way of asking uname doesn't work. Instead you somehow need to get
> the version of the kernel you're building for from the kernel source
> provided in --kerneldir. I don't know any better way than evaluating
> UTSRELEASE.
>   

If the user specified $kerneldir, it should be in the form 
/lib/modules/$version/build, no?  If so, then you can extract $version 
by removing the prefix and suffix from the string.

-- 
error compiling committee.c: too many arguments to function


  reply	other threads:[~2008-11-26 11:14 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-25 13:57 [PATCH] kvm-userspace: fix module build with --kerneldir Joerg Roedel
2008-11-26 10:42 ` Avi Kivity
2008-11-26 10:59   ` Maik Hentsche
2008-11-26 11:14     ` Avi Kivity [this message]
2008-11-26 12:14       ` Maik Hentsche
2008-11-26 16:03         ` Avi Kivity
2008-11-26 12:16       ` Jan Kiszka
2008-11-26 16:00         ` Avi Kivity
2008-11-27 14:15           ` Eduardo Habkost
2008-11-27 14:26             ` Avi Kivity
2008-12-01 14:28 ` Maik Hentsche
2008-12-09 15:02   ` Joerg Roedel
2008-12-10 10:06     ` 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=492D2F85.5050004@redhat.com \
    --to=avi@redhat.com \
    --cc=joerg.roedel@amd.com \
    --cc=kvm@vger.kernel.org \
    --cc=maik.hentsche@amd.com \
    /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).