[Thursday 06 November 2008 - 14:06:42] "Jan-Oliver Wagner" 
<[EMAIL PROTECTED]>:
> > 1.  The INSTALL_README file in openvas-libraries-1.0.2 doesn't
> > indicate which version of gnutls it needs. I had 1.0.20 installed along
> > with the development files and I still couldn't compile the libraries.
> > It was gnutls 2.x that solved the issue. Pointing this out would have
> > been a great help.
>
> Michael, can you add this hint to INSTALL_README for both, trunk and 1.0
> branch?

Done and done. Toan, thanks for spotting this.

> > 2.  If you compiled all the openvas components to the non default
> > path (ie. ./configure -prefix=/whatever/path) there is no flag to
> > specify where you install the dependences for the other subsequent
> > components. Example, if I installed libnasl in /opt/openvas-libnasl,
> > there is no flag in the configure script of the openvas-libraries to
> > point where I installed libnasl. You would have to hack the configure
> > script and change the hard-coded paths. Modifying the configure script
> > to look for non-default installation paths of its dependences would be a
> > great addition.
>
> Not sure I understand the problem: openvas-libraries should not need to
> know anything about openvas-libnasl. It's only vice versa.

I think Toans point is that you could theoretically configure the components 
with different prefixes, say -libraries with /opt/openvas-libraries 
and -libnasl with /opt/openvas-libnasl. I am not quite sure as to why one 
would want this, but I can imagine this might cause issues, especially if the 
necessary environment variables are not set. Is it that what you mean, Toan?

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
_______________________________________________
Openvas-discuss mailing list
[email protected]
http://lists.wald.intevation.org/mailman/listinfo/openvas-discuss

Reply via email to