Il giorno ven, 06/08/2010 alle 06.52 -0600, Eric Blake ha scritto:
>
> This says to nuke the distributed man page. Which means 'make && make
> clean && make' is once again requiring those extra tools.
>
I wanted to stay as close as possible to the original, since I know
people tend to be touchy
Il giorno mer, 24/02/2010 alle 09.23 -0700, Eric Blake ha scritto:
>
> Does this properly handle the case of 'no' or 'none required'? I
> think
> you need:
>
Gha you're right, not sure why I assumed that it used "c" for "none
required"
And yes I'm an overquoter in sh :P
>
--
Diego Elio Petten
Il giorno mer, 24/02/2010 alle 08.21 -0700, Eric Blake ha scritto:
> Just curious: Why the choice of AFX_, and not something like LV_ for libvirt?
Because I plan to finish this up and send it down to autoconf-archive
asap as it's not the first time I have to get something like this ;)
> The shell
Il giorno mer, 24/02/2010 alle 15.24 +, Richard W.M. Jones ha
scritto:
>
> The autoconf change looks fine, so ACK. However what platforms
> don't have dlopen in -ldl?
*BSD for instance
--
Diego Elio Pettenò — “Flameeyes”
http://blog.flameeyes.eu/
If you found a .asc file in this mail and
Il giorno mer, 24/02/2010 alle 14.21 +, Richard W.M. Jones ha
scritto:
>
> http://fedoraproject.org/wiki/Features/ChangeInImplicitDSOLinking
That definitely seems to be it, I've sent a small series of patches that
should handle that case properly, please let me know if there are
problems. So
Il giorno mer, 24/02/2010 alle 15.05 +0100, Jim Meyering ha scritto:
>
> That sounds reasonable, if we're guaranteed always to have a libdl.
> However, the fact that it's not needed on F12 suggests that we should
> be adding it only when necessary (hence a configure-time test).
I guess the probl
Il giorno ven, 12/02/2010 alle 13.29 +0100, Diego Elio Pettenò ha
scritto:
> Just checking for a windres tool might hit even on Linux systems when
> building for Linux (e.g.: when using Gentoo and having built binutils
> with
> multitarget support), and will then fail to link properly at the end
>
Il giorno sab, 23/01/2010 alle 16.32 -0700, Eric Blake ha scritto:
> Is there
> anyone that seriously falls in the latter category, of still wanting
> to
> _develop_ libvirt on RHEL-5?
The post is at worst two weeks old, you can easily find it in the
archives (search for my name in the page, I d
Il giorno sab, 23/01/2010 alle 15.47 -0700, Eric Blake ha scritto:
> Or is it too soon to expect
> all distros to have an automake that new pre-installed, and more
> effort
> be put into supporting automake 1.9.6 and autoconf 2.59 (those being
> the
> implicit minimum requirements due to the use of
Il giorno dom, 17/01/2010 alle 12.48 +, Daniel P. Berrange ha
scritto:
>
> .. one file for each logically indepdant block of m4 code from
> configure.ac
> Then, in the configure.ac file we'd just end up with a set of single
> line
> calls into these files loooking like
>
>From one point of vi
Il giorno dom, 17/01/2010 alle 13.22 +0100, Matthias Bolte ha scritto:
> > AC_ARG_WITH([xen-proxy],
> > -[ --with-xen-proxy add XEN setuid proxy support
> (on)],[],[with_xen_proxy=auto])
> > + AS_HELP_STRING([--with-xen-proxy], [add XEN setuid proxy support
> @<:@default=yes@:>@]),[
Il giorno ven, 08/01/2010 alle 12.44 +0100, Jim Meyering ha scritto:
>
>
> Oh, I see what you mean, finally.
> I had read only the first description of -shared in libtool
> documentation, and hadn't realized that was only for *compile mode*.
> There's a slightly different description following th
Il giorno ven, 08/01/2010 alle 11.16 +, Daniel P. Berrange ha
scritto:
>
>
> What problems do shared libraries cause with GDB - I've never had any
> trouble with it at all - it 'just works' perfectly picking up any
> debuginfo
> packages from things we link against too. The only GDB issues I
Il giorno ven, 08/01/2010 alle 12.12 +0100, Jim Meyering ha scritto:
>
>
> Using -shared in python/ would now be a little misleading,
> since it's useful only when building with --disable-shared,
> and python/ is no longer built with --disable-shared.
Not at all. It was needed to avoid building
Il giorno ven, 08/01/2010 alle 09.05 +0100, Jim Meyering ha scritto:
>
> * python/Makefile.am (libvirtmod_la_LDFLAGS): Do not use -shared.
> This reverts 8838ee39ab1c2bb7fffe93bfda220692664e8be6.
Not really necessary at this point.
--
Diego Elio Pettenò — “Flameeyes”
http://blog.flameeyes.eu/
Il giorno gio, 07/01/2010 alle 23.03 +0100, Jim Meyering ha scritto:
>
> So your change forced all other users of --disable-shared
> to also configure with --without-python, but did not inform them
> of the new constraint. BTW, it also rendered build instructions
> in the FAQ invalid.
I don't w
Il giorno gio, 07/01/2010 alle 22.23 +0100, Daniel Veillard ha scritto:
>
>
> I assume Jim want to keep --disable-shared as a convenient way to
> force libtool to generated binaries statically linked which is easier
> when dealing with gdb. If that's the case what would be nice is to be
> able
Il giorno gio, 07/01/2010 alle 21.29 +0100, Jim Meyering ha scritto:
>
> But --disable-shared is useful, and your change broke it.
On the usefulness of that I have generally a lot to say, but that's
another topic.
> As such, I can't see how you would be using --disable-shared.
Very simple: ./co
Il giorno gio, 07/01/2010 alle 21.14 +0100, Jim Meyering ha scritto:
>
> The change below reverts 8838ee39ab1c2bb7fffe93bfda220692664e8be6,
> so Diego, if your goal (with the reverted change) was more than to
> avoid seemingly-unnecessary work, please tell us what it was.
Well, to put it simply:
Il giorno mer, 23/12/2009 alle 14.28 -0500, Cole Robinson ha scritto:
>
> What is the output of 'virsh --connect lxc:/// capabilities'? Mine
> looks like:
>
fl...@yamato ~ % virsh --connect lxc:/// capabilities
x86_64
exe
32
/usr/libexec/libvirt_lx
I've been wanting to give a try to libvirt to handle containers from LXC
as well, but seems like if I follow the default configuration example, I
get this:
virsh # create /etc/libvirt/lxc/axant.xml
errore: Impossibile creare il dominio da /etc/libvirt/lxc/axant.xml
errore: unknown OS type exe
[s
Il giorno mer, 23/12/2009 alle 12.27 -0500, Cole Robinson ha scritto:
> I've had a daemon-conf failure for a while because the generated argv is too
> long, because my libvirt directory is /buried/deep/inside/a/directory/tree
> that pushes it over the limit. I haven't taken the time to figure out a
Il giorno mer, 23/12/2009 alle 15.42 +0100, Diego Elio “Flameeyes”
Pettenò ha scritto:
> I'm sincerely not sure what's going on here since the first validity
> errors (for bond.xml) don't seem right to me, so I'll leave it to
> whoever has an idea what the problem
If you pass libraries in the LDFLAGS variable, and then try AC_CHECK_FUNCS
to find whether a function is present or not, it'll fail badly when using
the --as-needed linker flag.
Instead, pass the libraries through the LIBS library, so that they are
passed after the conftest.c source file and the t
With the previous logic, if libhal_get_all_devices function was not found,
HAVE_HAL would be defined for the preprocessor but it wouldn't be enabled
in automake conditionals, causing the final link to fail with missing
references to HAL entries.
---
configure.in |7 ---
1 files changed, 4
Il giorno gio, 17/12/2009 alle 09.11 +0100, Daniel Veillard ha scritto:
>
> No idea what Portage is. Please keep the schemas in the main or
> client
> package and not as a separated chunk, there is really no reason to put
> them out, virsh, virt-xml-validate and the schemas should all be in
> th
Hi,
I've finally found the time to backport the schema fixes and I'm going
to add the nxml-libvirt-schemas package to Portage so that those like me
who like to edit the XML files with Emacs can do so with some support.
But I didn't pay enough attention before that the .rng files lack a
license he
Il giorno Fri, 11/12/2009 alle 20.02 +, Daniel P. Berrange ha
scritto:
> My preference is that we delete this block entirely and just
> declare it with a regex allowing a-Z, 0-9, _, -, .
I guess whatever choice works ;) I'm mostly concerned that right now my
configuration files don't validat
Il giorno Thu, 10/12/2009 alle 18.28 +0100, Matthias Bolte ha scritto:
>
> The crash could be due to the QEMU monitor handling problem that was
> recently fixed.
Yup that seems to be it, tied with a crash in qemu-kvm's 0.11.0 handling
of virtio network (qemu crashed, which then caused libvirt to
The two syntax should be equivalent, but the former creates, with trang, an
invalid Relax-NG Compact form file, as the output will contain the sequence
"+?" which is not recognized by tools like rnv.
---
docs/schemas/domain.rng | 40 +++-
1 files changed, 19 i
Hello,
In a recent post on my blog [1] I ranted on about libvirt and in
particular I complained that the configuration files look like what I
call “almost XML”. The reasons why I say that are multiple, let me try
to explain some.
In the configuration files, at least those created by virt-manager
Without this error the schema is not a well-formatted XML file.
---
docs/schemas/secret.rng |2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/docs/schemas/secret.rng b/docs/schemas/secret.rng
index 40e2b7f..39f8625 100644
--- a/docs/schemas/secret.rng
+++ b/docs/schemas/sec
With this error the schema is not a well-formed XML file.
---
docs/schemas/secret.rng |2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/docs/schemas/secret.rng b/docs/schemas/secret.rng
index 40e2b7f..39f8625 100644
--- a/docs/schemas/secret.rng
+++ b/docs/schemas/secret.rn
33 matches
Mail list logo
