From bitdealer at gmail.com Mon Nov 17 19:03:21 2008 From: bitdealer at gmail.com (Stephan Kleine) Date: Mon, 17 Nov 2008 19:03:21 +0100 Subject: [Openvas-distro] oO openvas-libraries-2.0.0.beta2 requires glib-2.0 >= 2.2.0 Message-ID: Hi folks. I today tried to build Beta 2 packages and failed cause it claims that glib-2.0 >= 2.2.0 would be required. Are you serious about this? Even openSUSE 11.1, which will be released in december, only contains glib2-2.16.1 and I kinda doubt that there are any other distros that come with 2.2.x. Please confirm / consider this since it would require using a new glib version just to get openvas running - which is kinda ... ;) best regards Stephan From bitdealer at gmail.com Mon Nov 17 19:47:44 2008 From: bitdealer at gmail.com (Stephan Kleine) Date: Mon, 17 Nov 2008 19:47:44 +0100 Subject: [Openvas-distro] oO openvas-libraries-2.0.0.beta2 requires glib-2.0 >= 2.2.0 In-Reply-To: References: Message-ID: Sorry, nevermind, I miserably failed at reading numbers ... ;D From bitdealer at gmail.com Mon Nov 17 21:59:48 2008 From: bitdealer at gmail.com (Stephan Kleine) Date: Mon, 17 Nov 2008 21:59:48 +0100 Subject: [Openvas-distro] Problems with building beta2 packages Message-ID: Hello again. After playing around with it some more I found a few problems (which hopefully don't result from some misreading this time): 1. openvas-client seems to build just fine. 2. openvas-libraries: In Fedora, Mandriva and openSUSE pre Factory (11.1) the files are called /usr/lib/libopenvas.2 and /usr/lib/libopenvas_hg.2 instead of /usr/lib/libopenvas.so.2 and /usr/lib/libopenvas.so.2 (note the .so.) while they are correctly named in Factory (11.1 development) for some unknown reason. Could you please fix your configuration so that the files are named with .so. everywhere like it was in previous versions as well and it is common practice? Also calling "autoreconf -fi" in %build before %configure results in loads of "warning: missing template:" stuff - e.g. BSDI BSD_BYTE_ORDERING DARWIN DEBUG_STORE ... - which shouldn't happen either afaik. 3. openvas-libnasl: As you can see at http://pastebin.ca/1259696 the build fails because it doesn't find some files that where compiled under "nasl/.libs". If I move them up into the correct directory ("nasl") it complains that "-lopenvas" can not be found. I'm not sure if this is related to the wrong naming of the files in openvas-libraries and the absence of a /usr/lib/libopenvas.so (as you know I'm not much a C guy). Sp please have a look at this. As always I'm happy to try out any suggested fixes and, of course, you are more than welcome to play around with it yourself. The packages can be found at https://build.opensuse.org/project/show?project=home%3Abitshuffler%3Aopenvas%3Aunstable best regards Stephan From timb at nth-dimension.org.uk Mon Nov 17 23:15:07 2008 From: timb at nth-dimension.org.uk (Tim Brown) Date: Mon, 17 Nov 2008 22:15:07 +0000 Subject: [Openvas-distro] Problems with building beta2 packages In-Reply-To: References: Message-ID: <200811172215.07656.timb@nth-dimension.org.uk> On Monday 17 November 2008 20:59:48 Stephan Kleine wrote: > Hello again. > > > After playing around with it some more I found a few problems (which > hopefully don't result from some misreading this time): > > 1. openvas-client seems to build just fine. > > 2. openvas-libraries: In Fedora, Mandriva and openSUSE pre Factory > (11.1) the files are called /usr/lib/libopenvas.2 and > /usr/lib/libopenvas_hg.2 instead of /usr/lib/libopenvas.so.2 and > /usr/lib/libopenvas.so.2 (note the .so.) while they are correctly > named in Factory (11.1 development) for some unknown reason. This can be resolved by calling libtoolize, Debian unstable suffers from the same problem, but I haven't tracked down why. > Also calling "autoreconf -fi" in %build before %configure results in > loads of "warning: missing template:" stuff - e.g. BSDI > BSD_BYTE_ORDERING DARWIN DEBUG_STORE ... - which shouldn't happen > either afaik. Not seen that myself. The Debian build scripts don't call autoreconf though. > 3. openvas-libnasl: As you can see at http://pastebin.ca/1259696 the > build fails because it doesn't find some files that where compiled > under "nasl/.libs". If I move them up into the correct directory > ("nasl") it complains that "-lopenvas" can not be found. I'm not sure > if this is related to the wrong naming of the files in > openvas-libraries and the absence of a /usr/lib/libopenvas.so (as you > know I'm not much a C guy). Quite possible, I can't see any reason why those files would be built under .libs. Perhaps someone with an RPM based distro can reproduce? Cheers, Tim -- Tim Brown From michael.wiegand at intevation.de Tue Nov 18 08:20:04 2008 From: michael.wiegand at intevation.de (Michael Wiegand) Date: Tue, 18 Nov 2008 08:20:04 +0100 Subject: [Openvas-distro] oO openvas-libraries-2.0.0.beta2 requires glib-2.0 >= 2.2.0 In-Reply-To: References: Message-ID: <20081118072004.GC15568@intevation.de> * Stephan Kleine [17. Nov 2008]: > Hi folks. > > I today tried to build Beta 2 packages and failed cause it claims that > glib-2.0 >= 2.2.0 would be required. > > Are you serious about this? Even openSUSE 11.1, which will be released > in december, only contains glib2-2.16.1 and I kinda doubt that there > are any other distros that come with 2.2.x. I've seen you've figured it out yourself, sorry for the confusion. :) For everybody who was wondering: The glib minor version numbers go beyond 9, so version 2.16 is indeed newer than version 2.2. Version 2.2 of glib was released in August 2003 AFAICT; at least this version should be available on all major *nix platforms. Version requirements for glib might rise in the long run, especially as we prepare to replace cruft in the code with glib implementations. But at least for the OpenVAS 1.0 and 2.0 series, glib 2.2 will be sufficient. But I can understand the configure error message might have lead to Stephans misunderstanding, I'll try to improve that (again). Any suggestions? Regards, Michael -- Michael Wiegand | OpenPGP key: D7D049EC | http://www.intevation.de/ Intevation GmbH, Neuer Graben 17, 49074 Osnabr?ck | AG Osnabr?ck, HR B 18998 Gesch?ftsf?hrer: Frank Koormann, Bernhard Reiter, Dr. Jan-Oliver Wagner From michael.wiegand at intevation.de Tue Nov 18 09:13:14 2008 From: michael.wiegand at intevation.de (Michael Wiegand) Date: Tue, 18 Nov 2008 09:13:14 +0100 Subject: [Openvas-distro] oO openvas-libraries-2.0.0.beta2 requires glib-2.0 >= 2.2.0 In-Reply-To: <20081118072004.GC15568@intevation.de> References: <20081118072004.GC15568@intevation.de> Message-ID: <20081118081314.GD15568@intevation.de> * Michael Wiegand [18. Nov 2008]: > Version 2.2 of glib was released in August 2003 AFAICT; at least this > version should be available on all major *nix platforms. > > Version requirements for glib might rise in the long run, especially as > we prepare to replace cruft in the code with glib implementations. But > at least for the OpenVAS 1.0 and 2.0 series, glib 2.2 will be > sufficient. Sorry for replying to my own mail, but I just looked into the issue a little deeper and it seems we do indeed require glib 2.6 already. Thanks to you and atomicturtle in #openvas for bringing this up, I'll fix that soon. Nevertheless, glib 2.6 was released in 2005 and should be available on most platforms as well. Regards, Michael -- Michael Wiegand | OpenPGP key: D7D049EC | http://www.intevation.de/ Intevation GmbH, Neuer Graben 17, 49074 Osnabr?ck | AG Osnabr?ck, HR B 18998 Gesch?ftsf?hrer: Frank Koormann, Bernhard Reiter, Dr. Jan-Oliver Wagner From bitdealer at gmail.com Tue Nov 18 17:20:27 2008 From: bitdealer at gmail.com (Stephan Kleine) Date: Tue, 18 Nov 2008 17:20:27 +0100 Subject: [Openvas-distro] Problems with building beta2 packages In-Reply-To: <200811172215.07656.timb@nth-dimension.org.uk> References: <200811172215.07656.timb@nth-dimension.org.uk> Message-ID: On Mon, Nov 17, 2008 at 11:15 PM, Tim Brown wrote: > On Monday 17 November 2008 20:59:48 Stephan Kleine wrote: >> Hello again. >> >> >> After playing around with it some more I found a few problems (which >> hopefully don't result from some misreading this time): >> >> 1. openvas-client seems to build just fine. >> >> 2. openvas-libraries: In Fedora, Mandriva and openSUSE pre Factory >> (11.1) the files are called /usr/lib/libopenvas.2 and >> /usr/lib/libopenvas_hg.2 instead of /usr/lib/libopenvas.so.2 and >> /usr/lib/libopenvas.so.2 (note the .so.) while they are correctly >> named in Factory (11.1 development) for some unknown reason. > > This can be resolved by calling libtoolize, Debian unstable suffers from the > same problem, but I haven't tracked down why. > Thanks, I solved it for the moment by calling "libtoolize --force" before %configure which results in correctly named files. >> Also calling "autoreconf -fi" in %build before %configure results in >> loads of "warning: missing template:" stuff - e.g. BSDI >> BSD_BYTE_ORDERING DARWIN DEBUG_STORE ... - which shouldn't happen >> either afaik. > > Not seen that myself. The Debian build scripts don't call autoreconf though. > The suse ones neither afaik. I was just under the impression that this should normally work just fine. >> 3. openvas-libnasl: As you can see at http://pastebin.ca/1259696 the >> build fails because it doesn't find some files that where compiled >> under "nasl/.libs". If I move them up into the correct directory >> ("nasl") it complains that "-lopenvas" can not be found. I'm not sure >> if this is related to the wrong naming of the files in >> openvas-libraries and the absence of a /usr/lib/libopenvas.so (as you >> know I'm not much a C guy). > > Quite possible, I can't see any reason why those files would be built > under .libs. Perhaps someone with an RPM based distro can reproduce? > The problem that it doesn't find the files bellow ".libs" apparently is that you use gcc and not libtool to build openvas-nasl which doesn't know where libtool put its stuff (See http://pastebin.ca/1259696 for the build log). The solution would be to use libtool to build openvas-nasl as well but I don't know how to do so, so the fix is up to you but I'll happily test it ;D The problem that "-lopenvas" can not be found is fixed by naming the libraries in openvas-libraries correctly. best regards Stephan From michael.wiegand at intevation.de Wed Nov 19 10:17:07 2008 From: michael.wiegand at intevation.de (Michael Wiegand) Date: Wed, 19 Nov 2008 10:17:07 +0100 Subject: [Openvas-distro] Problems with building beta2 packages In-Reply-To: References: <200811172215.07656.timb@nth-dimension.org.uk> Message-ID: <20081119091707.GB18497@intevation.de> * Stephan Kleine [18. Nov 2008]: > The problem that it doesn't find the files bellow ".libs" apparently > is that you use gcc and not libtool to build openvas-nasl which > doesn't know where libtool put its stuff (See > http://pastebin.ca/1259696 for the build log). The solution would be > to use libtool to build openvas-nasl as well but I don't know how to > do so, so the fix is up to you but I'll happily test it ;D This is indeed true, thank you for spotting this! It should be fixed with the last revision (1783), could you give that one a try and let me know if it works now? Regards, Michael -- Michael Wiegand | OpenPGP key: D7D049EC | http://www.intevation.de/ Intevation GmbH, Neuer Graben 17, 49074 Osnabr?ck | AG Osnabr?ck, HR B 18998 Gesch?ftsf?hrer: Frank Koormann, Bernhard Reiter, Dr. Jan-Oliver Wagner From bitdealer at gmail.com Wed Nov 19 15:57:08 2008 From: bitdealer at gmail.com (Stephan Kleine) Date: Wed, 19 Nov 2008 15:57:08 +0100 Subject: [Openvas-distro] Problems with building beta2 packages In-Reply-To: <20081119091707.GB18497@intevation.de> References: <200811172215.07656.timb@nth-dimension.org.uk> <20081119091707.GB18497@intevation.de> Message-ID: On Wed, Nov 19, 2008 at 10:17 AM, Michael Wiegand wrote: > * Stephan Kleine [18. Nov 2008]: >> The problem that it doesn't find the files bellow ".libs" apparently >> is that you use gcc and not libtool to build openvas-nasl which >> doesn't know where libtool put its stuff (See >> http://pastebin.ca/1259696 for the build log). The solution would be >> to use libtool to build openvas-nasl as well but I don't know how to >> do so, so the fix is up to you but I'll happily test it ;D > > This is indeed true, thank you for spotting this! It should be fixed with > the last revision (1783), could you give that one a try and let me know > if it works now? I tried revision 1793 but received the same error although indeed libtool now is used to build it. Full log is available at http://pastebin.ca/1261405 regards, Stephan From michael.wiegand at intevation.de Thu Nov 20 16:01:40 2008 From: michael.wiegand at intevation.de (Michael Wiegand) Date: Thu, 20 Nov 2008 16:01:40 +0100 Subject: [Openvas-distro] Problems with building beta2 packages In-Reply-To: References: <200811172215.07656.timb@nth-dimension.org.uk> <20081119091707.GB18497@intevation.de> Message-ID: <20081120150140.GC1575@intevation.de> * Stephan Kleine [20. Nov 2008]: > I tried revision 1793 but received the same error although indeed > libtool now is used to build it. Full log is available at > http://pastebin.ca/1261405 I was able to reproduce your error (although it took me some time ...), it seems to be related to the way configure handles the --disable-static flag. While I investigate this further, could you try a build without the --disable-static flag on your system and let me know if it succeeds? Thanks for spotting this, I'll keep you updated. Regards, Michael -- Michael Wiegand | OpenPGP key: D7D049EC | http://www.intevation.de/ Intevation GmbH, Neuer Graben 17, 49074 Osnabr?ck | AG Osnabr?ck, HR B 18998 Gesch?ftsf?hrer: Frank Koormann, Bernhard Reiter, Dr. Jan-Oliver Wagner From bitdealer at gmail.com Fri Nov 21 17:23:30 2008 From: bitdealer at gmail.com (Stephan Kleine) Date: Fri, 21 Nov 2008 17:23:30 +0100 Subject: [Openvas-distro] Problems with building beta2 packages In-Reply-To: <20081120150140.GC1575@intevation.de> References: <200811172215.07656.timb@nth-dimension.org.uk> <20081119091707.GB18497@intevation.de> <20081120150140.GC1575@intevation.de> Message-ID: > I was able to reproduce your error (although it took me some time ...), > it seems to be related to the way configure handles the --disable-static > flag. While I investigate this further, could you try a build without > the --disable-static flag on your system and let me know if it succeeds? Thanks for the hint, without --disable-static it worked. Now the good news is that it builds for Mandriva 2007 too but sadly openvas-libraries fails to build on openSUSE Factory - see http://rafb.net/p/RDB8Fz11.html for the build log. My list of things what should be improved / corrected is now the following: openvas-client: 1. stuff in "nessus" should append "-g" to compile flags like the makefile in "libnessus" does (same for stuff bellow "src" & "ssl") so valid debuging information can be retrieved. 2. shouldn't the localization files within "po" get build automatically - as in without requiring "cd po && make"? openvas-libraries: 1. it is necessary to run "libtoolize --force" to get correctly named .so files 2. it doesn't build on openSUSE Factory - see http://rafb.net/p/RDB8Fz11.html for the build log. openvas-libnasl: 1. it is necessary to run %configure without "--disable-static" Regarding how to reproduce this: It is actually very easy to do so if you use osc. The following is a short how to do this: 1. Go to http://build.opensuse.org/ and create an account (no worries you wont receive a single unwanted mail). 2. Go to http://download.opensuse.org/repositories/openSUSE:/Tools/ and add the subdirectory suiting your distribution / version as a repository and install "osc". 3. Check out a package: "osc co " - e.g. to get openvas-libraries from my unstable repo you do "osc co home:bitshuffler:openvas:unstable openvas-libraries". If needed it should prompt you for username & password of the account you created at 1.. 4. To build the package for a certain distribution / version & architecture run "osc build " - e.g. "osc build openSUSE_Factory i586 openvas-libraries.spec" - within the directory that contains the source & .spec files. This will retrieve all needed build dependencies, setup a minimal chroot environment (for which it will ask you for the root password) and then build the package within that chroot environment so your normal system will remain absolutely untouched. As you see it is very easy to do, so give it a try :) best regards Stephan