Re: [libvirt] Compiling libvirt RPC client library for QNX
On 01/03/14 9:39 AM, Panday Ritesh Sharma (rpanday) rpan...@cisco.com wrote: On 25/02/14 11:17 PM, Eric Blake ebl...@redhat.com wrote: On 02/25/2014 09:05 AM, Panday Ritesh Sharma (rpanday) wrote: We are using a wrapper of make for compilation for QNX. So I need to know, when I am compiling this client library on linux with '--without-libvirtd' option, what all .c files and libraries are being used. Then I will take those .c files to my build environment and link that to the libraries needed. I will have to see whether those libraries are present in my QNX build environment. Please helpŠ That feels awkward. Does QNX have a POSIX-compatible /bin/sh? If so, just unpack the tarball there, and run ./configure on your QNX machine the same way you do on Linux. I'm not personally familiar enough with QNX to know what build environment it provides. It may also be a situation where people tend to cross-compile for QNX rather than building natively. Libvirt supports cross-compilation (we build mingw client-only binaries under Fedora, so that setup could be copied for compiling client-only QNX binaries if you have a qnx cross-compiler on Linux). But at this point, you are pioneering new ground with regards to libvirt, and you will probably have to seek more help from people familiar with QNX compilation, as this list doesn't have the expertise with your system. Feel free to post build logs, and we can still try to help decipher them, but if you hit failures, you will probably have to be the one to do the legwork to resolve them. Hi Eric, This time I am writing a the bottom of this thread, is this correct ? Yes, thanks! -- Eric Blake eblake redhat com+1-919-301-3266 Libvirt virtualization library http://libvirt.org Hi Team, I am working here with our build infra team to get this library compiled for QNX. We will not be compiling on QNX-machine but use cross compiler. While going through 'configure' file, I realised it uses gcc compiler and links all related libraries. But here internally we use icc compiler for x86-machines. Do you have a configure file which I can use for icc i.e.; 'icc.10.2.014b'compiler ? When I tried using 'gcc.c4.2.1-p2' for trial purpose, which is available to us, I hit the error === checking for gnutls_handshake in -lgnutls... no configure: error: You must install the GnuTLS library in order to compile and run libvirt == Is there a option in 'configure' file which I can use to bypass this error ? Regards Ritesh Sharma Hi Team, Could you reply my query. Your help is much appreciated. Regards Ritesh Sharma -- libvir-list mailing list libvir-list@redhat.com https://www.redhat.com/mailman/listinfo/libvir-list
Re: [libvirt] Compiling libvirt RPC client library for QNX
On Sat, Mar 01, 2014 at 04:09:00AM +, Panday Ritesh Sharma (rpanday) wrote: When I tried using 'gcc.c4.2.1-p2' for trial purpose, which is available to us, I hit the error === checking for gnutls_handshake in -lgnutls... no configure: error: You must install the GnuTLS library in order to compile and run libvirt == Is there a option in 'configure' file which I can use to bypass this error ? You can answer this yourself by looking at the ./configure --help output which lists all possible otions. Hint --without-gnutls is what you want in this case. Regards, Daniel -- |: http://berrange.com -o-http://www.flickr.com/photos/dberrange/ :| |: http://libvirt.org -o- http://virt-manager.org :| |: http://autobuild.org -o- http://search.cpan.org/~danberr/ :| |: http://entangle-photo.org -o- http://live.gnome.org/gtk-vnc :| -- libvir-list mailing list libvir-list@redhat.com https://www.redhat.com/mailman/listinfo/libvir-list
Re: [libvirt] Compiling libvirt RPC client library for QNX
On 04/03/14 12:09 AM, Daniel P. Berrange berra...@redhat.com wrote: On Sat, Mar 01, 2014 at 04:09:00AM +, Panday Ritesh Sharma (rpanday) wrote: When I tried using 'gcc.c4.2.1-p2' for trial purpose, which is available to us, I hit the error === checking for gnutls_handshake in -lgnutls... no configure: error: You must install the GnuTLS library in order to compile and run libvirt == Is there a option in 'configure' file which I can use to bypass this error ? You can answer this yourself by looking at the ./configure --help output which lists all possible otions. Hint --without-gnutls is what you want in this case. Regards, Daniel -- |: http://berrange.com -o- http://www.flickr.com/photos/dberrange/ :| |: http://libvirt.org -o- http://virt-manager.org :| |: http://autobuild.org -o- http://search.cpan.org/~danberr/ :| |: http://entangle-photo.org -o- http://live.gnome.org/gtk-vnc :| Hi Daniel, IS there a configure file which can be used for 'icc' compiler, or the same configure file I need to modify and use for 'icc' ? This library is ever compiled with 'icc' compiler ? For the sake of compilation if I use '--without-gnutls' and '--without-macvtap' what will be it's impact ? I mean, will I be able to use the libvirt RPC client library ? Regards Ritesh Sharma -- libvir-list mailing list libvir-list@redhat.com https://www.redhat.com/mailman/listinfo/libvir-list
Re: [libvirt] Compiling libvirt RPC client library for QNX
On Mon, Mar 03, 2014 at 06:49:25PM +, Panday Ritesh Sharma (rpanday) wrote: On 04/03/14 12:09 AM, Daniel P. Berrange berra...@redhat.com wrote: On Sat, Mar 01, 2014 at 04:09:00AM +, Panday Ritesh Sharma (rpanday) wrote: When I tried using 'gcc.c4.2.1-p2' for trial purpose, which is available to us, I hit the error === checking for gnutls_handshake in -lgnutls... no configure: error: You must install the GnuTLS library in order to compile and run libvirt == Is there a option in 'configure' file which I can use to bypass this error ? You can answer this yourself by looking at the ./configure --help output which lists all possible otions. Hint --without-gnutls is what you want in this case. Regards, Daniel -- |: http://berrange.com -o- http://www.flickr.com/photos/dberrange/ :| |: http://libvirt.org -o- http://virt-manager.org :| |: http://autobuild.org -o- http://search.cpan.org/~danberr/ :| |: http://entangle-photo.org -o- http://live.gnome.org/gtk-vnc :| Hi Daniel, IS there a configure file which can be used for 'icc' compiler, or the same configure file I need to modify and use for 'icc' ? Just set the CC environment variable eg export CC=icc This library is ever compiled with 'icc' compiler ? I've tried it once in the past, but not for many years. It should mostly work since icc claims strong compatibility with gcc. For the sake of compilation if I use '--without-gnutls' and '--without-macvtap' what will be it's impact ? I mean, will I be able to use the libvirt RPC client library ? GNUTLS is used to provide TLS encryption for libvirtd TCP sockets. Libvirt can alternatively use cyrus-sasl for Kerberos based encryption and authentication. Failing that you'd have to use an SSH tunnel to access the libvirt RPC API remotely. macvtap has no impact on the client library. Regards, Daniel -- |: http://berrange.com -o-http://www.flickr.com/photos/dberrange/ :| |: http://libvirt.org -o- http://virt-manager.org :| |: http://autobuild.org -o- http://search.cpan.org/~danberr/ :| |: http://entangle-photo.org -o- http://live.gnome.org/gtk-vnc :| -- libvir-list mailing list libvir-list@redhat.com https://www.redhat.com/mailman/listinfo/libvir-list
Re: [libvirt] Compiling libvirt RPC client library for QNX
On 02/28/2014 09:09 PM, Panday Ritesh Sharma (rpanday) wrote: While going through 'configure' file, I realised it uses gcc compiler and links all related libraries. But here internally we use icc compiler for x86-machines. Do you have a configure file which I can use for icc i.e.; 'icc.10.2.014b'compiler ? The 'configure' file defaults to using gcc when compiling natively, but is already generic enough to support any compiler, native or cross. All you have to do is tell configure what it needs to know: ./configure --build=$(build-aux/config.guess) \ --host=$FIXME CC=icc.10.2.014b where you replace $FIXME with the proper target triple of your QNX machine (I honestly don't know what that would be, and a quick read through build-aux/config.sub which lists all canonical target triples didn't make it obvious to me). It sounds like you are brand new to cross-compiling code that follows GNU Coding Standards. If so, I'd highly suggest that you FIRST try something MUCH simpler, like cross-compiling GNU Hello[1] using the same arguments to that project's configure. Once you get a simple binary cross-compiling with correct --build, --host, and CC= arguments, then you can use the same arguments on any other project (including libvirt) where ./configure follows GNU Coding Standards. And as this list is not full of people with QNX experience, you may have better luck looking elsewhere for people who DO know how to cross-compile to QNX, even if what they compile is not libvirt, to at least learn the basics of setting up a successful cross-compile for your platform. [1]https://www.gnu.org/software/hello/ -- Eric Blake eblake redhat com+1-919-301-3266 Libvirt virtualization library http://libvirt.org signature.asc Description: OpenPGP digital signature -- libvir-list mailing list libvir-list@redhat.com https://www.redhat.com/mailman/listinfo/libvir-list
Re: [libvirt] Compiling libvirt RPC client library for QNX
On 25/02/14 11:17 PM, Eric Blake ebl...@redhat.com wrote: On 02/25/2014 09:05 AM, Panday Ritesh Sharma (rpanday) wrote: We are using a wrapper of make for compilation for QNX. So I need to know, when I am compiling this client library on linux with '--without-libvirtd' option, what all .c files and libraries are being used. Then I will take those .c files to my build environment and link that to the libraries needed. I will have to see whether those libraries are present in my QNX build environment. Please helpŠ That feels awkward. Does QNX have a POSIX-compatible /bin/sh? If so, just unpack the tarball there, and run ./configure on your QNX machine the same way you do on Linux. I'm not personally familiar enough with QNX to know what build environment it provides. It may also be a situation where people tend to cross-compile for QNX rather than building natively. Libvirt supports cross-compilation (we build mingw client-only binaries under Fedora, so that setup could be copied for compiling client-only QNX binaries if you have a qnx cross-compiler on Linux). But at this point, you are pioneering new ground with regards to libvirt, and you will probably have to seek more help from people familiar with QNX compilation, as this list doesn't have the expertise with your system. Feel free to post build logs, and we can still try to help decipher them, but if you hit failures, you will probably have to be the one to do the legwork to resolve them. Hi Eric, This time I am writing a the bottom of this thread, is this correct ? Yes, thanks! -- Eric Blake eblake redhat com+1-919-301-3266 Libvirt virtualization library http://libvirt.org Hi Team, I am working here with our build infra team to get this library compiled for QNX. We will not be compiling on QNX-machine but use cross compiler. While going through 'configure' file, I realised it uses gcc compiler and links all related libraries. But here internally we use icc compiler for x86-machines. Do you have a configure file which I can use for icc i.e.; 'icc.10.2.014b'compiler ? When I tried using 'gcc.c4.2.1-p2' for trial purpose, which is available to us, I hit the error === checking for gnutls_handshake in -lgnutls... no configure: error: You must install the GnuTLS library in order to compile and run libvirt == Is there a option in 'configure' file which I can use to bypass this error ? Regards Ritesh Sharma -- libvir-list mailing list libvir-list@redhat.com https://www.redhat.com/mailman/listinfo/libvir-list
Re: [libvirt] Compiling libvirt RPC client library for QNX
Hi Eric, I used the option '--without-macvtap' and I was able to compile on my linux box. When I compiled, I see many libraries are getting built. But as I have explained my requirement earlier, I just need a RPC client library, essentially the option '--with-remote'. If I check .c files I see only './src/libvirt.c' and './tools/virsh.c' are the two files where '# ifdef WITH_REMOTE' is present. Does it mean that as per my requirement I only need to compile these files? My intent is to have a library with minimal files which suffice to my requirement. Because that way it will be easier for me to compile them on QNX. You have mentioned on another thread that in a weeks time some new version of libvirt will come which we can compile for non-linux machines ? What change is coming in that version ? The latest version of libvirt can not be compiled for QNX ? Regards Ritesh Sharma On 24/02/14 10:15 PM, Eric Blake ebl...@redhat.com wrote: On 02/24/2014 05:58 AM, Panday Ritesh Sharma (rpanday) wrote: [please don't top-post on technical lists] Hi Roman, Before I jump to the compilation of libvirt for QNX, I thought of compiling it on linux with my required options. So that I will be knowing what all files are of my use (from compilation log). For that I ran ./configure with below option and then tried 'make'. But 'make' complains there is no 'makefile' and I need to run './configure' before I run 'make'. Please see the log below. Am I missing any thing here ? checking whether to compile with virtual port support... yes checking for LIBNL... no configure: error: libnl-devel = 1.1 is required for macvtap support You missed reading this error message. You either need libnl-devel installed, or to pass additional --without-* options to configure that avoid whatever was assuming that libnl was required (based on the error message, you might have luck with './configure --without-macvtap' if you aren't in the mood to install things). It may also be worth patching libvirt to behave saner by automatically avoiding macvtap when libnl is not available; patches are welcome, but it's lower priority for most developers, since most of us tend to build on machines with all the prereqs installed rather than focusing on minimal builds. blr-vxr-052~$ make There seems to be no Makefile in this directory. You must run ./configure before running `make'. make: *** [abort-due-to-no-makefile] Error 1 blr-vxr-052~$ Therefore it is no surprise that there was no makefile created. Oftentimes, I recommend using './configure make' rather than './configure; make', so that 'make' is not attempted if configure fails. -- Eric Blake eblake redhat com+1-919-301-3266 Libvirt virtualization library http://libvirt.org -- libvir-list mailing list libvir-list@redhat.com https://www.redhat.com/mailman/listinfo/libvir-list
Re: [libvirt] Compiling libvirt RPC client library for QNX
On Tue, Feb 25, 2014 at 03:10:59PM +, Panday Ritesh Sharma (rpanday) wrote: Hi Eric, I used the option '--without-macvtap' and I was able to compile on my linux box. When I compiled, I see many libraries are getting built. But as I have explained my requirement earlier, I just need a RPC client library, essentially the option '--with-remote'. You can do a client build by turning off the libvirtd daemon with --without-libvirtd, and then also disabling any other pieces you don't want using --without- - see the output of 'configure --help' for info on all the options available. If I check .c files I see only './src/libvirt.c' and './tools/virsh.c' are the two files where '# ifdef WITH_REMOTE' is present. Does it mean that as per my requirement I only need to compile these files? My intent is to have a library with minimal files which suffice to my requirement. Because that way it will be easier for me to compile them on QNX. You have mentioned on another thread that in a weeks time some new version of libvirt will come which we can compile for non-linux machines ? What change is coming in that version ? The latest version of libvirt can not be compiled for QNX ? Libvirt aims to write portable code for as many platforms as is practical. Currently we officially aim to support Linux (all modern flavours), FreeBSD, Windows via Mingw64 and OS-X because those are the ones where we have contributors who do regular testing. To the best of my knowledge we don't have any contributors who doing testing on QNX, so we can't make any guarantees about any version of libvirt being able to work on QNX. We need someone who has access to QNX to try libvirt on QNX, report any compilation problems encountered and write + test fixes for them. So if you're able to do this please report problems you find... Regards, Daniel -- |: http://berrange.com -o-http://www.flickr.com/photos/dberrange/ :| |: http://libvirt.org -o- http://virt-manager.org :| |: http://autobuild.org -o- http://search.cpan.org/~danberr/ :| |: http://entangle-photo.org -o- http://live.gnome.org/gtk-vnc :| -- libvir-list mailing list libvir-list@redhat.com https://www.redhat.com/mailman/listinfo/libvir-list
Re: [libvirt] Compiling libvirt RPC client library for QNX
On 02/25/2014 08:10 AM, Panday Ritesh Sharma (rpanday) wrote: Once again, please don't top-post on technical lists. Hi Eric, I used the option '--without-macvtap' and I was able to compile on my linux box. When I compiled, I see many libraries are getting built. But as I have explained my requirement earlier, I just need a RPC client library, essentially the option '--with-remote'. To build just the client library, use ./configure --without-libvirtd. If I check .c files I see only './src/libvirt.c' and './tools/virsh.c' are the two files where '# ifdef WITH_REMOTE' is present. Does it mean that as per my requirement I only need to compile these files? No. You must unpack the ENTIRE tarball, and then use the configure options to control which files are built. Some of the logic on what to build is in the makefiles, and another consideration is that there are a LOT of library files that are used in both libvirt.so (your client library) and in libvirtd (the daemon executable that you are not building). My intent is to have a library with minimal files which suffice to my requirement. Because that way it will be easier for me to compile them on QNX. Using configure options to compile fewer files is reasonable. Omitting files from the tarball is not. You have mentioned on another thread that in a weeks time some new version of libvirt will come which we can compile for non-linux machines ? What change is coming in that version ? The latest version of libvirt can not be compiled for QNX ? The latest version is currently 1.2.1, but 1.2.2-rc0 was just announced and 1.2.2 is expected next week if all goes well. If you could test 1.2.2-rc0 on QNX, we can still fix issues that you turn up before 1.2.2 goes stable. -- Eric Blake eblake redhat com+1-919-301-3266 Libvirt virtualization library http://libvirt.org signature.asc Description: OpenPGP digital signature -- libvir-list mailing list libvir-list@redhat.com https://www.redhat.com/mailman/listinfo/libvir-list
Re: [libvirt] Compiling libvirt RPC client library for QNX
Hi Daniel, I ran ./configure command with below options. I found these options in on of the mail replied by you. But still 'make' is compiling so many files. My question is, as I need only RPC client library (I can explain you more, what I want to do with this libvirt client library on QNX), do I need to compile a huge number of .c files and need to build so many .lo ? Yes, I do have access to qnx, I need your help to compile this on QNX. Later I will test and discuss the issue if I face any. blr-vxr-052~$ ./configure --enable-compile-warnings=error --without-xen --without-qemu--without-openvz --without-lxc --without-vbox --without-xenapi --without-esx --without-uml --without-sasl --without-avahi--without-polkit --without-python--without-libvirtd --without-phyp--without-hyperv--without-netcf --without-audit --without-dtrace --without-macvtap Regards Ritesh Sharma On 25/02/14 8:52 PM, Daniel P. Berrange berra...@redhat.com wrote: On Tue, Feb 25, 2014 at 03:10:59PM +, Panday Ritesh Sharma (rpanday) wrote: Hi Eric, I used the option '--without-macvtap' and I was able to compile on my linux box. When I compiled, I see many libraries are getting built. But as I have explained my requirement earlier, I just need a RPC client library, essentially the option '--with-remote'. You can do a client build by turning off the libvirtd daemon with --without-libvirtd, and then also disabling any other pieces you don't want using --without- - see the output of 'configure --help' for info on all the options available. If I check .c files I see only './src/libvirt.c' and './tools/virsh.c' are the two files where '# ifdef WITH_REMOTE' is present. Does it mean that as per my requirement I only need to compile these files? My intent is to have a library with minimal files which suffice to my requirement. Because that way it will be easier for me to compile them on QNX. You have mentioned on another thread that in a weeks time some new version of libvirt will come which we can compile for non-linux machines ? What change is coming in that version ? The latest version of libvirt can not be compiled for QNX ? Libvirt aims to write portable code for as many platforms as is practical. Currently we officially aim to support Linux (all modern flavours), FreeBSD, Windows via Mingw64 and OS-X because those are the ones where we have contributors who do regular testing. To the best of my knowledge we don't have any contributors who doing testing on QNX, so we can't make any guarantees about any version of libvirt being able to work on QNX. We need someone who has access to QNX to try libvirt on QNX, report any compilation problems encountered and write + test fixes for them. So if you're able to do this please report problems you find... Regards, Daniel -- |: http://berrange.com -o- http://www.flickr.com/photos/dberrange/ :| |: http://libvirt.org -o- http://virt-manager.org :| |: http://autobuild.org -o- http://search.cpan.org/~danberr/ :| |: http://entangle-photo.org -o- http://live.gnome.org/gtk-vnc :| -- libvir-list mailing list libvir-list@redhat.com https://www.redhat.com/mailman/listinfo/libvir-list
Re: [libvirt] Compiling libvirt RPC client library for QNX
On 25/02/14 9:18 PM, Panday Ritesh Sharma (rpanday) rpan...@cisco.com wrote: Hi Roman, Sorry !!! I did not understand Once again, please don't top-post on technical lists. I should not include 'libvirt-l...@redhat.com' in my mail thread ? I have already used the option '--without-libvirtd' and hence the result. We are using a wrapper of make for compilation for QNX. So I need to know, when I am compiling this client library on linux with '--without-libvirtd' option, what all .c files and libraries are being used. Then I will take those .c files to my build environment and link that to the libraries needed. I will have to see whether those libraries are present in my QNX build environment. Please helpŠ Regards Ritesh Sharma On 25/02/14 8:57 PM, Eric Blake ebl...@redhat.com wrote: On 02/25/2014 08:10 AM, Panday Ritesh Sharma (rpanday) wrote: Once again, please don't top-post on technical lists. Hi Eric, I used the option '--without-macvtap' and I was able to compile on my linux box. When I compiled, I see many libraries are getting built. But as I have explained my requirement earlier, I just need a RPC client library, essentially the option '--with-remote'. To build just the client library, use ./configure --without-libvirtd. If I check .c files I see only './src/libvirt.c' and './tools/virsh.c' are the two files where '# ifdef WITH_REMOTE' is present. Does it mean that as per my requirement I only need to compile these files? No. You must unpack the ENTIRE tarball, and then use the configure options to control which files are built. Some of the logic on what to build is in the makefiles, and another consideration is that there are a LOT of library files that are used in both libvirt.so (your client library) and in libvirtd (the daemon executable that you are not building). My intent is to have a library with minimal files which suffice to my requirement. Because that way it will be easier for me to compile them on QNX. Using configure options to compile fewer files is reasonable. Omitting files from the tarball is not. You have mentioned on another thread that in a weeks time some new version of libvirt will come which we can compile for non-linux machines ? What change is coming in that version ? The latest version of libvirt can not be compiled for QNX ? The latest version is currently 1.2.1, but 1.2.2-rc0 was just announced and 1.2.2 is expected next week if all goes well. If you could test 1.2.2-rc0 on QNX, we can still fix issues that you turn up before 1.2.2 goes stable. -- Eric Blake eblake redhat com+1-919-301-3266 Libvirt virtualization library http://libvirt.org Adding [libvirt-list] Hi Eric, This time I am writing a the bottom of this thread, is this correct ? Write way of mailing ? Could you please reply my query ? Regards Ritesh Sharma -- libvir-list mailing list libvir-list@redhat.com https://www.redhat.com/mailman/listinfo/libvir-list
Re: [libvirt] Compiling libvirt RPC client library for QNX
On Tue, Feb 25, 2014 at 03:39:58PM +, Panday Ritesh Sharma (rpanday) wrote: Hi Daniel, I ran ./configure command with below options. I found these options in on of the mail replied by you. But still 'make' is compiling so many files. My question is, as I need only RPC client library (I can explain you more, what I want to do with this libvirt client library on QNX), do I need to compile a huge number of .c files and need to build so many .lo ? Yes, I do have access to qnx, I need your help to compile this on QNX. Later I will test and discuss the issue if I face any. blr-vxr-052~$ ./configure --enable-compile-warnings=error --without-xen --without-qemu--without-openvz --without-lxc --without-vbox --without-xenapi --without-esx --without-uml --without-sasl --without-avahi--without-polkit --without-python--without-libvirtd --without-phyp--without-hyperv--without-netcf --without-audit --without-dtrace --without-macvtap You could also add --without-vmware --without-parallels --without-test but aside from that the list of .c files compiled with this configure invocation is an accurate minimum. Regards, Daniel -- |: http://berrange.com -o-http://www.flickr.com/photos/dberrange/ :| |: http://libvirt.org -o- http://virt-manager.org :| |: http://autobuild.org -o- http://search.cpan.org/~danberr/ :| |: http://entangle-photo.org -o- http://live.gnome.org/gtk-vnc :| -- libvir-list mailing list libvir-list@redhat.com https://www.redhat.com/mailman/listinfo/libvir-list
Re: [libvirt] Compiling libvirt RPC client library for QNX
On 25/02/14 10:03 PM, Daniel P. Berrange berra...@redhat.com wrote: On Tue, Feb 25, 2014 at 03:39:58PM +, Panday Ritesh Sharma (rpanday) wrote: Hi Daniel, I ran ./configure command with below options. I found these options in on of the mail replied by you. But still 'make' is compiling so many files. My question is, as I need only RPC client library (I can explain you more, what I want to do with this libvirt client library on QNX), do I need to compile a huge number of .c files and need to build so many .lo ? Yes, I do have access to qnx, I need your help to compile this on QNX. Later I will test and discuss the issue if I face any. blr-vxr-052~$ ./configure --enable-compile-warnings=error --without-xen --without-qemu--without-openvz --without-lxc --without-vbox --without-xenapi --without-esx --without-uml --without-sasl --without-avahi--without-polkit --without-python --without-libvirtd --without-phyp--without-hyperv--without-netcf --without-audit --without-dtrace --without-macvtap You could also add --without-vmware --without-parallels --without-test but aside from that the list of .c files compiled with this configure invocation is an accurate minimum. Regards, Daniel -- |: http://berrange.com -o- http://www.flickr.com/photos/dberrange/ :| |: http://libvirt.org -o- http://virt-manager.org :| |: http://autobuild.org -o- http://search.cpan.org/~danberr/ :| |: http://entangle-photo.org -o- http://live.gnome.org/gtk-vnc :| Hi Daniel, I added these new options and compiled. Now I have to do same exercise in my build environment for QNX. Do you have any idea whether 'configure' utility will work on QNX ? Regards Ritesh Sharma -- libvir-list mailing list libvir-list@redhat.com https://www.redhat.com/mailman/listinfo/libvir-list
Re: [libvirt] Compiling libvirt RPC client library for QNX
On Tue, Feb 25, 2014 at 05:00:47PM +, Panday Ritesh Sharma (rpanday) wrote: On 25/02/14 10:03 PM, Daniel P. Berrange berra...@redhat.com wrote: On Tue, Feb 25, 2014 at 03:39:58PM +, Panday Ritesh Sharma (rpanday) wrote: Hi Daniel, I ran ./configure command with below options. I found these options in on of the mail replied by you. But still 'make' is compiling so many files. My question is, as I need only RPC client library (I can explain you more, what I want to do with this libvirt client library on QNX), do I need to compile a huge number of .c files and need to build so many .lo ? Yes, I do have access to qnx, I need your help to compile this on QNX. Later I will test and discuss the issue if I face any. blr-vxr-052~$ ./configure --enable-compile-warnings=error --without-xen --without-qemu--without-openvz --without-lxc --without-vbox --without-xenapi --without-esx --without-uml --without-sasl --without-avahi--without-polkit --without-python --without-libvirtd --without-phyp--without-hyperv--without-netcf --without-audit --without-dtrace --without-macvtap You could also add --without-vmware --without-parallels --without-test but aside from that the list of .c files compiled with this configure invocation is an accurate minimum. I added these new options and compiled. Now I have to do same exercise in my build environment for QNX. Do you have any idea whether 'configure' utility will work on QNX ? I've no idea really. If QNX is sufficiently POSIX compatible then it should mostly work, but I'm not aware of anyone having used libvirt on QNX yet. Just try it and let us know what happens Regards, Daniel -- |: http://berrange.com -o-http://www.flickr.com/photos/dberrange/ :| |: http://libvirt.org -o- http://virt-manager.org :| |: http://autobuild.org -o- http://search.cpan.org/~danberr/ :| |: http://entangle-photo.org -o- http://live.gnome.org/gtk-vnc :| -- libvir-list mailing list libvir-list@redhat.com https://www.redhat.com/mailman/listinfo/libvir-list
Re: [libvirt] Compiling libvirt RPC client library for QNX
On 02/25/2014 09:05 AM, Panday Ritesh Sharma (rpanday) wrote: We are using a wrapper of make for compilation for QNX. So I need to know, when I am compiling this client library on linux with '--without-libvirtd' option, what all .c files and libraries are being used. Then I will take those .c files to my build environment and link that to the libraries needed. I will have to see whether those libraries are present in my QNX build environment. Please helpŠ That feels awkward. Does QNX have a POSIX-compatible /bin/sh? If so, just unpack the tarball there, and run ./configure on your QNX machine the same way you do on Linux. I'm not personally familiar enough with QNX to know what build environment it provides. It may also be a situation where people tend to cross-compile for QNX rather than building natively. Libvirt supports cross-compilation (we build mingw client-only binaries under Fedora, so that setup could be copied for compiling client-only QNX binaries if you have a qnx cross-compiler on Linux). But at this point, you are pioneering new ground with regards to libvirt, and you will probably have to seek more help from people familiar with QNX compilation, as this list doesn't have the expertise with your system. Feel free to post build logs, and we can still try to help decipher them, but if you hit failures, you will probably have to be the one to do the legwork to resolve them. Hi Eric, This time I am writing a the bottom of this thread, is this correct ? Yes, thanks! -- Eric Blake eblake redhat com+1-919-301-3266 Libvirt virtualization library http://libvirt.org signature.asc Description: OpenPGP digital signature -- libvir-list mailing list libvir-list@redhat.com https://www.redhat.com/mailman/listinfo/libvir-list
Re: [libvirt] Compiling libvirt RPC client library for QNX
On 25/02/14 11:17 PM, Eric Blake ebl...@redhat.com wrote: On 02/25/2014 09:05 AM, Panday Ritesh Sharma (rpanday) wrote: We are using a wrapper of make for compilation for QNX. So I need to know, when I am compiling this client library on linux with '--without-libvirtd' option, what all .c files and libraries are being used. Then I will take those .c files to my build environment and link that to the libraries needed. I will have to see whether those libraries are present in my QNX build environment. Please helpŠ That feels awkward. Does QNX have a POSIX-compatible /bin/sh? If so, just unpack the tarball there, and run ./configure on your QNX machine the same way you do on Linux. I'm not personally familiar enough with QNX to know what build environment it provides. It may also be a situation where people tend to cross-compile for QNX rather than building natively. Libvirt supports cross-compilation (we build mingw client-only binaries under Fedora, so that setup could be copied for compiling client-only QNX binaries if you have a qnx cross-compiler on Linux). But at this point, you are pioneering new ground with regards to libvirt, and you will probably have to seek more help from people familiar with QNX compilation, as this list doesn't have the expertise with your system. Feel free to post build logs, and we can still try to help decipher them, but if you hit failures, you will probably have to be the one to do the legwork to resolve them. Hi Eric, This time I am writing a the bottom of this thread, is this correct ? Yes, thanks! -- Eric Blake eblake redhat com+1-919-301-3266 Libvirt virtualization library http://libvirt.org Hi Eric, Yes you are right, we cross compile for QNX. I am here in touch with my build team to find how can we use './configure' and 'make' on my compilation machine and compile these tar boll. Regards Ritesh Sharma -- libvir-list mailing list libvir-list@redhat.com https://www.redhat.com/mailman/listinfo/libvir-list
Re: [libvirt] Compiling libvirt RPC client library for QNX
Panday Ritesh Sharma (rpanday) wrote: Thanks Roman for your response. Few questions which are not answered in that link. As I mentioned, my intent is to get only libvirt client library on QNX side not the whole libvirt. The libvirt daemon will still be running on linux box. The QNX machine will only be sending the request to define/start/destroy the domain and would be interested in getting lifecycle event. In that case do I need to compile whole libvirt which is down loaded or only subset of that suffice ? If only subset is needed, what are those ? You can specify features to compile in via ./configure flags, e.g. you could disable building of libvirtd using '--without-libvirtd' flag. Please check the output of ./configure --help. Can you please pass me the link where I could get latest libvirt, as you said 0.9.8 is quite old. JFYI, my linux box is running below host version so I would need compatible libvirt. You can find download links here: http://libvirt.org/downloads.html Roman Bogorodskiy -- libvir-list mailing list libvir-list@redhat.com https://www.redhat.com/mailman/listinfo/libvir-list
Re: [libvirt] Compiling libvirt RPC client library for QNX
Hi Roman, Before I jump to the compilation of libvirt for QNX, I thought of compiling it on linux with my required options. So that I will be knowing what all files are of my use (from compilation log). For that I ran ./configure with below option and then tried 'make'. But 'make' complains there is no 'makefile' and I need to run './configure' before I run 'make'. Please see the log below. Am I missing any thing here ? blr-vxr-052~$ ./configure --enable-compile-warnings=error --without-xen --without-qemu--without-openvz --without-lxc --without-vbox --without-xenapi --without-esx --without-uml --without-sasl --without-avahi --without-polkit --without-python --without-libvirtd --without-phyp --without-hyperv --without-netcf --without-audit --without-dtrace checking for a BSD-compatible install... /usr/bin/install -c checking whether build environment is sane... yes checking for a thread-safe mkdir -p... /bin/mkdir -p checking for gawk... gawk checking whether make sets $(MAKE)... yes checking whether to disable maintainer-specific portions of Makefiles... yes checking build system type... x86_64-unknown-linux-gnu checking host system type... x86_64-unknown-linux-gnu checking for gcc... gcc checking whether the C compiler works... yes checking for C compiler default output file name... a.out checking for suffix of executables... checking whether we are cross compiling... no checking for suffix of object files... o checking whether we are using the GNU C compiler... yes checking whether gcc accepts -g... yes checking for gcc option to accept ISO C89... none needed checking for style of include used by make... GNU checking dependency style of gcc... gcc3 checking how to run the C preprocessor... gcc -E checking for gcc... (cached) gcc checking whether we are using the GNU C compiler... (cached) yes checking whether gcc accepts -g... (cached) yes checking for gcc option to accept ISO C89... (cached) none needed checking dependency style of gcc... (cached) gcc3 checking for grep that handles long lines and -e... /bin/grep checking for egrep... /bin/grep -E checking for Minix Amsterdam compiler... no checking for ar... ar checking for ranlib... ranlib checking whether gcc and cc understand -c and -o together... yes 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 minix/config.h usability... no checking minix/config.h presence... no checking for minix/config.h... no checking whether it is safe to define __EXTENSIONS__... yes checking for _LARGEFILE_SOURCE value needed for large files... no checking for special C compiler options needed for large files... no checking for _FILE_OFFSET_BITS value needed for large files... no checking for gcc option to accept ISO C99... -std=gnu99 checking for gcc -std=gnu99 option to accept ISO Standard C... (cached) -std=gnu99 checking for inline... inline checking sys/socket.h usability... yes checking sys/socket.h presence... yes checking for sys/socket.h... yes checking arpa/inet.h usability... yes checking arpa/inet.h presence... yes checking for arpa/inet.h... yes checking features.h usability... yes checking features.h presence... yes checking for features.h... yes checking sys/param.h usability... yes checking sys/param.h presence... yes checking for sys/param.h... yes checking for unistd.h... (cached) yes checking wctype.h usability... yes checking wctype.h presence... yes checking for wctype.h... yes checking netdb.h usability... yes checking netdb.h presence... yes checking for netdb.h... yes checking netinet/in.h usability... yes checking netinet/in.h presence... yes checking for netinet/in.h... yes checking stdio_ext.h usability... yes checking stdio_ext.h presence... yes checking for stdio_ext.h... yes checking termios.h usability... yes checking termios.h presence... yes checking for termios.h... yes checking sys/time.h usability... yes checking sys/time.h presence... yes checking for sys/time.h... yes checking sys/mman.h usability... yes checking sys/mman.h presence... yes checking for sys/mman.h... yes checking pty.h usability... yes checking pty.h presence... yes checking for pty.h... yes checking poll.h usability... yes checking poll.h presence... yes checking for poll.h... yes checking sys/ioctl.h usability... yes checking sys/ioctl.h presence... yes checking for sys/ioctl.h... yes checking sys/filio.h usability... no checking sys/filio.h presence... no checking for sys/filio.h... no checking pthread.h usability... yes checking pthread.h presence... yes checking for pthread.h... yes checking sched.h usability... yes checking sched.h presence... yes checking for sched.h... yes checking sys/select.h usability... yes checking sys/select.h presence... yes checking for sys/select.h... yes checking
Re: [libvirt] Compiling libvirt RPC client library for QNX
On 02/24/2014 05:58 AM, Panday Ritesh Sharma (rpanday) wrote: [please don't top-post on technical lists] Hi Roman, Before I jump to the compilation of libvirt for QNX, I thought of compiling it on linux with my required options. So that I will be knowing what all files are of my use (from compilation log). For that I ran ./configure with below option and then tried 'make'. But 'make' complains there is no 'makefile' and I need to run './configure' before I run 'make'. Please see the log below. Am I missing any thing here ? checking whether to compile with virtual port support... yes checking for LIBNL... no configure: error: libnl-devel = 1.1 is required for macvtap support You missed reading this error message. You either need libnl-devel installed, or to pass additional --without-* options to configure that avoid whatever was assuming that libnl was required (based on the error message, you might have luck with './configure --without-macvtap' if you aren't in the mood to install things). It may also be worth patching libvirt to behave saner by automatically avoiding macvtap when libnl is not available; patches are welcome, but it's lower priority for most developers, since most of us tend to build on machines with all the prereqs installed rather than focusing on minimal builds. blr-vxr-052~$ make There seems to be no Makefile in this directory. You must run ./configure before running `make'. make: *** [abort-due-to-no-makefile] Error 1 blr-vxr-052~$ Therefore it is no surprise that there was no makefile created. Oftentimes, I recommend using './configure make' rather than './configure; make', so that 'make' is not attempted if configure fails. -- Eric Blake eblake redhat com+1-919-301-3266 Libvirt virtualization library http://libvirt.org signature.asc Description: OpenPGP digital signature -- libvir-list mailing list libvir-list@redhat.com https://www.redhat.com/mailman/listinfo/libvir-list
Re: [libvirt] Compiling libvirt RPC client library for QNX
On 02/22/2014 12:47 PM, Panday Ritesh Sharma (rpanday) wrote: HI Team, I have downloaded the libvirt source code from libvirt_0.9.8.orig.tar.gzhttps://launchpad.net/ubuntu/+archive/primary/+files/libvirt_0.9.8.orig.tar.gz . I just wanted libvirt RPC client library to be compiled for QNX. 0.9.8 is really old. I'd highly recommend trying a newer client, such as 1.2.1 (or wait a week for 1.2.2) - we have fixed bugs in the meantime where older packages did not build as well for non-Linux machines. -- Eric Blake eblake redhat com+1-919-301-3266 Libvirt virtualization library http://libvirt.org signature.asc Description: OpenPGP digital signature -- libvir-list mailing list libvir-list@redhat.com https://www.redhat.com/mailman/listinfo/libvir-list
Re: [libvirt] Compiling libvirt RPC client library for QNX
Thanks Roman for your response. Few questions which are not answered in that link. As I mentioned, my intent is to get only libvirt client library on QNX side not the whole libvirt. The libvirt daemon will still be running on linux box. The QNX machine will only be sending the request to define/start/destroy the domain and would be interested in getting lifecycle event. In that case do I need to compile whole libvirt which is down loaded or only subset of that suffice ? If only subset is needed, what are those ? Can you please pass me the link where I could get latest libvirt, as you said 0.9.8 is quite old. JFYI, my linux box is running below host version so I would need compatible libvirt. Linux host OS : gcc version 4.4.1 (Wind River Linux Sourcery G++ 4.4a-341) Regards Ritesh Sharma On 23/02/14 3:18 AM, Roman Bogorodskiy bogorods...@gmail.com wrote: Panday Ritesh Sharma (rpanday) wrote: HI Team, I have downloaded the libvirt source code from libvirt_0.9.8.orig.tar.gzhttps://launchpad.net/ubuntu/+archive/primary/+ files/libvirt_0.9.8.orig.tar.gz . I just wanted libvirt RPC client library to be compiled for QNX. My remote box which is running QNX would like to establish libvirt connection with linux box to launch virtual domains/VMs and would also like to get lifecycle events. Could you please let me know what all directory/files I need to compile which I have got from libvirt_0.9.8.orig.tar.gzhttps://launchpad.net/ubuntu/+archive/primary/+ files/libvirt_0.9.8.orig.tar.gz ? While browsing through net I found the files available under src/util, src/conf, src/rpc, src/remote, are sufficient for client RPC library? Is this correct or I need to include any other files ? Is there any instruction or help available which I can use to compile this library for QNX ? Hi, The instruction is available here: http://libvirt.org/compiling.html#compiling I'm not sure it compiles on QNX though. PS 0.9.8 is quite old, you could consider getting more recent version. Roman Bogorodskiy -- libvir-list mailing list libvir-list@redhat.com https://www.redhat.com/mailman/listinfo/libvir-list
Re: [libvirt] Compiling libvirt RPC client library for QNX
Hi Roman, In addition to my below queries, do I need any other library to compile libvirt, any pre-requisite is there ? Regards Ritesh Sharma On 23/02/14 3:52 PM, Panday Ritesh Sharma (rpanday) rpan...@cisco.com wrote: Thanks Roman for your response. Few questions which are not answered in that link. As I mentioned, my intent is to get only libvirt client library on QNX side not the whole libvirt. The libvirt daemon will still be running on linux box. The QNX machine will only be sending the request to define/start/destroy the domain and would be interested in getting lifecycle event. In that case do I need to compile whole libvirt which is down loaded or only subset of that suffice ? If only subset is needed, what are those ? Can you please pass me the link where I could get latest libvirt, as you said 0.9.8 is quite old. JFYI, my linux box is running below host version so I would need compatible libvirt. Linux host OS : gcc version 4.4.1 (Wind River Linux Sourcery G++ 4.4a-341) Regards Ritesh Sharma On 23/02/14 3:18 AM, Roman Bogorodskiy bogorods...@gmail.com wrote: Panday Ritesh Sharma (rpanday) wrote: HI Team, I have downloaded the libvirt source code from libvirt_0.9.8.orig.tar.gzhttps://launchpad.net/ubuntu/+archive/primary/ + files/libvirt_0.9.8.orig.tar.gz . I just wanted libvirt RPC client library to be compiled for QNX. My remote box which is running QNX would like to establish libvirt connection with linux box to launch virtual domains/VMs and would also like to get lifecycle events. Could you please let me know what all directory/files I need to compile which I have got from libvirt_0.9.8.orig.tar.gzhttps://launchpad.net/ubuntu/+archive/primary/ + files/libvirt_0.9.8.orig.tar.gz ? While browsing through net I found the files available under src/util, src/conf, src/rpc, src/remote, are sufficient for client RPC library? Is this correct or I need to include any other files ? Is there any instruction or help available which I can use to compile this library for QNX ? Hi, The instruction is available here: http://libvirt.org/compiling.html#compiling I'm not sure it compiles on QNX though. PS 0.9.8 is quite old, you could consider getting more recent version. Roman Bogorodskiy -- libvir-list mailing list libvir-list@redhat.com https://www.redhat.com/mailman/listinfo/libvir-list
Re: [libvirt] Compiling libvirt RPC client library for QNX
Panday Ritesh Sharma (rpanday) wrote: HI Team, I have downloaded the libvirt source code from libvirt_0.9.8.orig.tar.gzhttps://launchpad.net/ubuntu/+archive/primary/+files/libvirt_0.9.8.orig.tar.gz . I just wanted libvirt RPC client library to be compiled for QNX. My remote box which is running QNX would like to establish libvirt connection with linux box to launch virtual domains/VMs and would also like to get lifecycle events. Could you please let me know what all directory/files I need to compile which I have got from libvirt_0.9.8.orig.tar.gzhttps://launchpad.net/ubuntu/+archive/primary/+files/libvirt_0.9.8.orig.tar.gz ? While browsing through net I found the files available under src/util, src/conf, src/rpc, src/remote, are sufficient for client RPC library? Is this correct or I need to include any other files ? Is there any instruction or help available which I can use to compile this library for QNX ? Hi, The instruction is available here: http://libvirt.org/compiling.html#compiling I'm not sure it compiles on QNX though. PS 0.9.8 is quite old, you could consider getting more recent version. Roman Bogorodskiy -- libvir-list mailing list libvir-list@redhat.com https://www.redhat.com/mailman/listinfo/libvir-list
