On 07/24/2013 11:24 PM, Abhishek Sharma wrote: > Hi, > > I am new to libvirt and I am trying to compile libvirt from the git > repository. I mainly plan to use it for managing ESX server. However I get the > following error during make. > > /"libvirt undefined reference to virNetTLSInit"/ > > Here are the steps which I took. > > 1. Get the code. git clone git://libvirt.org/libvirt.git > <http://libvirt.org/libvirt.git> > 2. Run autogen > ./autogen.sh --without-xen --with-esx --without-numactl --without-remote > --without-libvirtd --without-one --without-openvz --without-qemu --without-uml > --without-phyp --without-vbox --without-lxc --without-one --without-test > --without-network --without-selinux --with-python > > 3. make > > > Looks like the following commit somehow separated the gnutls symbols. > > /commit 83d7e4e4607a96b6959a6b0afd44a10a783fd928 > Author: Daniel P. Berrange <berrange(a)redhat.com <mailto: berrange(a)redhat.com&gt;&gt; > Date: Wed Mar 13 13:37:29 2013 +0000 > > Use separate symbol file for GNUTLS symbols/ > > How can I successfully compile libvirt ? Try building it --with-remote, it seems we assume that in quite a few places. Jan

On 07/25/2013 10:17 AM, Abhishek Sharma wrote: > Thanks Jan, [please don't top-post on technical lists] > > Yes it worked when I removed --without-remote. Good to know. That said, we should still fix things before 1.1.1 is released to fix this bug, so that future users don't have to figure out the magic configure option to use. >>> 2. Run autogen >>> ./autogen.sh --without-xen --with-esx --without-numactl --without-remote >>> --without-libvirtd --without-one --without-openvz --without-qemu >> --without-uml >>> --without-phyp --without-vbox --without-lxc --without-one --without-test >>> --without-network --without-selinux --with-python >>> >>> How can I successfully compile libvirt ? >> >> Try building it --with-remote, it seems we assume that in quite a few >> places. -- Eric Blake eblake redhat com +1-919-301-3266 Libvirt virtualization library http://libvirt.org

Since I am new to this mailing list, I am not sure what is the procedure of tracking bugs/enhancements like this. Should I go ahead and file a bug at https://bugzilla.redhat.com/ ?