On Wed, 2016-06-15 at 11:50 -0400, Laine Stump wrote:
You really shouldn't waste your time doing make rpm all the time IMHO.
./autogen.sh --system make -j 12 sudo systemctl stop libvirtd.service sudo ./daemon/libvirtd
will "just work(tm)" - its how I've done all libvirt development for years.
Yeah, I used to do it that way, and at some point I switched to just making the rpm and installing it. I don't even remember now why I did that - it could have just been because I was testing on a different machine from where I was building, or maybe I was rebooting a lot and wanted my new libvirtd to be the one that came up at boot time. At the time I switched, the penalty was small enough that it just became automatic, but over the last year or so the build time (for make -j$LOTS rpm) has slowly crept up to the point where it's now time to retrain my muscle memory and use the in-tree libvirtd.
I suppose one downside of that is that make rpm failures won't be noticed as quickly :-)
https://ci.centos.org/view/libvirt-project/job/libvirt-daemon-rpm/ :) By the way, it's failing right now, but should start to pass again with this patch. I've just pushed it. -- Andrea Bolognani Software Engineer - Virtualization Team