Itainium - RISC HPUX 11i v1 C Code question

[James M. Dunn]

/opt/binaryscan/binaryscan -o text /tmp/callcti.sl
/opt/binaryscan/.binaryscan: Cannot open /usr/lib/libCTI.sl (No such file or directory)
*****************************************
*
* binaryScan
* Summary Report
*
*****************************************

Date: Thu May 22 11:22:58 2008
OS Version: ush12, HP-UX B.11.11 U, 9000/800
Scanner Version: binaryScan V3.0
Database Used: pa_ipf.db
Shared Library Autoscan: YES

Reported Dispositions:
Migration Environment
Not Documented
No Information
Non-critical Change
Critical Change
Not Going Forward

*****************************************
*
* Scan Summary :
*
*****************************************


Count of dispositions for /tmp/callcti.sl:

0 -- Migration Environment
0 -- Not Documented
0 -- No Information
0 -- Non-critical Change
0 -- Critical Change
0 -- Not Going Forward


I take that this output means its portable...

[Duncan Edmonstone]

Afraid I know where the tool is, but not how to interperet its output.

I note that the binary you are checking is a shared lib... do you call that shared lib from other code of yours that you intend to port to Itanium?

The reason I ask is that what ARIES will *not* allow you to do is call a PA-RISC shared library from a IA64 executable. The executable would have to stay on PA-RISC as well.

HTH

Duncan

[Dennis Handly]

For more info about Aries see:
http://www.hp.com/go/aries

>Duncan: what ARIES will *not* allow you to do is call a PA-RISC shared library from a IA64 executable. The executable would have to stay on PA-RISC as well.

What Duncan means is that the whole application would have to be left as-is and the whole thing copied to your new Integrity box.