libcrypto.so vs libcrypto.s1 - Nagios compile

[joseken]

I'm attempting to compile Nagrios NRPE on a 11.31 ia64 system and am having some issues including SSL. It's been traced down to the fact that the configure script is looking for libs that end in  .sl instead of .so

 elif test "`uname -s`" = "HP-UX" ; then
                                soext="sl"
                        else
                                soext="so"
                        fi
                        if test -f "$dir/libssl.$soext"; then
                                found_ssl=yes
                                break
                        fi

I'm new to HP-UX so I have no idea if the is an issue with the configure script or if I need something else that I'm not seeing. I'm hoping that someone here can help enlighten me to the nature of SSL libraries in HP-UX.

[Bill Hassell]

The script has not been updated for Integrity machines. From the HP doc about .so and .sl naming conventions:

"The standard HP naming convention (and it is a convention, not any type of enforced rule) is that native mode (ELF-32 or ELF-64 IA) shared libraries will have the suffix .so and that libraries that are intended for use with compatibility mode programs (running under ARIES) are typically suffixed with .sl, which is the same suffix as on PA-RISC hpux machines."

So it depends on how the code is compiled and linked -- native IA64 mode will use .so filenames so the script would have to include that test. If the code is being compiled as PARISC, then the .sl suffix would be used.

This is by convention - filenames can be whatever you want but with libraries, consistency is the best rule (along with updated versions of the make packages).

SSL can be problematic. HP distributes OpenSSL in a fairly standard way but there are lots of other SSL packages that do not use the usual library loactions or suffixes. You'll need to check where your SSLlibraries are located.

[joseken]

I modified the configure script to look for .so instead of .sl and I was able to compile the NRPE binary and verify SSL functionality.

Thank you for your assistance.