Migrating to Solaris 64-bit: Checklist for Conversion

Print-friendly Version

Assuming you need to convert your code to 64-bit, the following checklist may be helpful:

• Read this list with an emphasis on converting applications to LP64.
• Review all data structures and interfaces to verify that these are still valid in the 64-bit environment. Include <sys/types.h> (or at minimum, <sys/isa_defs.h>) in your code to pull in the _ILP32 or _LP64 definitions as well as many basic derived types.
• Include <sys/types.h> (or at minimum, <sys/isa_defs.h>) in your code to pull in the _ILP32 or _LP64 definitions as well as many basic derived types.
• Move function prototypes and external declarations with non-local scope to headers and include these headers in your code.
• Run lint(1B) using the -errchk=longptr64 and  -D__sparcv9 flags and review each warning individually, being aware that not all warnings require a change to the code. Depending on the resulting changes, you might also want to run lint(1B) again, both in 32-bit and 64-bit modes.
• Compile code as both 32-bit and 64-bit, unless the application is being provided only as 64-bit.
• Test the application by executing the 32-bit version on the 32-bit operating system, and the 64-bit version on the 64-bit operating system. You could include testing the 32-bit version on the 64-bit operating system, but this is not required.