Re: ibopenarc.so.0: cannot open shared object file

[Jonathan Sélea <jonathan@xxxxxxxx>]

libopenarc.so.0 and libopenarc.so is in the catalogue that you mentioned
(usr(local/lib)

The exact commands I used to compile it is stated in my first email :)


root@list:/usr/local/sbin# ldd openarc
        linux-vdso.so.1 =>  (0x00007fffc13d1000)
        libopenarc.so.0 => not found
        libmilter.so.1.0.1 =>
/usr/lib/x86_64-linux-gnu/libmilter.so.1.0.1 (0x00007fa948990000)
        libssl.so.1.0.0 => /lib/x86_64-linux-gnu/libssl.so.1.0.0
(0x00007fa948727000)
        libcrypto.so.1.0.0 => /lib/x86_64-linux-gnu/libcrypto.so.1.0.0
(0x00007fa9482e3000)
        libresolv.so.2 => /lib/x86_64-linux-gnu/libresolv.so.2
(0x00007fa9480c8000)
        libbsd.so.0 => /lib/x86_64-linux-gnu/libbsd.so.0
(0x00007fa947eb3000)
        libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0
(0x00007fa947c96000)
        libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007fa9478cc000)
        libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x00007fa9476c8000)
        /lib64/ld-linux-x86-64.so.2 (0x00007fa948ba1000)

If I am not wrong, openarc expects that libopenarc.so.0 is in the same
catalogue as the openarc binary?

My system in an Ubuntu 16.04.3, I have the same problem on Debian 8 and
9 so it must be something that I do wrong.
What is the process you follow when you deploy it? From Download to
adding it as milter if I may ask

/ Jonathan


On 2018-01-14 14:14, Juri Haberland wrote:
> On 14/01/18 13:43, Jonathan Sélea wrote:
>> The steps I posted proceeded without any errors at all.
>>
>> |libtool libbsd-devel openssl-devel libopendkim-devel.x86_64 \
>> sendmail-milter.x86_64 sendmail-devel.x86_64 Thoose packages is
>> installed / Jonathan |
> Well,
>
> next I would check if the lib was actually build, installed and included in
> the ld.so.cache.
> Did you use --prefix for your configure command? If not, the library should
> be in /usr/local/lib. Is it there?
> Check with "ldd -v /path/to/openarc-binary" where it is expected.
> If it is there, is this path searched by ldconfig? Look at /etc/ld.so.conf.
>
> On my Debian/Ubuntu systems it just works...
>
>
>   Juri
>

Attachment: smime.p7s
Description: S/MIME Cryptographic Signature