Building an application on a "64-bit HP-UX" environment necessary or not?

[Jaideep Krishnan]

Hi,

I have an application that is 32 as well as 64-bit compliant. It compiles/builds on Solaris using flags USE_64=0 and USE_64=1 to generate the application that runs on 32 and 64-bit Solaris platforms, respectively.

This application needs to be ported to HP-UX. Infact it has already been compiled, built, packaged and tested runtime on a 32-bit HP-UX system.

What I would want to know is, is it required that the product be compiled/built and packaged on a "64-bit HP-UX system" in order for the product to generate 64-bit application that can run on any 64-bit HP-UX system?

By the way, the command "uname -mrsvil" when run on the platform, where it has been built to generate the "32-bit" part of the application, returns the following:

HP-UX B.11.11 U 9000/800 2640277115 unlimited-user license

"getconf KERNEL_BITS" command when run on the same platform returns 64.

Please let me know the following......
Is the above platform sufficient to build and package the product so that it would run on a 64-bit HP-UX environment as well? Or else, would it have to be built on any other HP-UX environments like HP-UX11i, for example?

Thanks a lot for your help,
Jaideep.

[Ravi_8]

Hi Jaideep

32 bit appliactions will run on 64 bit HP-UX also.

If source code is in C. while compiling you may get error, Once the HP me gave an option to use with 64 bit PA-RISC ( i have forgotten actually).

since 64 bit OS also support 32 bit appliactions, the above platform should be sufficient

[Biswajit Tripathy]

32bit PS-RISC binaries will run fine when you move
them to a 64 bit machine. But it's advisable to
compile your code for 64 bit system. Check the
compiler documentation to findout the compiler
options you should use while compiling for 64bit.
Also, you might want to run thro' your source code
to make sure that it's "64 bit safe". Things to look for
would be any code that assumes the address size
to be 32 bit.

- Biswajit

[Jaideep Krishnan]

Hi Ravi and Biswajit,
Thank you so much for your prompt responses.

I would still want to know if this application can be built on the SAME hpux environment (HP-UX 11.11) with the appropriate compile options to generate 64 bit packages?

Or, does the kernel itself have to be 64-bit of the platform on which the Build & Packaging processes have to take place(For example, HP-UX 11i)?

Here is the OS on which it was built earlier to generate the 32-bit packages:

HP-UX B.11.11 U 9000/800 2640277115 unlimited-user license

getconf KERNEL_BITS -> 64

Please let me know in this regard.

Thanks & Rgds,
Jaideep

[Ravi_8]

Hi,

application can be built on the SAME hpux environment with the appropriate compile options to generate 64 bit packages

[rick jones]

Specifically, you would use +DD64 as a compiler option (HP compiler at least) and so long as you have the 64-bit compilation stuff loaded it will compile and build a 64-bit app, even on a 32-bit system.

Now, there may be wrinkles if you want to build native IPF binaries on PA-RISC or whatnot. IPF (Itanium) systems will run PA-RISC binaries, but if you can build native that is prefered.

BTW, your system that has B.11.11 in the uname _is_ an 11i system - an 11iv1 system to be precise.

[TwoProc]

Just my two cents... If I'm doing a port today of some code that would have a 5 to 8 year life cycle - I'd certainly compile 64 bit - just so that my programs would be easier to expand in the future. Heck, If I'm porting already, then an additional flag to 64 bit is just a small matter added to the heap.

But, the *biggest* reason that I'd choose 64 bit is that there is a limit to how much 32 bit "stuff" the 11i 64 bit environment can run (I think around 2.7G) until you must starting doing something called "memory windows" to manage your application in 32 bit adddressable windows w/in the 64 bit space. It's a neat workaround if you have to do it - but not having to worry about it all is MUCH better.

My vote goes to 64 bit conversion.

[Trond Haugen]

Adding to the answers you already have got I would just like to point out that as you system IS 64bits it can compile both 32 and 64 bit programs/applications.

11.11 is the same as 11i or more precise 11i v1. You will find plenty of other threads discussing the various versions of 11i.

Regards,
Trond

[Bob_Vance]

In his case, he has a 64-bit system, so certainly he can do both 32-bit build and 64-bit build.

Now, Rick says that even if you are on a 32-bit system, you can build 64-bit. My question is where do the 64-bit libraries come from to do the linking? Are they loaded and stored somewhere when you do the ANSI_C install? And then does the 64-bit flag automatically find them for the link?

tks
bv

[rick jones]

I believe they come with the compiler install - they _may_ need to be selected explicitly if the system is 32 bit, but I'm not sure of that. All the systems on which I myself have tried to build 64-bit binaries have been running 64-bit kernels...

This day and age, the only place where one could be running a 32-bit kernel would be:

1) obsolete 10.20 which cannot build 64-bit
2) 11.0 or 11.i on PA-8200 or earlier CPUs

since those are the only places where 32 bit kernels run (well, going back as far as 10.20)

IIRC it has been quite a while indeed since HP sold a PA-8200 based system (eg K570, C240) and while I'm sure they would "work" as compile engines life would really be better walking on two legs with a system from this millenium :) Particularly since 11iv2u2 (11.23pi or 11.23update2) dropped support the last of the PA-8200 systems.

Having said all that, I will confess that I was sad to see my old 735/99 wolrkstation, which I'd been keeping to have as a museum peice, get carted away when i wasn't around to protect it...

[Bob_Vance]

Thanks, Rick.

bv

[Jaideep Krishnan]

Hi, Thank you so much for all your views.

What about the LD_LIBRARY_PATH and SHLIB_PATH alternatives?

While porting this application from SOLARIS to 32-bit HP-UX, as described above, we moved all the occurances of LD_LIBRARY_PATH's
to SHLIB_PATH.

Would SHLIB_PATH work on 64-bit HP-UX system?

From HP porting guide, I received the information that -
"32-bit HP-UX supports SHLIB_PATH, while, 64-bit HP-UX supports LD_LIBRARY_PATH".

Will 64-bit HP-UX support "SHLIB_PATH" under any circumstance?

Please let me know.
Thanks & Rgds,

Jaideep

[TwoProc]

Jaideep,

I get so confused with these two - across a few different Unix variants - I find it easier to be safe and just set both of the doggone things to the same thing. I know, that's lazy, and at some point in the past I actually knew when to call which one. Then old age and senility kicked in, and I just set 'em both. Taheckwifet. :-)