Hm - I would suggest doing a minimal build build with: --with-cxx=0 --with-clib-autodetect=0 --with-fortranlib-autodetect=0 LIBS="/opt/intel-16.0/compilers_and_libraries_2016.0.083/mac/compiler/lib/libifcore.a"
And see if that makes a difference. Satish On Sat, 19 Sep 2015, Blaise A Bourdin wrote: > Hi, > > I was traveling and did not have time to finish investigating, but there > seems to be an issue with fortran get_command_argument and friends in mixed > language mode. I will continue to investigate and will report back. > > Blaise > > > On Sep 19, 2015, at 10:18 AM, Satish Balay <ba...@mcs.anl.gov> wrote: > > > > [from the available logs] its not clear what the issue is. > > > > PETSc fortran interface attempts to use getarg_() and iargc_() [fortran > > library functions] - or its variants - directly from C. > > > > This usage is non-standard and messy [and some compiler folks - said - > > its unsupported usage]. > > > > Also - configure attempts to guess the fortran link libraries - and > > constructs a link command cCompilerLibs + cxxCompilerLibs + > > fortranCompilerLibs. > > > > Perhaps there is a bug in this detection code - thats triggering this > > error. Its verifyable by attempting to use: > > > > --with-clib-autodetect=0 --with-clib-autodetect=0 > > --with-cxxlib-autodetect=0 LIBS='liblist' > > > > where 'liblist' should be determined manually - for the linking of > > C/fortran/CXX to work correctly. > > > > My fix attempts to call command_argument_count(), > > get_command_argument() directly from fortran - and if that doesn't > > work - then its likely a compiler bug.. > > > > [which one can try to replicate with a simple test code] > > > > Satish > > > > On Thu, 17 Sep 2015, Jeff Hammond wrote: > > > >> Please report this via premier.intel.com. > >> > >> Jeff > >> > >> On Wed, Sep 16, 2015 at 11:13 AM, Blaise A Bourdin <bour...@lsu.edu> wrote: > >> > >>> Hi, > >>> > >>> I am testing intel 16 compilers under mac OS, and notice that options > >>> handling for all past and current versions of petsc is broken in fortran > >>> (options are not parsed). > >>> I narrowed it down to *argc at start.c:168 always being 0 when intel 16 is > >>> used (but taking the right value using intel 15 or gcc 5), but I can’t > >>> find > >>> my way through the multiple macros to figure out what is really the > >>> matter… > >>> The problem does not seem to arise under linux with the same compilers. > >>> > >>> Any idea of what is going on? Any test I can run to help (I assume that > >>> you don’t have a test box with the latest intel compilers)? Is it a petsc > >>> bug or an intel bug? > >>> > >>> I use an up to date pets-dev master, and the configure.log file is > >>> available at > >>> https://filestogeaux.lsu.edu/public/download.php?FILE=bourdin/89329uFByT9 > >>> > >>> Thanks, > >>> > >>> Blaise > >>> > >>> -- > >>> Department of Mathematics and Center for Computation & Technology > >>> Louisiana State University, Baton Rouge, LA 70803, USA > >>> Tel. +1 (225) 578 1612, Fax +1 (225) 578 4276 > >>> http://www.math.lsu.edu/~bourdin > >>> > >>> > >>> > >>> > >>> > >>> > >>> > >>> > >> > >> > >> > >