On Wed, Aug 20, 2008 at 4:30 PM, Jun Koi <junkoi2004@xxxxxxxxx> wrote: > Hi, > > I added some new code to libvirt.c, and recompile. However, when "make > install". qemud/.libs/libvirtd is installed but not qemud/libvirtd. > Why? Looks like a bug? > > The problem is that qemud/libvirtd has my new code, but not > qemud/.libs/libvirtd! So "make install" installs the old binary, which > I dont know where it is from. (Perhaps from the first compilation?) > > I am not familiar with the autoconf Makefile, and cannot figure it out > why it is working this way. > This is not getting funny anymore. I clean src/.libs/*, and qemud/.libs/*, and recompile and "make install" again. This step installed stuffs in .libs/ into system. Then I found that qemud/libvirtd and src/virsh works well together (for ex, src/virsh -c qemu:///system list works well), but /usr/sbin/libvirtd and /usr/bin/virsh dont work: "virsh -c qemu:///system list" reports "failed to connect to hypervisor". I am wondering what is going on with those binary in .libs/?? Thanks, J > Many thanks, > Jun > -- Libvir-list mailing list Libvir-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/libvir-list