https://community.hpe.com/t5/operating-system-hp-ux/c-compiler-for-64-bit-hp11-11-superdome/m-p/2585470#M725540 Hi Paul:<BR /><BR />I would set the +DA2.0W compiler flag. That should set the proper defines for you. In any event, the PA-8600 processors will definitely <BR />understand PA_RISC_2 codesets.<BR /><BR />Normally, if you are compiling on the target machines, the underlying target architecture is determing by the compiler automatically. Of course, if you are compiling on another machine to run on the Superdome, then for optimum execution set +DA2.0W.<BR /><BR />Regards, Clay Wed, 26 Sep 2001 17:23:40 GMT A. Clay Stephenson 2001-09-26T17:23:40Z https://community.hpe.com/t5/operating-system-hp-ux/c-compiler-for-64-bit-hp11-11-superdome/m-p/2585469#M725539 We are migrating C code from 10.20 to 11.11 which is running on superdome. In the C code is referring va_list wihich is in the /usr/include/stdio.h. I don't know which parameters I should DEFINE in the makefile for Superdome, so C pre-process will recongize va_list, i.e., __hp9000s800, _PA_RISC1_0, during the compiling. Could I find the parameters/configuration from a file or command? Wed, 26 Sep 2001 17:02:06 GMT https://community.hpe.com/t5/operating-system-hp-ux/c-compiler-for-64-bit-hp11-11-superdome/m-p/2585469#M725539 PAUL CHEN_2 2001-09-26T17:02:06Z https://community.hpe.com/t5/operating-system-hp-ux/c-compiler-for-64-bit-hp11-11-superdome/m-p/2585470#M725540 Hi Paul:<BR /><BR />I would set the +DA2.0W compiler flag. That should set the proper defines for you. In any event, the PA-8600 processors will definitely <BR />understand PA_RISC_2 codesets.<BR /><BR />Normally, if you are compiling on the target machines, the underlying target architecture is determing by the compiler automatically. Of course, if you are compiling on another machine to run on the Superdome, then for optimum execution set +DA2.0W.<BR /><BR />Regards, Clay Wed, 26 Sep 2001 17:23:40 GMT https://community.hpe.com/t5/operating-system-hp-ux/c-compiler-for-64-bit-hp11-11-superdome/m-p/2585470#M725540 A. Clay Stephenson 2001-09-26T17:23:40Z https://community.hpe.com/t5/operating-system-hp-ux/c-compiler-for-64-bit-hp11-11-superdome/m-p/2585471#M725541 A Clay, It works. But I got the following errors:"/usr/ccs/bin/ld: (Warning) At least one PA 2.0 object file (crp_po.o) was detect<BR />ed. The linked output may not run on a PA 1.x system." It's weird I used /usr/bin/cc but the message saying I used "/usr/ccs/bin/ld" Wed, 26 Sep 2001 20:27:20 GMT https://community.hpe.com/t5/operating-system-hp-ux/c-compiler-for-64-bit-hp11-11-superdome/m-p/2585471#M725541 PAUL CHEN_2 2001-09-26T20:27:20Z https://community.hpe.com/t5/operating-system-hp-ux/c-compiler-for-64-bit-hp11-11-superdome/m-p/2585472#M725542 Hi Paul:<BR /><BR />That is perfectly normal. The warning just means that this will only run on PA-RISC2 processors (PA-8xxx and above). If you want to compile for a broader set of target environments, change to +DAportable. You will lose some efficiency, but in reality, the vast majority of applications that are written for UNIX are not CPU bound but rather are i/o bound.<BR /><BR />If you just want to suppress the warnings,<BR />you can set LDOPTS=+vnocompatwarnings and export this variable .<BR /><BR />Man ld for details.<BR /><BR /><BR />Regards, Clay<BR /> Wed, 26 Sep 2001 20:48:22 GMT https://community.hpe.com/t5/operating-system-hp-ux/c-compiler-for-64-bit-hp11-11-superdome/m-p/2585472#M725542 A. Clay Stephenson 2001-09-26T20:48:22Z