> On 21 Jul 2023, at 5:11 PM, Robert Crockett via petsc-users
> 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
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
No Jacob's fixes have not remedied the errors, unfortunately. Not for trying -
he has sent me an update since the first.
I'll build MPI separately; thanks for the tips.
~Robert
Confidential – Limited Access and Use
-Original Message-
From: Satish Balay
Sent: Friday, July 21, 2023
Thanks Junchao! Your fix worked perfectly.
Philip Fackler
Research Software Engineer, Application Engineering Group
Advanced Computing Systems Research Section
Computer Science and Mathematics Division
Oak Ridge National Laboratory
From: Fackler, Philip via
We don't have a good way to verify if the changes continue to work
with the minver of the pkg [and if minor fixes can get this working -
without increasing this requirement - sure without access to the new
features provided by the new version]
Having a single version dependency between pkgs makes
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.crock...@lamresearch.com 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
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
> wrote:
>
> Hello,
> I built PETSc with –with-cxx=0 in order to get around a likely Intel C++
>
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
hypre_Error was changed from an integer to a struct in hypre. PETSc code was
changed in main to work with that struct and not work if hypre_Error is an int.
This means main cannot work with previous hypre versions (where hypre_Error is
an int). Sure, instead of changing the minimum version
10 matches
Mail list logo
