Linking problem during 11V2 upgrade

[sathis kumar]

Hello,

We are currently working on migrating our applications from HP-UX 11i to HP-UX 11V2. We are facing some issues during our linking process. The error message we get is "ld: Mismatched ABI (not an ELF file) for -lapi".
We copied the shared library "libapi.sl" from HP-UX 11i. Linking is working fine when we do it on HP-UX 11i box. But we are getting the error on HP-UX 11V2 box. Could you please confirm whether we can directly copy the shared library file from 11i to 11V2 and use ?

Thanks in advance for your help.

[Dennis Handly · Accepted solution]

>Could you please confirm whether we can directly copy the shared library file from 11i to 11V2 and use?

You can copy the lib from PA to IPF but all you can do is also copy the executable and then run. You can't do linking/development of PA applications.

[sathis kumar]

We create our own shared library by linking
"libapi.sl". The process we followed:

- Copied libapi.sl from 11i to 11V2.
- Tried creating our own shared library by linking "libapi.sl" (that we copied from 11i)
- Linking failed with error "ld: Mismatched ABI (not an ELF file) for -lapi"

From your reply, we understand that we can not use the shared library which was built in 11i on 11V2? Kindly correct me if I am wrong.

Thanks in advance, Sathis Kumar

[Dennis Handly]

>we understand that we can not use the shared library which was built in 11i on 11v2? Kindly correct me if I am wrong.

(You need to be more specific. 11i v2 supports both PA and IPF. So you need to mention you are on Integrity.)

Yes, and no.
You can copy the whole application over to IPF and just run it under Aries.

But you can't mix and match PA and IPF objects so if you need to change anything or want it to run at native speeds, you have to recompile and link the whole application, including any third party libs.