HPBEDEBUG_GetHpBeDebug

[Alex Feng]

Hi everybody,

I am trying to port my HP PA RISC to Itanium using gcc v 4.4.3.
At first I got the libu2comp.so not found message, but after downloading and installing, I am now getting this symbol not found message.
I can probably by-pass it by declaring it, somewhere, but I would like to know what it is.

Thanks.

collect2: ld terminated with signal 9 [Killed]
/usr/lib/hpux64/dld.so: Unsatisfied code symbol 'HPBEDEBUG_GetHpBeDebug' in load
module '/opt/langtools/lib/hpux64/libu2comp.so'.
*** Error exit code 1

[Dennis Handly]

>but after downloading and installing, I am now getting this symbol not found message.

You have no business downloading and installing libu2comp.so if you haven't purchased the aC++ compiler. How did you do that?

>PA RISC to Integrity using gcc v 4.4.3.

Have you removed ALL of your PA objects and archives?
What HP-UX version are you using? What linker patch do you have? Newer linkers shouldn't invoke u2comp with mismatched objects.

[Alex Feng]

I downloaded the Trial version of that compiler which came with the libu2comp.so.

HP-UX hp3006 B.11.23 U ia64 2640781999 unlimited-user license

As for the linker, it's just the default linker that came with it.

[Dennis Handly]

>I downloaded the Trial version of that compiler which came with the libu2comp.so.

If you aren't using aC++, you should remove it.

>it's just the default linker that came with it.

That is likely your secondary problem. The recommended patch is: PHSS_40537

[Alex Feng]

Installing the patch didn't help. As soon as I uninstalled the aCC Trial version it complained about the libu2comp.so not found again.

I think the reason my build is looking for it is because I am linking in an Oracle library. Anyhow, I noticed on the HP DVD that came with the the server, it comes with aCC. After installing that the, error went away and replaced with a new error.

CPL Product: B3911DB
Codeword Req.: No
Size: 321979719
Revision: C.11.23.09
Description: HP aC++ Compiler (S700)

CPL Product: B3913DB
Codeword Req.: No
Size: 321979719
Revision: C.11.23.09
Description: HP aC++ Compiler (S800)

Thanks for your help Dennis.

[Dennis Handly]

>As soon as I uninstalled the aCC Trial version it complained about the libu2comp.so not found again.

This should only happen if you have PA objects and libs in your link line. (And I thought the new linker would give a better error message.)
What does file(1) show for each?

>I think the reason my build is looking for it is because I am linking in an Oracle library.

Can you run file on that?

>it comes with aCC. CPL Product: B3911DB CPL Product: B3913DB

These versions are obsolete and not supported.

>replaced with a new error.

What's that error?

[Alex Feng]

The build didn't like the library "/usr/lib/libsec.1" saying something like invalid library.

Then, I changed "/usr/lib/libsec.1" to "usr/lib/hpux32/libsec.so.1"

and everything worked.

I'm guessing libsec.1 on Itanium is different than the libsec.1 on PA RISC.

[Alex Feng]

Using the C compiler that came with the server seems to fix the problem.

[Dennis Handly]

>The build didn't like the library "/usr/lib/libsec.1" saying something like invalid library.

Of course. Because of Aries(5), Integrity systems have both the PA and IPF shlibs.
PA is in /usr/lib/ and IPF is in /usr/lib/hpux??/.

>I changed /usr/lib/libsec.1

Why are you mentioning either? You should just link with -lsec.

>I'm guessing libsec.1 on Integrity is different than the libsec.1 on PA RISC.

If it has the same path, they should be the same.