Jan-Oliver Wagner wrote:
> On Sunday 14 December 2008 02:31:52 Joey Schulze wrote:
> > Tim Brown wrote:
> > > > > > for the libraries. BTW if you're using Unbutu, there are packaging
> > > > > > files under packaging/debian that can be used to build packages and
> > > > > > which are maintained by OpenVAS developers associated with Debian.
> > > >
> > > > Just to add to this I had the exact same problem, with the same
> > > > symptoms. I'll try to libtoolize fix now. I had to apt-get install
> > > > libtool before I had 'libtoolize' also.
> > >
> > > IMO this should be considered a blocking bug. We know how to resolve it
> > > but the fix needs to be merged into trunk before 2.0.0.
> >
> > Definitively.
>
> but how?
>
> Michael and myself, none of us a autotools guru, tried to understand
> and reproduce the problem. I am still not convinced there is a problem
> on the side of OpenVAS (which does not mean it is not there - I just
> don't see it).
As far as I've understood the problem, it would be sufficient to
execute the autotools chain on a clean checkout and commit the new
files that have been created/updated, at least ltmain.sh (guessed).
The problem is that you cannot just run ./configure && make to build
libraries. You'll have to run `libtoolize -f' before. That's
documented only in IRC logs and on this mailing list as far as I can
see.
Regards,
Joey
--
A mathematician is a machine for converting coffee into theorems. Paul Erdös
Please always Cc to me when replying to me on the lists.
_______________________________________________
Openvas-discuss mailing list
[email protected]
http://lists.wald.intevation.org/mailman/listinfo/openvas-discuss
