On Donnerstag, 6. November 2008, Toan Nguyen wrote:
>       My mistake. I should've proofread it first. Yes, I meant the other way. 
> Below is an example of what I mean. I'm compiling libnasl right now on 
> another machine and it's complaining about gpgme not being installed:
> configure: error: ""
> ""
> "*** gpgme is not installed ! You need to install it before you"
> "compile openvas-libnasl."
> 
> Let's see if there is a flag to specify where I installed gpgme. 
> ./configure --help | grep -i gpg
> 
> And no results are returned. Apparently, libnasl can only detect gpgme in its 
> default installation path. It's not really a big problem for me but it's just 
> convenient if the configure script allows you to input paths of where you 
> installed the dependencies. 

the "usual" way is that "gpgme-config" should be in the path.





        Sure, that's easy enough. After manually putting in gpgme-config in the 
path, now I can't declare where openvas-libraries are. I even tried using 
--libdir and exporting LD_LIBRARY_PATH to point to where openvas-libraries are:

./configure --prefix=/opt/openvas/apps/libnasl 
--libdir=/opt/openvas/apps/libraries


And, libnasl still doesn't see it: 

configure: error: ""
""
"*** openvas-libraries is not installed ! You need to install it before you"
"compile openvas-libnasl."




-Toan



> UNSUCCESSFUL: 
> 
> FEED=rsync://rsync.openvas.org:/nvt-feed
> 
> SUCCESSFUL:
> 
> [EMAIL PROTECTED]::nvt-feed

I've now added a note to the sync script about this. Thanks.

Best

        Jan


-- 
Dr. Jan-Oliver Wagner                        Intevation GmbH, Osnabrück
Amtsgericht Osnabrück, HR B 18998             http://www.intevation.de/
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
_______________________________________________
Openvas-discuss mailing list
[email protected]
http://lists.wald.intevation.org/mailman/listinfo/openvas-discuss

Reply via email to