I think the warnings reported by suncc are harmless. It is probably because the inline asm statements use GNU syntax, and there is a ";;" in a struct after macro expansion. --Junchao Zhang On Fri, Apr 10, 2015 at 1:19 PM, Lou Picciano <[email protected]> wrote:

Thank You, Junchao,

Spot on! (Duh! Dumb error)

Am now getting successful(?) compiles to completion, but I see many, many repetitions of messages like this - for a series of .lo objects:

Anything to be concerned with?

CC src/mpid/common/thread/lib_libmpi_la-mpid_thread.lo

"/datapool/home/drlou/Downloads/mpich-3.2b1/src/openpa/src/primitives/opa_gcc_intel_32_64_ops.h", line 95: warning: parameter in inline asm statement unused: %2

"/datapool/home/drlou/Downloads/mpich-3.2b1/src/openpa/src/primitives/opa_gcc_intel_32_64_ops.h", line 103: warning: parameter in inline asm statement unused: %1

"/datapool/home/drlou/Downloads/mpich-3.2b1/src/openpa/src/primitives/opa_gcc_intel_32_64_ops.h", line 111: warning: parameter in inline asm statement unused: %1

"/datapool/home/drlou/Downloads/mpich-3.2b1/src/openpa/src/primitives/opa_gcc_intel_32_64_ops.h", line 121: warning: parameter in inline asm statement unused: %2

"/datapool/home/drlou/Downloads/mpich-3.2b1/src/openpa/src/primitives/opa_gcc_intel_32_64_ops.h", line 129: warning: parameter in inline asm statement unused: %3

"/datapool/home/drlou/Downloads/mpich-3.2b1/src/openpa/src/primitives/opa_gcc_intel_32_64_ops.h", line 142: warning: parameter in inline asm statement unused: %1

"/datapool/home/drlou/Downloads/mpich-3.2b1/src/openpa/src/primitives/opa_gcc_intel_32_64_ops.h", line 151: warning: parameter in inline asm statement unused: %1

"/datapool/home/drlou/Downloads/mpich-3.2b1/src/openpa/src/primitives/opa_gcc_intel_32_64_ops.h", line 159: warning: parameter in inline asm statement unused: %3

"/datapool/home/drlou/Downloads/mpich-3.2b1/src/openpa/src/primitives/opa_gcc_intel_32_64_ops.h", line 167: warning: parameter in inline asm statement unused: %3

"src/mpid/ch3/channels/nemesis/include/mpid_nem_datatypes.h", line 156: warning: syntax error: empty member declaration "src/mpid/ch3/channels/nemesis/include/mpid_nem_datatypes.h", line 161: warning: syntax error:

On Apr 9, 2015, at 6:25 PM, Junchao Zhang <[email protected]> wrote:

Lou, I looked at your config.log. You passed CC=/opt/solarisstudio12.4/bin/CC to configure, which is wrong. You should use CC=/opt/solarisstudio12.4/bin/cc. If you want C++, just use CXX=...

--Junchao Zhang

On Thu, Apr 9, 2015 at 9:12 AM, Junchao Zhang <[email protected]> wrote: I happened to build MPICH with SolarisStudio12.4 for Linux a couple of days ago. Could you send config.log of your build?

--Junchao Zhang

On Wed, Apr 8, 2015 at 10:51 PM, Lou Cetinich <[email protected]

...

wrote: I only need Fortran.

(In fact, apart from exhaustive testing, and the endpoint target of a production build), I’d otherwise be happy to disable everything else… (!)

Lou

On Apr 8, 2015, at 11:47 PM, Thakur, Rajeev <[email protected]> wrote:

If you don't need to use Fortran, you can configure with --disable-fortran.

Rajeev

On Apr 8, 2015, at 10:36 PM, Lou Picciano <[email protected]> wrote:

Attempting to configure mpich-3.2b1 for the SolarisStudio12.4 suite...

Issues around complex.h (Yes, I'll have to look for prerequisites)

and the message about FORTRAN integer length - which seems to have been dealt with a couple of years ago, and only in the ifort context?

CROSS_F77_SIZEOF_INTEGER seems to be ignored; I've tried all of 1,2,4,8...

Many thanks!

checking complex.h presence... yes configure: WARNING: complex.h: present but cannot be compiled configure: WARNING: complex.h: check for missing prerequisite headers? configure: WARNING: complex.h: see the Autoconf documentation configure: WARNING: complex.h: section "Present But Cannot Be Compiled" configure: WARNING: complex.h: proceeding with the compiler's result configure: WARNING: ## -------------------------------- ## configure: WARNING: ## Report this to [email protected] ## configure: WARNING: ## -------------------------------- ## checking for complex.h... no checking size of _Bool... 0 checking size of float _Complex... 0 checking size of double _Complex... 0 checking size of long double _Complex... 0 checking for _Bool... no checking for float _Complex... no checking for double _Complex... no checking for long double _Complex... no checking for size of Fortran type integer... 0 checking for size of Fortran type real... 0 checking for size of Fortran type double precision... 0 checking whether integer*1 is supported... yes checking whether integer*2 is supported... yes checking whether integer*4 is supported... yes checking whether integer*8 is supported... yes checking whether integer*16 is supported... no checking whether real*4 is supported... yes checking whether real*8 is supported... yes checking whether real*16 is supported... yes configure: error: Unable to configure with Fortran support because configure could not determine the size of a Fortran INTEGER. Consider setting CROSS_F77_SIZEOF_INTEGER to the length in bytes of a Fortran INTEGER _______________________________________________ discuss mailing list [email protected] To manage subscription options or unsubscribe: https://lists.mpich.org/mailman/listinfo/discuss

_______________________________________________ discuss mailing list [email protected] To manage subscription options or unsubscribe: https://lists.mpich.org/mailman/listinfo/discuss

_______________________________________________ discuss mailing list [email protected] To manage subscription options or unsubscribe: https://lists.mpich.org/mailman/listinfo/discuss

_______________________________________________ discuss mailing list [email protected] To manage subscription options or unsubscribe: https://lists.mpich.org/mailman/listinfo/discuss

_______________________________________________ discuss mailing list [email protected] To manage subscription options or unsubscribe: https://lists.mpich.org/mailman/listinfo/discuss

_______________________________________________ discuss mailing list [email protected] To manage subscription options or unsubscribe: https://lists.mpich.org/mailman/listinfo/discuss