[petsc-users] MPICH C++ compilers when using PETSC --with-cxx=0

[Satish Balay]

On Fri, 21 Jul 2023, Satish Balay via petsc-users wrote:

> Were you able to try Jacob's fix - so you could build with cxx?
> 
> Wrt building external pkgs - one way:
> 
> - first build pkgs:
> ./configure PETSC_ARCH=arch-pkgs --prefix=$HOME/soft/petsc-pkgs --with-cc=icc --with-cxx=icpc --with-fc=ifort --download-mpich --download-suitesparse
> 
> - now build PETSc with these pkgs
> ./configure PETSC_ARCH=arch-mybuild --with-mpi-dir=$HOME/soft/petsc-pkgs --with-cxx=0
> 
> [can't use --with-suitesparse-dir here - due to cxx dependencies within configure - but you disable this dependency check in configure - by commenting out one line of code]
> 
> Wrt configure options used - they are listed in configure.log - also in - for ex:
> 
> [balay at pj01 petsc]$ ls arch-linux-c-debug/externalpackages/*/*petsc*
> arch-linux-c-debug/externalpackages/git.sowing/sowing.petscconf

Also at:

[balay at pj01 petsc]$ ls arch-linux-c-debug/lib/petsc/conf/pkg.conf*
arch-linux-c-debug/lib/petsc/conf/pkg.conf.sowing

Satish

> 
> Satish
> 
> On Fri, 21 Jul 2023, Barry Smith wrote:
> 
> > 
> >   You need to look in the configure.log you to see the exact configure/cmake command PETSc configure is using for each package it builds specific to that run of PETSc configure. We do not save them in some other place.
> > 
> > 
> > 
> > > On Jul 21, 2023, at 12:14 PM, Robert.Crockett at lamresearch.com wrote:
> > > 
> > > Can I easily get the MPICH config PETSc uses? I’m poking through the repo and not seeing anything related to config of downloaded packages.
> > > Thanks,
> > > Robert
> > >  
> > > From: Barry Smith <bsmith at petsc.dev <mailto:bsmith at petsc.dev>> 
> > > Sent: Friday, July 21, 2023 11:35 AM
> > > To: Crockett, Robert <Robert.Crockett at lamresearch.com <mailto:Robert.Crockett at lamresearch.com>>
> > > Cc: petsc-users at mcs.anl.gov <mailto:petsc-users at mcs.anl.gov>
> > > Subject: Re: [petsc-users] MPICH C++ compilers when using PETSC --with-cxx=0
> > >  
> > > You don't often get email from bsmith at petsc.dev <mailto:bsmith at petsc.dev>. Learn why this is important <https://aka.ms/LearnAboutSenderIdentification>	
> > >  
> > > External Email: Do NOT reply, click on links, or open attachments unless you recognize the sender and know the content is safe. If you believe this email may be unsafe, please click on the “Report Phishing” button on the top right of Outlook.
> > > 
> > >  
> > > 
> > >  
> > >   No, you will need to build MPICH yourself, stand-alone and then direct PETSc's configure to use what you have built.
> > >  
> > >   Barry
> > >  
> > > 
> > > 
> > > On Jul 21, 2023, at 11:11 AM, Robert Crockett via petsc-users <petsc-users at mcs.anl.gov <mailto:petsc-users at mcs.anl.gov>> wrote:
> > >  
> > > Hello,
> > > I built PETSc with –with-cxx=0 in order to get around a likely Intel C++ compiler bug.
> > > However, the MPICH that also gets built by PETSc then picks up the wrong C++ compiler; mpicxx -show indicates that it is using G++, while mpicc is correctly using icc.
> > >  
> > > Is there a way to get PETSc to pass the correct C++ compiler for the MPICH build when using –with-cxx=0? I need to compile parts of my own program with mpicxx/icpc.
> > > Robert Crockett 
> > > Plasma Simulation Engineer | OCTO - Computational Products
> > > P: 617.648.8349  M: 415.205.4567
> > > 
> > > LAM RESEARCH
> > > 4650 Cushing Pkwy, Fremont CA 94538 USA 
> > > lamresearch.com <https://www.lamresearch.com/>
> > > <image001.png>
> > >  
> > > 
> > > LAM RESEARCH CONFIDENTIALITY NOTICE: This e-mail transmission, and any documents, files, or previous e-mail messages attached to it, (collectively, "E-mail Transmission") may be subject to one or more of the following based on the associated sensitivity level: E-mail Transmission (i) contains confidential information, (ii) is prohibited from distribution outside of Lam, and/or (iii) is intended solely for and restricted to the specified recipient(s). If you are not the intended recipient, or a person responsible for delivering it to the intended recipient, you are hereby notified that any disclosure, copying, distribution or use of any of the information contained in or attached to this message is STRICTLY PROHIBITED. If you have received this transmission in error, please immediately notify the sender and destroy the original transmission and its attachments without reading them or saving them to disk. Thank you.
> > > 
> > > 
> > > Confidential – Limited Access and Use
> > >  
> > > 
> > > Confidential – Limited Access and Use
> > > 
> > 
> > 
>