On Mon, Jan 04, 2010 at 04:22:25PM +0100, Gerd Hoffmann wrote: > On 12/23/09 12:37, Avi Kivity wrote: >> On 12/23/2009 12:58 PM, Thomas Treutner wrote: >>> On Wednesday 23 December 2009 11:24:04 Avi Kivity wrote: >>>> Please post a full log, after 'make clean'. >>> http://pastebin.com/f404c8648 >>> >> >> Oh, I missed it at first - looks like libxenguest and libxenctrl conflict. > > Indeed, there are (un)lock_pages functions in both libraries. It is > fixed in xen 3.3+, where libxenguest doesn't has these functions any > more. > > /me also wonders why Debian seems to have only static xen libraries. > I think when linking against the shared libraries avoids this too as the > functions are supposed to be library-internal. > >> Copying Gerd for an opinion. > > I think there isn't much we can do about this, it is clearly a xen bug. > > Uhm, well, while thinking about it: The test app compiled and linked by > configure should have failed in a simliar way, thereby automatically > disabling xen support. I have no idea why it didn't ... "static library" is in fact just an archive of objects. If you happen not to pull in the conflicting objects, you won't see the conflict. So test file would have to call lock_pages/unlock_pages for config to detect the issue. > cheers, > Gerd > -- > To unsubscribe from this list: send the line "unsubscribe kvm" in > the body of a message to majordomo@xxxxxxxxxxxxxxx > More majordomo info at http://vger.kernel.org/majordomo-info.html -- To unsubscribe from this list: send the line "unsubscribe kvm" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
