On 16/05/2017 15:58, Adrian Klaver wrote:
> For completeness what does:
>
> ls -al /usr/lib64/libssl.so
>
> show?
>
(Trimming things down a bit to keep things a little bit more readable,
now we've got the package dependencies issue sorted. Hopefully.
Hope that's OK?)
I can see the following:
$ ls -l /usr/lib64/libssl.so
lrwxrwxrwx 1 root root 16 May 15 16:57 /usr/lib64/libssl.so ->
libssl.so.1.0.1e
Just to expand on that a bit :
$ ls -l /usr/lib64/libssl.*
lrwxrwxrwx 1 root root 16 May 15 16:57 /usr/lib64/libssl.so ->
libssl.so.1.0.1e
lrwxrwxrwx 1 root root 16 May 11 12:41 /usr/lib64/libssl.so.10 ->
libssl.so.1.0.1e
-rwxr-xr-x 1 root root 440K Sep 22 2016 /usr/lib64/libssl.so.1.0.1e
>
>>
>> Ah, sorry. A bit got truncated. Here you go:
>>
>> /bin/ld: warning: libssl.so.1.0.0, needed by
>> /db_demo/app/postgres/9.6.2-3/lib/libpq.so, may conflict with
>> libssl.so.10
>> /lib64/libldap_r-2.4.so.2: undefined reference to `ber_sockbuf_io_udp'
>> collect2: error: ld returned 1 exit status
>> make: *** [repmgrd] Error 1
> Not sure what is going on here. My usual reaction to a message like
> this when compiling is to install the --devel package for the library
> involved. In this case I believe it would be something like:
>
> openldap2-devel
OK, thank you. I'll pass that along to our UNIX team and ask for that to
be installed, see what we get ...
>
> This is just an off the top of the head suggestion, no warranty:)
What? You mean I can't get my money back? :)
Many thanks for all the help so far. It's been very, very, helpful. I'm
sure it's nearly there ...
Regards,
Martin.
--
Martin Goodson
"Have you thought up some clever plan, Doctor?"
"Yes, Jamie, I believe I have."
"What're you going to do?"
"Bung a rock at it."