Library information needed on HP-UX 11.0

[Insu Kim]

I plan to upgrade a system with HP-UX 10.20 to one with HP-UX 11.0.
Could you please tell me where libraries are on HP-UX 11.0 as opposed to HP-UX 10.20 and any options needed to compile C-based applications on either HP-UX 11.0 32bit or HP-UX 11.0 64 bit ?

Optionally,
Any decision is not made at this time whether we go to HP-UX 11.0 32bit or HP-UX 11.0 64bit.
Any suggestions would be apperciated.

[Steven Sim Kok Leong]

Hi,

You can find all the information you need here:

http://www.docs.hp.com/hpux/os/11.0/index.html

Specifically, the Release notes highlights the architecture and compiler differences, found at sub-link:

http://www.docs.hp.com/hpux/onlinedocs/B3782-90716/B3782-90716.html

Major features and differences in HP-UX 11.00 can be found at sub-link:

http://www.docs.hp.com/hpux/onlinedocs/B3782-90716/00/00/13-con.html

Advantages of using 64-bit HP-UX 11.00 over 32-bit HP-UX 11.00 can be found at sub-link:

http://www.docs.hp.com/hpux/onlinedocs/B3782-90716/00/00/15-con.html

Hope this helps. Regards.

Steven Sim Kok Leong
Brainbench MVP for Unix Admin
http://www.brainbench.com

[Bill Hassell]

Part of the compatibility between 10.20 and future releases allows programs to port seamlessly to the next generation. Assuming no liberties have been taken within the programs to use non-portable features, there should be no problems.

In compiling programs on 11.0 in a 64-bit environment, be sure to use the +DAportable option to ensure backward compatility. Leaving out this option in a 64-bit OS will create a 64-bit data model program. Now in a stand-alone program, this seldom causes any issues but when the data is shared or imported from other sources, care must be taken to handle to the larger pointer sizes, etc.

Check out http://software.hp.com/STK/

Also, print out the 11.0 Release Notes found in /usr/share/doc which will detail many of the differences.

[A. Clay Stephenson]

In addition to the other suggestions, one other thing to be aware of mixed 32-bit and 64-bit code accessing shared memory segments. A 64-bit process might create a shared memory segment that a 32-bit application might need to access. This is permitted but you have to use the correct flags when the shared memory segment is created. Man shmget and shmop for those details.

If you use the +DAportable option your code will execute in both the 32-bit and 64-bit worlds. Bear in mind, that in general, 64-bit code will not execute any faster but does remove many resource limits. 32-bit code will execute on all platforms but the converse is not true.