From: Cyrill Gorcunov <gorcunov@gmail.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: linux-kernel@vger.kernel.org, mingo@redhat.com, hpa@zytor.com,
heil@terminal-consulting.de, penberg@kernel.org,
tglx@linutronix.de, linux-tip-commits@vger.kernel.org,
KVM devel mailing list <kvm@vger.kernel.org>
Subject: Re: [tip:tools/kvm] kvm tools: Add conditional compilation of symbol resolving
Date: Sun, 22 May 2011 15:00:41 +0400 [thread overview]
Message-ID: <4DD8ECD9.6080300@gmail.com> (raw)
In-Reply-To: <20110522105816.GA13373@elte.hu>
On 05/22/2011 02:58 PM, Ingo Molnar wrote:
>
> * tip-bot for Cyrill Gorcunov <gorcunov@gmail.com> wrote:
>
>> diff --git a/tools/perf/feature-tests.mak b/tools/kvm/config/feature-tests.mak
>> similarity index 83%
>> copy from tools/perf/feature-tests.mak
>> copy to tools/kvm/config/feature-tests.mak
>
> Btw, now that we have feature-tests.mak it would be nice to populate the checks
> for the various assumptions.
>
> One i recently ran into on a new box where i tried to install tools/kvm was:
>
> In file included from /usr/include/features.h:387:0,
> from /usr/include/unistd.h:26,
> from include/kvm/util.h:12,
> from bios/e820.c:5:
> /usr/include/gnu/stubs.h:7:27: fatal error: gnu/stubs-32.h: No such file or directory
> compilation terminated.
> make: *** [bios/bios-rom.bin] Error 1
>
> that's a dependency on glibc-dev[el].
>
> Thanks,
>
> Ingo
Ouch. I've been hitting this lack of gnu/stubs-32.h on Fedora 15 too and eventually
I had to install i686 packages for devel. I'll try to resolve this issue tonight, I
suppose it's not absolutely urgent, right?
--
Cyrill
prev parent reply other threads:[~2011-05-22 11:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <tip-c474e3fec70bcacd5b24a24838c653e5a13e7b58@git.kernel.org>
2011-05-22 10:58 ` [tip:tools/kvm] kvm tools: Add conditional compilation of symbol resolving Ingo Molnar
2011-05-22 11:00 ` Ingo Molnar
2011-05-22 11:02 ` Cyrill Gorcunov
2011-05-22 11:00 ` Cyrill Gorcunov [this message]
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=4DD8ECD9.6080300@gmail.com \
--to=gorcunov@gmail.com \
--cc=heil@terminal-consulting.de \
--cc=hpa@zytor.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=mingo@redhat.com \
--cc=penberg@kernel.org \
--cc=tglx@linutronix.de \
/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.