On 03/06/2013 06:05 PM, Saravanan Shanmugham (sarvi) wrote:
I am using the following configure to minimize dependencies and avoid
anything unrelated to getting a libvirt remote client going. Turned on —with-remote=yes,
--with-python=yes —with-rhel5-api=yes
[your mailer doesn't wrap long lines, which makes it harder to read]
./configure --with-python --with-apparmor=no ...
You can also spell --without-apparmor instead of --with-apparmor=no (and
so forth). Many of those options are automatically disabled if you use
--without-libvirtd, or if a particular library is detected as not
installed; it might be worth minimizing your configure line to prune
options that don't make a difference. The resulting summary printed at
the end of the configure run will show you which pieces were detected as
enabled or disabled.
I am getting the following error/warnings.
CC libvirt_util_la-virfile.lo
In file included from util/virfile.c:36:
/usr/include/linux/loop.h:31:2: #error "Wrong dev_t in loop.h"
You'll have to debug this one yourself - something in your old system
header doesn't like the order in which other files were included.
In file included from util/virfile.c:42:
util/viralloc.h:67: warning: declaration of 'remove' shadows a global
declaration
/usr/include/stdio.h:154: warning: shadowed declaration is here
This one's a trivial fix. In fact, it looks like we've fixed a similar
problem for other platforms before, given that commit de53eff fixed the
same problem for virShrinkN. I'll push this shortly under the trivial rule.
diff --git i/src/util/viralloc.h w/src/util/viralloc.h
index 3c97a58..6f46d0b 100644
--- i/src/util/viralloc.h
+++ w/src/util/viralloc.h
@@ -64,7 +64,7 @@ int virInsertElementsN(void *ptrptr, size_t size,
size_t at, size_t *countptr,
bool clearOriginal, bool inPlace)
ATTRIBUTE_RETURN_CHECK ATTRIBUTE_NONNULL(1) ATTRIBUTE_NONNULL(4);
int virDeleteElementsN(void *ptrptr, size_t size, size_t at, size_t
*countptr,
- size_t remove, bool inPlace)
+ size_t toremove, bool inPlace)
ATTRIBUTE_NONNULL(1) ATTRIBUTE_NONNULL(4);
int virAllocVar(void *ptrptr,
size_t struct_size,
Finally, you mentioned using libvirt 1.0.2; you'll have similar issues
with 1.0.3, where you will have to backport patches yourself. For now,
you might want to try libvirt.git to automatically pick up fixes as they
get pushed; but I have no idea how well git worked in RHEL4.
--
Eric Blake eblake redhat com +1-919-301-3266
Libvirt virtualization library
http://libvirt.org