> On May 23, 2017, at 9:17 AM, Reindl Harald <[email protected]> wrote:
> 
> 
> 
> Am 23.05.2017 um 16:10 schrieb Brandon Perry:
>>> On May 23, 2017, at 9:04 AM, Dehm, Jochen <[email protected]> wrote:
>>> 
>>> I want to use a 2nd server  to control my OpenVAS server via omp.
>>> 
>>> After building openvas-libraries and openvas-cli from the source, I get the 
>>> following error:
>>> 
>>> root@sv-idoit ~ # omp
>>> omp: error while loading shared libraries: libopenvas_omp.so.8: cannot open 
>>> shared object file: No such file or directory
>>> 
>>> root@sv-idoit ~ # which omp
>>> /usr/local/bin/omp
>>> 
>>> The file is however available:
>>> 
>>> root@sv-idoit ~/OpenVAS/openvas-cli-1.4.5/build # locate libopenvas_omp.so.8
>>> /root/OpenVAS/openvas-libraries-8.0.8/build/omp/libopenvas_omp.so.8
>>> /root/OpenVAS/openvas-libraries-8.0.8/build/omp/libopenvas_omp.so.8.0.8
>>> /usr/local/lib/libopenvas_omp.so.8
>>> /usr/local/lib/libopenvas_omp.so.8.0.8
>> Either set your —prefix=/usr when configuring (before compiling) so that 
>> make install installs to /usr instead of /usr/local.
> 
> bad idea when you spit random stuff without proper packaging around
> 
>> Or, for immediate gratification.
>> export PATH=$PATH:/usr/local
>> omp —help
> 
> nonsense - libraries has *nothing* to do with PATH
> 
> echo "/usr/local/lib/" > /etc/ld.so.conf.d/usr-local-lib.conf
> chmod 0644 /etc/ld.so.conf.d/usr-local-lib.conf
> ldconfig

Sorry, you’re right. I meant LD_LIBRARY_PATH. Unfortunately the coffee is still 
brewing.

> 
> _______________________________________________
> Openvas-discuss mailing list
> [email protected] 
> <mailto:[email protected]>
> https://lists.wald.intevation.org/cgi-bin/mailman/listinfo/openvas-discuss 
> <https://lists.wald.intevation.org/cgi-bin/mailman/listinfo/openvas-discuss>

Attachment: signature.asc
Description: Message signed with OpenPGP

_______________________________________________
Openvas-discuss mailing list
[email protected]
https://lists.wald.intevation.org/cgi-bin/mailman/listinfo/openvas-discuss

Reply via email to