On Tue, Oct 6, 2009 at 5:01 AM, Anand Kumria wildfire@progsoc.org wrote:
Hi,
What's with the colours? Why are you making it harder to understand what was said by who?
It would also be really useful if you kept the attribution lines, so we could all see who had said what, when.
What Richard is asking you for is the output of the ./configure command.
These are the packages that are required: as given in the mingw32.spec file mingw32-filesystem mingw32-gtk2 mingw32-libvirt mingw32-libxml2 mingw32-libglade2 mingw32-gtk-vnc pkgconfig
These are all there..
[root@FC11-KVM ~]# rpm -qa | grep mingw32-filesystem mingw32-filesystem-50-3.fc11.1.noarch [root@FC11-KVM ~]# rpm -qa | grep mingw32-gtk2 mingw32-gtk2-2.16.6-1.fc11.noarch mingw32-gtk2-static-2.16.6-1.fc11.noarch [root@FC11-KVM ~]# rpm -qa | grep mingw32-libvirt mingw32-libvirt-0.6.1-1.fc11.noarch [root@FC11-KVM ~]# rpm -qa | grep mingw32-libxml2 mingw32-libxml2-2.7.4-1.fc11.noarch mingw32-libxml2-static-2.7.4-1.fc11.noarch [root@FC11-KVM ~]# rpm -qa | grep mingw32-libglade2 mingw32-libglade2-2.6.4-2.fc11.noarch mingw32-libglade2-static-2.6.4-2.fc11.noarch [root@FC11-KVM ~]# rpm -qa | grep mingw32-gtk-vnc mingw32-gtk-vnc-0.3.8-5.fc11.noarch [root@FC11-KVM ~]# rpm -qa | grep pkgconfig pkgconfig-0.23-8.fc11.i586
-----------------------
this is how i configured the virt-viewer:
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
and here is the result:
checking for a BSD-compatible install... /usr/bin/install -c checking whether build environment is sane... yes checking for i686-pc-mingw32-strip... i686-pc-mingw32-strip checking for a thread-safe mkdir -p... /bin/mkdir -p checking for gawk... gawk checking whether make sets $(MAKE)... yes checking build system type... i386-pc-linux-gnu checking host system type... i686-pc-mingw32 checking for i686-pc-mingw32-gcc... i686-pc-mingw32-gcc checking for C compiler default output file name... a.exe checking whether the C compiler works... yes checking whether we are cross compiling... yes checking for suffix of executables... .exe checking for suffix of object files... o checking whether we are using the GNU C compiler... yes checking whether i686-pc-mingw32-gcc accepts -g... yes checking for i686-pc-mingw32-gcc option to accept ISO C89... none needed checking for style of include used by make... GNU checking dependency style of i686-pc-mingw32-gcc... gcc3 checking whether i686-pc-mingw32-gcc and cc understand -c and -o together... yes checking for a sed that does not truncate output... /bin/sed checking for grep that handles long lines and -e... /bin/grep checking for egrep... /bin/grep -E checking for fgrep... /bin/grep -F checking for ld used by i686-pc-mingw32-gcc... /usr/i686-pc-mingw32/bin/ld checking if the linker (/usr/i686-pc-mingw32/bin/ld) is GNU ld... yes checking for BSD- or MS-compatible name lister (nm)... /usr/bin/i686-pc-mingw32-nm -B checking the name lister (/usr/bin/i686-pc-mingw32-nm -B) interface... BSD nm checking whether ln -s works... yes checking the maximum length of command line arguments... 1966080 checking whether the shell understands some XSI constructs... yes checking whether the shell understands "+="... yes checking for /usr/i686-pc-mingw32/bin/ld option to reload object files... -r checking for i686-pc-mingw32-objdump... i686-pc-mingw32-objdump checking how to recognize dependent libraries... file_magic ^x86 archive import|^x86 DLL checking for i686-pc-mingw32-ar... i686-pc-mingw32-ar checking for i686-pc-mingw32-strip... (cached) i686-pc-mingw32-strip checking for i686-pc-mingw32-ranlib... i686-pc-mingw32-ranlib checking command to parse /usr/bin/i686-pc-mingw32-nm -B output from i686-pc-mingw32-gcc object... ok checking how to run the C preprocessor... i686-pc-mingw32-gcc -E checking for ANSI C header files... yes checking for sys/types.h... yes checking for sys/stat.h... yes checking for stdlib.h... yes checking for string.h... yes checking for memory.h... yes checking for strings.h... yes checking for inttypes.h... yes checking for stdint.h... yes checking for unistd.h... yes checking for dlfcn.h... yes checking for objdir... .libs checking if i686-pc-mingw32-gcc supports -fno-rtti -fno-exceptions... no checking for i686-pc-mingw32-gcc option to produce PIC... -DDLL_EXPORT -DPIC checking if i686-pc-mingw32-gcc PIC flag -DDLL_EXPORT -DPIC works... yes checking if i686-pc-mingw32-gcc static flag -static works... yes checking if i686-pc-mingw32-gcc supports -c -o file.o... yes checking if i686-pc-mingw32-gcc supports -c -o file.o... (cached) yes checking whether the i686-pc-mingw32-gcc linker (/usr/i686-pc-mingw32/bin/ld) supports shared libraries... yes checking whether -lc should be explicitly linked in... yes checking dynamic linker characteristics... Win32 ld.exe checking how to hardcode library paths into programs... immediate checking whether stripping libraries is possible... yes checking if libtool supports shared libraries... yes checking whether to build shared libraries... yes checking whether to build static libraries... yes checking whether gcc understands -Wp,-D_FORTIFY_SOURCE=2... yes checking whether gcc understands -fexceptions... yes checking whether gcc understands -fstack-protector... yes checking whether gcc understands --param=ssp-buffer-size=4... yes checking whether gcc understands -fasynchronous-unwind-tables... yes checking whether gcc understands -Wall... yes checking whether gcc understands -Wmissing-prototypes... yes checking whether gcc understands -std=c99... yes checking whether gcc understands -Wnested-externs... yes checking whether gcc understands -Wpointer-arith... yes checking whether gcc understands -Wextra... yes checking whether gcc understands -Wshadow... yes checking whether gcc understands -Wcast-align... yes checking whether gcc understands -Wwrite-strings... yes checking whether gcc understands -Waggregate-return... yes checking whether gcc understands -Winline... yes checking whether gcc understands -Wredundant-decls... yes checking whether gcc understands -Wno-sign-compare... yes checking what language compliance flags to pass to the C compiler... checking for i686-pc-mingw32-pkg-config... no checking for pkg-config... /usr/bin/pkg-config configure: WARNING: using cross tools not prefixed with host triplet checking pkg-config is at least version 0.9.0... yes checking for LIBXML2... yes checking for LIBVIRT... yes checking for GTK2... yes checking for LIBGLADE2... yes checking for GTKVNC... yes checking sys/socket.h usability... no checking sys/socket.h presence... no checking for sys/socket.h... no checking sys/un.h usability... no checking sys/un.h presence... no checking for sys/un.h... no checking windows.h usability... yes checking windows.h presence... yes checking for windows.h... yes checking for fork... no checking for socketpair... no configure: creating ./config.status config.status: creating Makefile config.status: creating src/Makefile config.status: creating man/Makefile config.status: creating plugin/Makefile config.status: creating virt-viewer.spec config.status: creating mingw32-virt-viewer.spec config.status: creating config.h config.status: executing depfiles commands config.status: executing libtool commands
What he hasn't asked, yet, is how porting libvirt and the virt-* utilis helps you.
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.
Thanks, Anand
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...
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.
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.
Regards Anuj