Here is an example libxl module gcc command:
gcc -O1 -fno-omit-frame-pointer -m64 -g -fno-strict-aliasing -std=gnu99
-Wall -Wstrict-prototypes -Wdeclaration-after-statement
-Wno-unused-but-set-variable -Wno-unused-local-typedefs -D__XEN_TOOLS__
-MMD -MF .libxl.o.d -D_LARGEFILE_SOURCE -D_LARGEFIL
I'm have a lot of difficulty implementing the actions suggested so far by
those who've chimed in about this issue. I've resolved now to do the
following:
* make clean and make world on xen source, and capture build logs
* look up libxl build logs and see what compiler flags were used
* repeat abo
Thanks Guido, unfortunately no luck:
root@:~/debian# grep DEB_CONFIGURE_EXTRA_ARGS *
grep: apparmor: Is a directory
grep: patches: Is a directory
grep: source: Is a directory
root@:~/debian#
root@:~/debian#
root@:~/debian#
root@:~/debian# grep DEB_CONFIGURE_EXTRA_ARGS */*
root@:~/debian#
root@:~/d
Hi,
I am using qemu hook script to track status of VM live migration - libvirt
1.2.9 as included in Debian Wheezy backports.
I would like to be informed of the fact that VM migration has successfully
finished as soon as possible. Based on the steps below, when would that be
possible?
Sample VM m
On Tue, Mar 03, 2015 at 02:31:27PM -0500, Wayne Mills wrote:
> I downloaded and untarred the deb package and grepped for 'configure', but
> none of the hits were configure commands. Is there a better way to find it?
Assuming this is still based on the Debian package look for
DEB_CONFIGURE_EXTRA_A
