/usr/lib/lib*.sl vs. /usr/lib/lib*.1 vs . /usr/lib/lib*.2

[Hannu R]

Hi,

I have a problem with our development machine compared to our customers "production" machines, in our machine most of /usr/lib/lib*.sl (libc, libcl,libm,..) libraries/links points to .1 version of libs, and at the customer they point to .2 versions, and it seems to cause problems (when running apps in cust. host, we'll get "invalid version for shared library xxxx") mostly with oracles client library. I tried different library orders when linking and I also linked .2 versions to our progs. (and tried all sort of things) but I am not satisfied.

Question: why those *.sl links point to .1 versions in our system and to .2 versions at the customer, does some patch level affect that, both machines are UX11.0

What do I have to do to get those links to point to .2 versions (I think I just can't recreate them) ?

Thanks,
Hannu

[harry d brown jr]

Hannu,

do a man on "libcadmin"

live free or die
harry

[Mark Vollmers]

Hannu-

do the two machines run different versions of Oracle? or was one installed twice or overwrote an old version? it almost seems like there is something like that going on. It sounds more like a software issue rather than a hp version or patch issue to me.

Mark

[harry d brown jr]

Hannu,

Are both machines IDENTICAL, meaning model, CPU speed, etc?

live free or die
harry

[Santosh Nair_1]

If I'm not mistaken, all the .1 files in /usr/lib should be HPUX 10.20 libraries (which are included in HPUX 11.0 for backward compatibility). The .2 files are for HPUX 11.0. So on HPUX 11.0 systems, all the .sl files should point to the .2 files.

-Santosh

[Charles Slivkoff]

*.sl is used when the application is being linked. The *.sl file (reference by the sym-link) is opened and its embedded name is stored in the executable.

At run time, the loader will attempt to load the embedded name. This allows app built on 10.20 linked to libc.1 to run on 11.x, as libc.1 is still provided.

"chatr" against a library will display its embedded name. "chatr" against an executable will list the libraries it will attempt to load.