[petsc-dev] Fwd: [petsc-users] configure error on Titan with Intel

[Barry Smith]

Configure Options: --configModules=PETSc.Configure --optionsModule=config.compilerOptions --COPTFLAGS="-mp -fast" --CXXOPTFLAGS="-mp -fast" --FOPTFLAGS="-mp -fast" --prefix=/autofs/na3_home1/adams/petsc_master_opt64idx_pgi --download-metis --with-hwloc=0 --download-parmetis --with-cc=cc --with-clib-autodetect=0 --with-cxx=CC --with-cxxlib-autodetect=0 --with-fc=ftn --with-fortranlib-autodetect=0 --with-shared-libraries=0 --known-mpi-shared-libraries=1 --with-x=0 --with-64-bit-indices --with-debugging=0 PETSC_ARCH=arch-titan-

  If you turn off autodetect for the language libraries and don't provide the correct link libraries with configure then there is no way it is going to work.



> On May 14, 2015, at 8:39 AM, Mark Adams <mfadams at lbl.gov> wrote:
> 
> We have Titan working but we have a problem that we need lstdc++ to get PETSc to configure.  Otherwise it fails to build fortran.  This seems to only be needed for GNU.  This is for PGI.  If we remove this C++ works, otherwise there is a missing external.  I guess I can just deploy two version, on for fortran and one for C++ (I have a C++ and a fortran code that I support).
> 
> 
> On Tue, May 12, 2015 at 9:36 AM, Barry Smith <bsmith at mcs.anl.gov> wrote:
> 
>   Remind me again how much the US tax payers spend on this machine each year.
> 
> 
>> Begin forwarded message:
>> 
>> From: Mark Adams <mfadams at lbl.gov>
>> Subject: Re: [petsc-users] configure error on Titan with Intel
>> Date: May 12, 2015 at 11:12:55 AM CDT
>> To: Barry Smith <bsmith at mcs.anl.gov>
>> Cc: Jed Brown <jed at jedbrown.org>, petsc-users <petsc-users at mcs.anl.gov>, "David Trebotich" <treb at lbl.gov>, "D'Azevedo, Ed F." <dazevedoef at ornl.gov>
>> 
>> 
>> 
>>   Notes: ./configure ran fine and detected -lhwloc in some standard system install location under normal circumstances it couldn't just disappear for a different example.
>> 
>> 
>> I configured in an interactive shell, so on a compute node.  I tried to 'make ex56' on a login node, as usual.  So I am guessing that it would have worked if I had made it a compute node.  They have an inconstancy, I'm guessing. I can try it all on a compute node ....
>> 
>> Mark
>>  
>> 
>> > /
>> >
>> > On Fri, May 8, 2015 at 5:51 PM, Jed Brown <jed at jedbrown.org> wrote:
>> > Satish Balay <balay at mcs.anl.gov> writes:
>> >
>> > > Also - Perhaps with intel compilers - the recommended blas is
>> > > something other than ACML? [like MKL?]. Something to check..
>> >
>> > MKL (and anything built using the Intel compiler) has the "run slower on
>> > AMD" feature.  For any given operation, ACML won't necessarily be
>> > faster, but at least it's not intentionally crippled.  For most of what
>> > PETSc does, any such MKL/ACML difference is irrelevant.
>> >
>> > <configure.log><make.log>
>> 
>> 
> 
> 
> <configure.log>