From: Jan Kiszka <jan.kiszka@siemens.com>
To: Nikola Ciprich <extmaillist@linuxbox.cz>
Cc: kvm <kvm@vger.kernel.org>,
"nikola.ciprich@linuxbox.cz" <nikola.ciprich@linuxbox.cz>
Subject: Re: [ANNOUNCE] kvm-kmod-2.6.36
Date: Mon, 25 Oct 2010 11:08:29 +0200 [thread overview]
Message-ID: <4CC5490D.9030609@siemens.com> (raw)
In-Reply-To: <20101025075639.GB10936@pcnci.linuxbox.cz>
Am 25.10.2010 09:56, Nikola Ciprich wrote:
> hmm,
> seems to be regression between kvm-kmod-2.6.35-rc3 and kvm-kmod-2.6.35,
> namely this snippet:
> --- kvm-kmod-2.6.35-rc3/configure 2010-06-24 19:49:35.000000000 +0200
> +++ kvm-kmod-2.6.35.6/configure 2010-10-01 11:30:03.000000000 +0200
> @@ -89,7 +89,7 @@
> kerneldir=$(cd $kerneldir; pwd)
>
> # see if we have split build and source directories
> -if [ -d "$kerneldir/include2" -o -L "$kerneldir/source" ]; then
> +if [ ! -d "$kerneldir/Kbuild" ]; then
> kernelsourcedir=$kerneldir/source
> if [ ! -L "$kernelsourcedir" ]; then
> kernelsourcedir=${kerneldir%/build*}/source
>
> n.
Oops, small but obviously fatal copy&paste mistake. Does this solve
your issue?
diff --git a/configure b/configure
index 4a37883..e37f5ff 100755
--- a/configure
+++ b/configure
@@ -89,7 +89,7 @@ arch=${arch%%-*}
kerneldir=$(cd $kerneldir; pwd)
# see if we have split build and source directories
-if [ ! -d "$kerneldir/Kbuild" ]; then
+if [ ! -e "$kerneldir/Kbuild" ]; then
kernelsourcedir=$kerneldir/source
if [ ! -L "$kernelsourcedir" ]; then
kernelsourcedir=${kerneldir%/build*}/source
Jan
--
Siemens AG, Corporate Technology, CT T DE IT 1
Corporate Competence Center Embedded Linux
next prev parent reply other threads:[~2010-10-25 9:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-21 11:48 [ANNOUNCE] kvm-kmod-2.6.36 Jan Kiszka
2010-10-25 6:47 ` Nikola Ciprich
2010-10-25 7:56 ` Nikola Ciprich
2010-10-25 9:08 ` Jan Kiszka [this message]
2010-10-25 9:45 ` Nikola Ciprich
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=4CC5490D.9030609@siemens.com \
--to=jan.kiszka@siemens.com \
--cc=extmaillist@linuxbox.cz \
--cc=kvm@vger.kernel.org \
--cc=nikola.ciprich@linuxbox.cz \
/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.