Well, until I'm mixing things up, is there any reason at all for sticking with some outdated version that was released more than 2 years ago? E.g. 1.3.12 was released like 40 hours ago.
So how about porting that patch to the current version and trying to get it into upstream so that patching has an end? Personally I tried building it once and couldn't be bothered to loose any more hairs after a few hours cause I don't need it anyways but since some people apparently want it it would be nice to offer packages for them. regards, Stephan @Matt: I'm somehow wondering where you got 0.1.16 from since it isn't tagged in their SVN: http://dev.zenoss.com/trac/browser/tags?rev=21516 On Wednesday July 21 2010 21:05:42 Matthew Coene wrote: > Holy Jebus, what a trial... Still not working but I am either delusional > as to my progress or possibly getting a little further along... > > I have previously tried to configure WMI support on my Ubuntu 10.04 box > using practically every iteration of possibilities... > > Autoconf (all varieties in the repo's) > Python, 2.4. 2.5, 2.6 and 3.1 > - with the OpenVAS patches and AutoConf 2.6 patches and without > - WMI 0.1.13 and today WMI 0.1.16 > > As it turns out with some manual kludging around I adapted the OpenVAS > patches and the WMI_Autoconf 2.6 patches to the new WMI_0.1.16 tarball > release... Python 2.6 was a disaster, so I installed all the Python3.1 > packages... (2.6 was seemingly a useless course of effort... everything > was broken regardless of what I tried.) > > I forced Python 3.1 with > > export PYTHON_VERSION=3.1 > > Believe it or not, I actually get (for the most part) a clean "./configure" > run. (At least a non-fatal iteration)... > > Now when I attempt the last piece of the puzzle... e.g. . make proto > wmi/libwmiclient.so, I get the following output.... > > Compiling wmi/winsmb.c > wmi/winsmb.c: In function âsmb_connectâ: > wmi/winsmb.c:123: warning: assignment makes pointer from integer without a > cast > wmi/winsmb.c:132: error: too many arguments to function âgensec_initâ > wmi/winsmb.c:143: error: too many arguments to function > âcli_credentials_set_confâ > wmi/winsmb.c:151: error: too many arguments to function âlp_smb_portsâ > wmi/winsmb.c:153: warning: passing argument 4 of âsmbcli_full_connectionâ > from incompatible pointer type > ./libcli/libcli_proto.h:34: note: expected âconst char *â but argument is > of type âconst char **â > wmi/winsmb.c:153: warning: passing argument 7 of âsmbcli_full_connectionâ > from incompatible pointer type > ./libcli/libcli_proto.h:34: note: expected âstruct event_context *â but > argument is of type âstruct cli_credentials *â > wmi/winsmb.c:153: error: too many arguments to function > âsmbcli_full_connectionâ > The following command failed: > gcc -Ilib/replace -Ilib/talloc -Ilib/tdb/include -Iheimdal_build > -Iheimdal/lib/roken -Ilib/socket_wrapper -Iheimdal/lib/des > -Iheimdal/lib/com_err -Iheimdal/lib/asn1 -Iheimdal/lib/krb5 > -Iheimdal/lib/hdb -Iheimdal/lib/gssapi/spnego -Iheimdal/lib/gssapi > -Iheimdal/lib/gssapi/krb5 -I heimdal/lib/gssapi/mech -Ilib/popt > -I./include -I. -I./lib -I./lib/replace -D_SAMBA_BUILD_=4 -DHAVE_CONFIG_H > -fPIC -c wmi/winsmb.c -o wmi/winsmb.o > make: *** [wmi/winsmb.o] Error 1 > > BAH.... So close... I can almost taste victory... Sort of tastes like blood > as I have been gnawing on my lip in frustration for a looooooong > time... ;-) > > Knowing this would it be better for me to keep pursuing this course of > action, or wait for someone who actually knows what they are doing to help > with a functional release / instruction set....??? > > Maybe all these efforts can be used to help someone else not have to jump > through all the hoops the whole way like I have??? I am thinking it might > just be a function / syntax variation like between using Python 2.6 and > 3.1... I got similar but not identical errors at one point using Python 2.4 > vs. 2.6..... > > Cheers, > > > Matt > > > ______________________________________________________________________ > This email has been scanned by the MessageLabs Email Security System. > For more information please visit http://www.messagelabs.com/email > ______________________________________________________________________ > _______________________________________________ > Openvas-discuss mailing list > [email protected] > http://lists.wald.intevation.org/mailman/listinfo/openvas-discuss _______________________________________________ Openvas-discuss mailing list [email protected] http://lists.wald.intevation.org/mailman/listinfo/openvas-discuss
