Improve handling of explicit C++ dialect requests in the following scenarios:

1. Fail immediately when a user explicitly requests a C++ dialect which the compiler fails
to satisfy instead of sile

Improve handling of explicit C++ dialect requests in the following scenarios:

1. Fail immediately when a user explicitly requests a C++ dialect which the compiler fails
to satisfy instead of silently deleting the compiler.
2. Fix handling of old C++ dialects, e.g. --with-cxx-dialect=c++[03|98]. If the user
explicitly requests these versions a hard error is produced. Previously the C++ compiler
would be silently deleted.
3. Fix handling of unsupported C++ dialects, e.g. --with-cxx-dialect=c++2b. Instead of
crashing configure, these are now correctly diagnosed as "Unknown C++ dialect".

Address the following additional C++ dialect errors. In all cases configure will now
produce an immediate error in checkCxxDialect():

1. --with-cxx=<does not work with C++11>
2. --downlod-package --with-cxx=<does not work with package C++ requirement>
3. --download-package (but implicit compiler does not support package min dialect).

show more ...

configure: update MUMPS, CMake, and p4est

SYCL: allow using icpx as syclc

Merge remote-tracking branch 'origin/release'

Merge branch 'barry/2023-04-14/check-for-conda-on-failure' into 'main'

If configure fails and Conda is running possibly print additional helpful text

See merge request petsc/petsc!6332

Merge branch 'barry/2023-04-19/fix-petsc4pybuild-rm-build-dir/release' into 'release'

make petsc4pybuild must rm src/binding/petsc4py/build

See merge request petsc/petsc!6339

Config: check mpich MPIX_Threadcomm

To faciliate mpich experiments, but currently no real tests yet.

Fix configuration crash.

Undefined loPacks variable

make petsc4pybuild must rm src/binding/petsc4py/build or else any old stuff in there (like from other PETSC_ARCH) also gets installed with make petsc4pyinstall

If configure fails and Conda is running print useful information in error message

In other words it automatically prints what we would send in our first email after looking at
configure.log

Satish

If configure fails and Conda is running print useful information in error message

In other words it automatically prints what we would send in our first email after looking at
configure.log

Satish may suggest tempering the wording

Commit-type: configure, build, debugability

show more ...

Merge remote-tracking branch 'origin/release'

Fix default MPI_COMM_WORLD communicator in Htool

Thanks-to: Pierre-Henri Tournier

Merge remote-tracking branch 'origin/release'

Merge branch 'jolivet/cleanup-buildsystem' into 'release'

BuildSystem: remove unused options

See merge request petsc/petsc!6311

BuildSystem: remove unused options

Fix typos

Merge branch 'jose/netlib-blaslapack' into 'main'

configure: add --download-netlib-lapack

See merge request petsc/petsc!6270

configure: add --download-netlib-lapack

Merge remote-tracking branch 'origin/release'

mpfr: add backup download url

Merge remote-tracking branch 'origin/release'

Fix -Wzero-as-null-pointer-constant

Merge remote-tracking branch 'origin/release'

Merge branch 'balay/fix-macos-version-check' into 'release'

configure: macos version check can fail

See merge request petsc/petsc!6289

config: fix --with-cmake-exec=path example

May as well not lead the user into this:

Warning! Incorrect argument type specified: -with-cmake=/usr/bin/cmake - expecting type Bool.