<div class="gmail_quote">On Tue, Oct 6, 2009 at 5:01 AM, Anand Kumria <span dir="ltr"><<a href="mailto:wildfire@progsoc.org">wildfire@progsoc.org</a>></span> wrote:<br> <blockquote style="BORDER-LEFT: #ccc 1px solid; MARGIN: 0px 0px 0px 0.8ex; PADDING-LEFT: 1ex" class="gmail_quote">Hi,<br><br>What's with the colours? Why are you making it harder to understand what was said by who? </blockquote> <blockquote style="BORDER-LEFT: #ccc 1px solid; MARGIN: 0px 0px 0px 0.8ex; PADDING-LEFT: 1ex" class="gmail_quote"> <div class="gmail_quote"> <div><br>It would also be really useful if you kept the attribution lines, so we could all see who had said what, when.<br><br>What Richard is asking you for is the output of the ./configure command. </div></div></blockquote> <div> </div> <div> </div> <div> <div> </div> <div> <div>These are the packages that are required: as given in the mingw32.spec file</div> <div>mingw32-filesystem</div> <div>mingw32-gtk2</div> <div>mingw32-libvirt</div> <div>mingw32-libxml2</div> <div>mingw32-libglade2</div> <div>mingw32-gtk-vnc</div> <div>pkgconfig</div> <div> </div> <div>These are all there..</div> <div> </div> <div>[root@FC11-KVM ~]# rpm -qa | grep mingw32-filesystem<br>mingw32-filesystem-50-3.fc11.1.noarch<br>[root@FC11-KVM ~]# rpm -qa | grep mingw32-gtk2<br>mingw32-gtk2-2.16.6-1.fc11.noarch<br>mingw32-gtk2-static-2.16.6-1.fc11.noarch<br> [root@FC11-KVM ~]# rpm -qa | grep mingw32-libvirt<br>mingw32-libvirt-0.6.1-1.fc11.noarch<br>[root@FC11-KVM ~]# rpm -qa | grep mingw32-libxml2<br>mingw32-libxml2-2.7.4-1.fc11.noarch<br>mingw32-libxml2-static-2.7.4-1.fc11.noarch<br> [root@FC11-KVM ~]# rpm -qa | grep mingw32-libglade2<br>mingw32-libglade2-2.6.4-2.fc11.noarch<br>mingw32-libglade2-static-2.6.4-2.fc11.noarch<br>[root@FC11-KVM ~]# rpm -qa | grep mingw32-gtk-vnc<br>mingw32-gtk-vnc-0.3.8-5.fc11.noarch<br> [root@FC11-KVM ~]# rpm -qa | grep pkgconfig<br>pkgconfig-0.23-8.fc11.i586</div> <div> </div> <div> </div> <div>-----------------------</div> <div> </div> <div>this is how i configured the virt-viewer:</div> <div> </div> <div>PKG_CONFIG_PATH="/usr/i686-pc-mingw32/sys-root/mingw/lib/pkgconfig" CC="i686-pc-mingw32-gcc" ./configure --build=i386-pc-linux --host=i686-pc-mingw32 --prefix="/usr/i686-pc-mingw32/sys-root/mingw" --sysconfdir=C:\\pki</div> <div> </div> <div> </div> <div>and here is the result:</div> <div> </div> <div> </div> <div>checking for a BSD-compatible install... /usr/bin/install -c<br>checking whether build environment is sane... yes<br>checking for i686-pc-mingw32-strip... i686-pc-mingw32-strip<br>checking for a thread-safe mkdir -p... /bin/mkdir -p<br> checking for gawk... gawk<br>checking whether make sets $(MAKE)... yes<br>checking build system type... i386-pc-linux-gnu<br>checking host system type... i686-pc-mingw32<br>checking for i686-pc-mingw32-gcc... i686-pc-mingw32-gcc<br> checking for C compiler default output file name... a.exe<br>checking whether the C compiler works... yes<br>checking whether we are cross compiling... yes<br>checking for suffix of executables... .exe<br>checking for suffix of object files... o<br> checking whether we are using the GNU C compiler... yes<br>checking whether i686-pc-mingw32-gcc accepts -g... yes<br>checking for i686-pc-mingw32-gcc option to accept ISO C89... none needed<br>checking for style of include used by make... GNU<br> checking dependency style of i686-pc-mingw32-gcc... gcc3<br>checking whether i686-pc-mingw32-gcc and cc understand -c and -o together... yes<br>checking for a sed that does not truncate output... /bin/sed<br>checking for grep that handles long lines and -e... /bin/grep<br> checking for egrep... /bin/grep -E<br>checking for fgrep... /bin/grep -F<br>checking for ld used by i686-pc-mingw32-gcc... /usr/i686-pc-mingw32/bin/ld<br>checking if the linker (/usr/i686-pc-mingw32/bin/ld) is GNU ld... yes<br> checking for BSD- or MS-compatible name lister (nm)... /usr/bin/i686-pc-mingw32-nm -B<br>checking the name lister (/usr/bin/i686-pc-mingw32-nm -B) interface... BSD nm<br>checking whether ln -s works... yes<br>checking the maximum length of command line arguments... 1966080<br> checking whether the shell understands some XSI constructs... yes<br>checking whether the shell understands "+="... yes<br>checking for /usr/i686-pc-mingw32/bin/ld option to reload object files... -r<br>checking for i686-pc-mingw32-objdump... i686-pc-mingw32-objdump<br> checking how to recognize dependent libraries... file_magic ^x86 archive import|^x86 DLL<br>checking for i686-pc-mingw32-ar... i686-pc-mingw32-ar<br>checking for i686-pc-mingw32-strip... (cached) i686-pc-mingw32-strip<br> checking for i686-pc-mingw32-ranlib... i686-pc-mingw32-ranlib<br>checking command to parse /usr/bin/i686-pc-mingw32-nm -B output from i686-pc-mingw32-gcc object... ok<br>checking how to run the C preprocessor... i686-pc-mingw32-gcc -E<br> checking for ANSI C header files... yes<br>checking for sys/types.h... yes<br>checking for sys/stat.h... yes<br>checking for stdlib.h... yes<br>checking for string.h... yes<br>checking for memory.h... yes<br>checking for strings.h... yes<br> checking for inttypes.h... yes<br>checking for stdint.h... yes<br>checking for unistd.h... yes<br>checking for dlfcn.h... yes<br>checking for objdir... .libs<br>checking if i686-pc-mingw32-gcc supports -fno-rtti -fno-exceptions... no<br> checking for i686-pc-mingw32-gcc option to produce PIC... -DDLL_EXPORT -DPIC<br>checking if i686-pc-mingw32-gcc PIC flag -DDLL_EXPORT -DPIC works... yes<br>checking if i686-pc-mingw32-gcc static flag -static works... yes<br> checking if i686-pc-mingw32-gcc supports -c -o file.o... yes<br>checking if i686-pc-mingw32-gcc supports -c -o file.o... (cached) yes<br>checking whether the i686-pc-mingw32-gcc linker (/usr/i686-pc-mingw32/bin/ld) supports shared libraries... yes<br> checking whether -lc should be explicitly linked in... yes<br>checking dynamic linker characteristics... Win32 ld.exe<br>checking how to hardcode library paths into programs... immediate<br>checking whether stripping libraries is possible... yes<br> checking if libtool supports shared libraries... yes<br>checking whether to build shared libraries... yes<br>checking whether to build static libraries... yes<br>checking whether gcc understands -Wp,-D_FORTIFY_SOURCE=2... yes<br> checking whether gcc understands -fexceptions... yes<br>checking whether gcc understands -fstack-protector... yes<br>checking whether gcc understands --param=ssp-buffer-size=4... yes<br>checking whether gcc understands -fasynchronous-unwind-tables... yes<br> checking whether gcc understands -Wall... yes<br>checking whether gcc understands -Wmissing-prototypes... yes<br>checking whether gcc understands -std=c99... yes<br>checking whether gcc understands -Wnested-externs... yes<br> checking whether gcc understands -Wpointer-arith... yes<br>checking whether gcc understands -Wextra... yes<br>checking whether gcc understands -Wshadow... yes<br>checking whether gcc understands -Wcast-align... yes<br>checking whether gcc understands -Wwrite-strings... yes<br> checking whether gcc understands -Waggregate-return... yes<br>checking whether gcc understands -Winline... yes<br>checking whether gcc understands -Wredundant-decls... yes<br>checking whether gcc understands -Wno-sign-compare... yes<br> checking what language compliance flags to pass to the C compiler... <br>checking for i686-pc-mingw32-pkg-config... no<br>checking for pkg-config... /usr/bin/pkg-config<br>configure: WARNING: using cross tools not prefixed with host triplet<br> checking pkg-config is at least version 0.9.0... yes<br>checking for LIBXML2... yes<br>checking for LIBVIRT... yes<br>checking for GTK2... yes<br>checking for LIBGLADE2... yes<br>checking for GTKVNC... yes<br>checking sys/socket.h usability... no<br> checking sys/socket.h presence... no<br>checking for sys/socket.h... no<br>checking sys/un.h usability... no<br>checking sys/un.h presence... no<br>checking for sys/un.h... no<br>checking windows.h usability... yes<br>checking windows.h presence... yes<br> checking for windows.h... yes<br>checking for fork... no<br>checking for socketpair... no<br>configure: creating ./config.status<br>config.status: creating Makefile<br>config.status: creating src/Makefile<br>config.status: creating man/Makefile<br> config.status: creating plugin/Makefile<br>config.status: creating virt-viewer.spec<br>config.status: creating mingw32-virt-viewer.spec<br>config.status: creating config.h<br>config.status: executing depfiles commands<br> config.status: executing libtool commands</div></div></div> <div> </div> <div> </div> <blockquote style="BORDER-LEFT: #ccc 1px solid; MARGIN: 0px 0px 0px 0.8ex; PADDING-LEFT: 1ex" class="gmail_quote"> <div class="gmail_quote"> <div><br>What he hasn't asked, yet, is how porting libvirt and the virt-* utilis helps you.<br><br>What is the actual end goal here? A "just for fun" experiment, in which case you are probably better served by answers to your questions which lead you to do the deeper debugging. Or a school project, in which case the same applies.<br> <br>Thanks,<br>Anand<br></div></div></blockquote></div> <div><br> </div> <div>I had to call the libvirt functions from my windows machine and this could only be done by porting libvirt to windows(as a client).. i have done that sucessfully and now I can call all the functions from my windows machine...</div> <div> </div> <div>Now what happens is that after I create a new Guest OS using my code(from windows), I have to logon into my server machine and then continue installing the Guest. This is where i thought of porting virt-viewer to windows so that i can do it from the same remote windows machine.</div> <div> </div> <div>The only problem that im facing right now is with the virt-viewer. If this issues is resolved, we are thinking of intergate libvirt with one of our product.</div> <div> </div> <div>Regards</div> <div>Anuj</div>