<div dir="ltr">For what it's worth, I have actually used get_command_argument in my own code and just now confirmed that it works just fine with Intel 16 in a small test program.  It would be helpful to disambiguate that from all the shared library discussion.<div><br></div><div>The other solution is to use ISO C11* as God intended and stop mucking around with all these flowery languages.</div><div><br></div><div>Jeff<br><div class="gmail_extra"><br></div><div class="gmail_extra">* It is true that no compiler yet supports C11 threads, but that is because C compiler developers know better than to troll the PETSc team with programming atrocities like threads.</div><div class="gmail_extra"><br><div class="gmail_quote">On Tue, Sep 22, 2015 at 9:16 PM, Satish Balay <span dir="ltr"><<a href="mailto:balay@mcs.anl.gov" target="_blank">balay@mcs.anl.gov</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">On Tue, 22 Sep 2015, Blaise A Bourdin wrote:<br>
<br>
> With the later configuration, it looks like what matters is the order in which  -lmpifort and -lifcore are listed:<br>
> This one works:<br>
> mpif90 -Wl,-multiply_defined,suppress -Wl,-multiply_defined -Wl,suppress -Wl,-commons,use_dylibs -Wl,-search_paths_first   -g -O0  -I/opt/HPC/petsc-dev/include/petsc/finclude -o ex5f90 ex5f90.o -Wl,-rpath,/opt/HPC/petsc-dev/Darwin-intel16.0-g/lib -L/opt/HPC/petsc-dev/Darwin-intel16.0-g/lib  -lpetsc -Wl,-rpath,/opt/intel-16.0/compilers_and_libraries_2016.0.083/mac/compiler/lib -L/opt/intel-16.0/compilers_and_libraries_2016.0.083/mac/compiler/lib -Wl,-rpath,/opt/intel-16.0/compilers_and_libraries_2016.0.083/mac/mkl/lib -lifcore -lmpifort<br>
><br>
> This one does not:<br>
> mpif90 -Wl,-multiply_defined,suppress -Wl,-multiply_defined -Wl,suppress -Wl,-commons,use_dylibs -Wl,-search_paths_first   -g -O0  -I/opt/HPC/petsc-dev/include/petsc/finclude -o ex5f90 ex5f90.o -Wl,-rpath,/opt/HPC/petsc-dev/Darwin-intel16.0-g/lib -L/opt/HPC/petsc-dev/Darwin-intel16.0-g/lib  -lpetsc -Wl,-rpath,/opt/intel-16.0/compilers_and_libraries_2016.0.083/mac/compiler/lib -L/opt/intel-16.0/compilers_and_libraries_2016.0.083/mac/compiler/lib -Wl,-rpath,/opt/intel-16.0/compilers_and_libraries_2016.0.083/mac/mkl/lib -lmpifort -lifcore<br>
<br>
</span>Does linking with -lifcore vs<br>
/opt/intel-16.0/compilers_and_libraries_2016.0.083/mac/compiler/lib/libifcore.a<br>
make a difference?<br>
<br>
And what do you have for:<br>
<br>
cd /opt/HPC/mpich-3.1.4-intel16.0/lib<br>
ls<br>
nm -Ao libmpiifort.* |grep get_command_argument<br>
<br>
BTW: I'm assuming you have sept 20 or newer petsc master branch.<br>
<span class="HOEnZb"><font color="#888888"><br>
Satish<br>
</font></span></blockquote></div><br><br clear="all"><div><br></div>-- <br><div class="gmail_signature">Jeff Hammond<br><a href="mailto:jeff.science@gmail.com" target="_blank">jeff.science@gmail.com</a><br><a href="http://jeffhammond.github.io/" target="_blank">http://jeffhammond.github.io/</a></div>
</div></div></div>