On Thu, Jan 31, 2013 at 2:52 AM, Eric Blake <eblake@redhat.com> wrote: [...]
Pastebin links expire, making it harder to follow the conversation when revisiting the list archives in the future. It is okay to paste the actual error into the message rather than making people chase through a link.
You are right, i will do accoding to what you said. Thanks.
Could anyone give me some suggestions? Thanks in advance ;-)
[...] /usr/bin//xsltproc: /usr/local/lib/libxml2.so.2: no version information available (required by /usr/lib/libxslt.so.1) /usr/bin//xsltproc: /usr/local/lib/libxml2.so.2: no version information available (required by /usr/lib/libxslt.so.1) /usr/bin//xsltproc: /usr/local/lib/libxml2.so.2: no version information available (required by /usr/lib/libxslt.so.1) /usr/bin//xsltproc: /usr/local/lib/libxml2.so.2: no version information available (required by /usr/lib/libxslt.so.1) /usr/bin//xsltproc: /usr/local/lib/libxml2.so.2: no version information available (required by /usr/lib/libxslt.so.1) /usr/bin//xsltproc: /usr/local/lib/libxml2.so.2: no version information available (required by /usr/lib/libxslt.so.1) /usr/bin//xsltproc: /usr/local/lib/libxml2.so.2: no version information available (required by /usr/lib/libxslt.so.1) /usr/bin//xsltproc: /usr/local/lib/libxml2.so.2: no version information available (required by /usr/lib/libexslt.so.0) /usr/bin//xsltproc: /usr/local/lib/libxml2.so.2: no version information available (required by /usr/lib/libexslt.so.0) /usr/bin//xsltproc: /usr/local/lib/libxml2.so.2: no version information available (required by /usr/lib/libexslt.so.0) /usr/bin//xmlcatalog: /usr/local/lib/libxml2.so.2: no version information available (required by /usr/bin//xmlcatalog) missing XHTML1 DTD Generating drvphyp.html.tmp
I'm not sure why your xsltproc is so noisy (it's probably a broken install that you ought to look into fixing), but that it outside the scope of the libvirt list. Meanwhile, your problem is definitely related to the fact that you don't have enough developer tools installed, but you are trying to build from git, and therefore the html files aren't pre-built. If you use the official libvirt 1.0.2 tarball (released today) instead of building from git, you would not have this problem. Otherwise, it sounds like you need to install the proper DTD files for generating the html files, before 'make install' has a chance of working. On Fedora, the packages are named xhtml1-dtds and docbook-dtds; I'm not sure what they are named on other distros.
Also, be aware that it is possible to test a just-built libvirt without installing it first, by using './autogen.sh --system' to start the build, and then using './run daemon/libvirtd' after completing the build (for best results, you'll need to preinstall a distro build of libvirt, but then disable the distro service, so fhat all the auxiliary files that the in-tree binary wants to use will already be in place).
Hmmm..., actually, i can now use libvirt sucessfully. I forecast up errors does no matter with my using libvirt correctly, right? I use Libvirt to test Sheepdog storage driver for Libvirt and add my new storage driver. -- Thanks Harry Wei