<meta http-equiv="Content-Type" content="text/html; charset=utf-8"><div dir="ltr">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. </div><div class="gmail_extra"><br clear="all"><div><div class="gmail_signature"><div dir="ltr">--Junchao Zhang</div></div></div>
<br><div class="gmail_quote">On Fri, Apr 10, 2015 at 1:19 PM, Lou Picciano <span dir="ltr"><<a href="mailto:LouPicciano@comcast.net" target="_blank">LouPicciano@comcast.net</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style="word-wrap:break-word">Thank You, Junchao,<br><br>Spot on! (Duh! Dumb error)<br><br>Am now getting successful(?) compiles to completion, but I see many, many repetitions of messages like this - for a series of .lo objects:<div><br></div><div>Anything to be concerned with?<br><br><blockquote style="margin:0 0 0 40px;border:none;padding:0px"></blockquote><font face="Courier"> CC src/mpid/common/thread/lib_libmpi_la-mpid_thread.lo<br></font><blockquote style="margin:0 0 0 40px;border:none;padding:0px"></blockquote><font face="Courier">"/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<br></font><blockquote style="margin:0 0 0 40px;border:none;padding:0px"></blockquote><font face="Courier">"/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<br></font><blockquote style="margin:0 0 0 40px;border:none;padding:0px"></blockquote><font face="Courier">"/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<br></font><blockquote style="margin:0 0 0 40px;border:none;padding:0px"></blockquote><font face="Courier">"/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<br></font><blockquote style="margin:0 0 0 40px;border:none;padding:0px"></blockquote><font face="Courier">"/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<br></font><blockquote style="margin:0 0 0 40px;border:none;padding:0px"></blockquote><font face="Courier">"/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<br></font><blockquote style="margin:0 0 0 40px;border:none;padding:0px"></blockquote><font face="Courier">"/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<br></font><blockquote style="margin:0 0 0 40px;border:none;padding:0px"></blockquote><font face="Courier">"/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<br></font><blockquote style="margin:0 0 0 40px;border:none;padding:0px"></blockquote><font face="Courier">"/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<br></font><blockquote style="margin:0 0 0 40px;border:none;padding:0px"></blockquote><font face="Courier">"src/mpid/ch3/channels/nemesis/include/mpid_nem_datatypes.h", line 156: warning: syntax error: empty member declaration<br>"src/mpid/ch3/channels/nemesis/include/mpid_nem_datatypes.h", line 161: warning: syntax error: </font><div><div class="h5"><br><br><div><br></div><div>On Apr 9, 2015, at 6:25 PM, Junchao Zhang <<a href="mailto:jczhang@mcs.anl.gov" target="_blank">jczhang@mcs.anl.gov</a>> wrote:<br><br><blockquote type="cite">Lou,<br> 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=...<br><br><br>--Junchao Zhang<br><br>On Thu, Apr 9, 2015 at 9:12 AM, Junchao Zhang <<a href="mailto:jczhang@mcs.anl.gov" target="_blank">jczhang@mcs.anl.gov</a>> wrote:<br>I happened to build MPICH with SolarisStudio12.4 for Linux a couple of days ago.<br>Could you send config.log of your build?<br><br>--Junchao Zhang<br><br>On Wed, Apr 8, 2015 at 10:51 PM, Lou Cetinich <<a href="mailto:loucetinich@gmail.com" target="_blank">loucetinich@gmail.com</a>> wrote:<br>I only need Fortran. <br><br>(In fact, apart from exhaustive testing, and the endpoint target of a production build), I’d otherwise be happy to disable everything else… (!)<br><br>Lou<br><br><br>On Apr 8, 2015, at 11:47 PM, Thakur, Rajeev <<a href="mailto:thakur@mcs.anl.gov" target="_blank">thakur@mcs.anl.gov</a>> wrote:<br><br><blockquote type="cite">If you don't need to use Fortran, you can configure with --disable-fortran.<br><br>Rajeev<br><br>On Apr 8, 2015, at 10:36 PM, Lou Picciano <<a href="mailto:loupicciano@comcast.net" target="_blank">loupicciano@comcast.net</a>> wrote:<br><br><blockquote type="cite">Attempting to configure mpich-3.2b1 for the SolarisStudio12.4 suite...<br><br>Issues around complex.h (Yes, I'll have to look for prerequisites)<br><br>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?<br><br>CROSS_F77_SIZEOF_INTEGER seems to be ignored; I've tried all of 1,2,4,8...<br><br>Many thanks!<br><br>checking complex.h presence... yes<br>configure: WARNING: complex.h: present but cannot be compiled<br>configure: WARNING: complex.h: check for missing prerequisite headers?<br>configure: WARNING: complex.h: see the Autoconf documentation<br>configure: WARNING: complex.h: section "Present But Cannot Be Compiled"<br>configure: WARNING: complex.h: proceeding with the compiler's result<br>configure: WARNING: ## -------------------------------- ##<br>configure: WARNING: ## Report this to <a href="mailto:discuss@mpich.org" target="_blank">discuss@mpich.org</a> ##<br>configure: WARNING: ## -------------------------------- ##<br>checking for complex.h... no<br>checking size of _Bool... 0<br>checking size of float _Complex... 0<br>checking size of double _Complex... 0<br>checking size of long double _Complex... 0<br>checking for _Bool... no<br>checking for float _Complex... no<br>checking for double _Complex... no<br>checking for long double _Complex... no<br>checking for size of Fortran type integer... 0<br>checking for size of Fortran type real... 0<br>checking for size of Fortran type double precision... 0<br>checking whether integer*1 is supported... yes<br>checking whether integer*2 is supported... yes<br>checking whether integer*4 is supported... yes<br>checking whether integer*8 is supported... yes<br>checking whether integer*16 is supported... no<br>checking whether real*4 is supported... yes<br>checking whether real*8 is supported... yes<br>checking whether real*16 is supported... yes<br>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<br>_______________________________________________<br>discuss mailing list <a href="mailto:discuss@mpich.org" target="_blank">discuss@mpich.org</a><br>To manage subscription options or unsubscribe:<br><a href="https://lists.mpich.org/mailman/listinfo/discuss" target="_blank">https://lists.mpich.org/mailman/listinfo/discuss</a><br></blockquote><br>_______________________________________________<br>discuss mailing list <a href="mailto:discuss@mpich.org" target="_blank">discuss@mpich.org</a><br>To manage subscription options or unsubscribe:<br><a href="https://lists.mpich.org/mailman/listinfo/discuss" target="_blank">https://lists.mpich.org/mailman/listinfo/discuss</a><br></blockquote><br><br>_______________________________________________<br>discuss mailing list <a href="mailto:discuss@mpich.org" target="_blank">discuss@mpich.org</a><br>To manage subscription options or unsubscribe:<br><a href="https://lists.mpich.org/mailman/listinfo/discuss" target="_blank">https://lists.mpich.org/mailman/listinfo/discuss</a><br><br><br>_______________________________________________<br>discuss mailing list <a href="mailto:discuss@mpich.org" target="_blank">discuss@mpich.org</a><br>To manage subscription options or unsubscribe:<br><a href="https://lists.mpich.org/mailman/listinfo/discuss" target="_blank">https://lists.mpich.org/mailman/listinfo/discuss</a><br></blockquote><br></div></div></div></div></div><br>_______________________________________________<br>
discuss mailing list <a href="mailto:discuss@mpich.org">discuss@mpich.org</a><br>
To manage subscription options or unsubscribe:<br>
<a href="https://lists.mpich.org/mailman/listinfo/discuss" target="_blank">https://lists.mpich.org/mailman/listinfo/discuss</a><br></blockquote></div><br></div>