With these options, it fails to install as below /bin/mkdir -p '/ws/sarvi-sjc/skunkworks/bspace/usrcisco/libexec' /bin/mkdir -p '/ws/sarvi-sjc/skunkworks/bspace/usrcisco/share/augeas/lenses' /bin/mkdir -p '/ws/sarvi-sjc/skunkworks/bspace/usrcisco/share/augeas/lenses/tests' /bin/mkdir -p '/etc/libvirt' /bin/mkdir: cannot create directory `/etc/libvirt': Permission denied make-3.79.1-p7[3]: *** [install-confDATA] Error 1 make-3.79.1-p7[3]: Leaving directory `/ws/sarvi-sjc/skunkworks/bspace/libvirt-1.0.3/src' make-3.79.1-p7[2]: *** [install-am] Error 2 make-3.79.1-p7[2]: Leaving directory `/ws/sarvi-sjc/skunkworks/bspace/libvirt-1.0.3/src' make-3.79.1-p7[1]: *** [install] Error 2 make-3.79.1-p7[1]: Leaving directory `/ws/sarvi-sjc/skunkworks/bspace/libvirt-1.0.3/src' make-3.79.1-p7: *** [install-recursive] Error 1 Just changing # define LIBVIRTD_PRIV_UNIX_SOCKET LOCALSTATEDIR "/run/libvirt/libvirt-sock" # define LIBVIRTD_PRIV_UNIX_SOCKET_RO LOCALSTATEDIR "/run/libvirt/libvirt-sock-ro" To # define LIBVIRTD_PRIV_UNIX_SOCKET "/var" "/run/libvirt/libvirt-sock" # define LIBVIRTD_PRIV_UNIX_SOCKET_RO "/var" "/run/libvirt/libvirt-sock-ro" Fixed the problem and things worked fine. It would be nice for a client only builds to be able to control through a ./configure argument or through some other .conf file where the server expects to find its socket file. That said, I am wondering why the client has to know where the server maintains its libvirt-sock files? Can't client and the server both talk in relative path terms instead of absolute? Sarvi On 3/6/13 10:52 AM, "Daniel P. Berrange" <berrange@redhat.com> wrote:
On Wed, Mar 06, 2013 at 06:42:05PM +0000, Saravanan Shanmugham (sarvi) wrote:
Thanks Daniel.
Is there a way around this. We want the virtualization hosts to have standard Fedora libvirt RPMs installed and running.
We are eventually trying to compile a subset of libvirt client tools only(the virsh client, python, libvirt and remote-drivers to run on various other developer systems ranging from RHEL 4/5/6 to allow them to be able to connect to the virtualization hosts. These compiled client tools will need to go into a --prefix=/usr/nonstddir/ which will be NFS mounted by all developer machines.
You might get away with using
--prefix=/usr/nonstddir --localstatedir=/var --sysconfdir=/etc
Regards, Daniel -- |: http://berrange.com -o- http://www.flickr.com/photos/dberrange/ :| |: http://libvirt.org -o- http://virt-manager.org :| |: http://autobuild.org -o- http://search.cpan.org/~danberr/ :| |: http://entangle-photo.org -o- http://live.gnome.org/gtk-vnc :|