<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto"><div>I always build MPICH from git by hand. MacPorts broke my toolchain such that I could not compile MPICH or MPI-free Fortran applications. I believe GCC and/or binutils stuff was improperly told to generate/work with 32bit objects. Replacing MacPorts with Homebrew solved my problems. I suppose I could have reinstalled MacPorts (since it worked fine for me for over a year before self-destructing) but an expert advised me to switch.</div><div><br></div><div>Jeff<br><br>Sent from my iPhone</div><div><br>On Jan 13, 2014, at 12:39 AM, "Eric A. Borisch" <<a href="mailto:eborisch@gmail.com">eborisch@gmail.com</a>> wrote:<br><br></div><blockquote type="cite"><div><div dir="ltr"><div>He's building with icc/ifort, so it's not being done via MacPorts. I don't think he even needs MP or Homebrew installed to build MPICH, just Intel's tools (and Xcode).</div><div><br></div>
<div><font><span style="background-color:rgba(255,255,255,0)">Building with 'make V=1' (or configuring with --disable-silent-rules) will provide more insight into what is going on. If you do have MP or Homebrew installed, you can rule out most interaction by removing their locations (/opt/local/bin, or /usr/local/bin, respectively) from PATH.</span></font></div>
<div><br></div><div>Jeff, I'm sorry to year you were unhappy with the (MP) tools. FWIW, it's been reworked to have a standardized MPICH version (with GCC's Fortan and the system's default C compiler) that is installed for use by any (macports-built) package that needs it.<span></span></div>
<div><br></div><div>Thanks,</div><div> - Eric</div><div><br></div>On Sunday, January 12, 2014, Jeff Hammond wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Might be the MacPorts garbage that bit me a while back too. If GCC fails, I suggest wiping MacPorts and installing Homebrew and the associated toolchain.<br>
<br>
Jeff<br>
<br>
Sent from my iPhone<br>
<br>
> On Jan 12, 2014, at 7:58 PM, Rajeev Thakur <<a>thakur@mcs.anl.gov</a>> wrote:<br>
><br>
> It sounds like a 32-bit, 64-bit incompatibility between some installed compilers/linker. Are you able to build with gcc?<br>
><br>
><br>
>> On Jan 10, 2014, at 3:09 PM, "Salmon, Rene" <<a>salmr0@bp.com</a>> wrote:<br>
>><br>
>><br>
>> Hi,<br>
>><br>
>> Just trying to build MPICH 3.1rc2 on a Mac. The build seems to work but fails while trying to compile the examples. This is using the intel compilers.<br>
>><br>
>> ifort,icc version 14.0.0.074<br>
>><br>
>> Here is the config line.<br>
>> ./configure CC=icc CXX=icpc F77=ifort FC=ifort --enable-fc<br>
>><br>
>><br>
>> error message.<br>
>><br>
>> make[4]: Nothing to be done for `all'.<br>
>> make[4]: Nothing to be done for `all-am'.<br>
>> Making all in .<br>
>> Making all in .<br>
>> Making all in examples<br>
>> CCLD cpi<br>
>> Undefined symbols for architecture x86_64:<br>
>> "_MPI_Bcast", referenced from:<br>
>> _main in cpi.o<br>
>> "_MPI_Comm_rank", referenced from:<br>
>> _main in cpi.o<br>
>> "_MPI_Comm_size", referenced from:<br>
>> _main in cpi.o<br>
>> "_MPI_Finalize", referenced from:<br>
>> _main in cpi.o<br>
>> "_MPI_Get_processor_name", referenced from:<br>
>> _main in cpi.o<br>
>> "_MPI_Init", referenced from:<br>
>> _main in cpi.o<br>
>> "_MPI_Reduce", referenced from:<br>
>> _main in cpi.o<br>
>> "_MPI_Wtime", referenced from:<br>
>> _main in cpi.o<br>
>> ld: symbol(s) not found for architecture x86_64<br>
>> make[2]: *** [cpi] Error 1<br>
>> make[1]: *** [all-recursive] Error 1<br>
>> make: *** [all] Error 2<br>
>><br>
>> Thank you.<br>
>><br>
>> Rene<br>
>> _______________________________________________<br>
>> discuss mailing list <a>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>
> discuss mailing list <a>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>
discuss mailing list <a>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>
</div></blockquote><blockquote type="cite"><div><span>_______________________________________________</span><br><span>discuss mailing list <a href="mailto:discuss@mpich.org">discuss@mpich.org</a></span><br><span>To manage subscription options or unsubscribe:</span><br><span><a href="https://lists.mpich.org/mailman/listinfo/discuss">https://lists.mpich.org/mailman/listinfo/discuss</a></span></div></blockquote></body></html>