Thanks for these notes.
FWIW - I don't see this issue on the CI MacOS boxes [2 Intel (default
install of catalina, upgraded to ventura) , 1 M1 (montery, managed by
admins)]
And I think it should be preferable to avoid these nasty scripts that
keep modifying the firewall rules [per petsc binary,
Hi,
I realize this is an old thread but I have some recent experience based on
setting up an M2 Mac that might be relevant.
I was dreading moving to Apple Silicon Macs because of issues like these but I
actually did not run into this particular problem.
While I can’t be certain I think it is
> On 20 Mar 2023, at 2:45 AM, Barry Smith wrote:
>
>
> I found a bit more information in gmakefile.test which has the magic sauce
> used by make test to stop the firewall popups while running the test suite.
>
> # MACOS FIREWALL HANDLING
> # - if run with MACOS_FIREWALL=1
> #
I found a bit more information in gmakefile.test which has the magic sauce
used by make test to stop the firewall popups while running the test suite.
# MACOS FIREWALL HANDLING
# - if run with MACOS_FIREWALL=1
# (automatically set in $PETSC_ARCH/lib/petsc/conf/petscvariables if
configured
This helped only during the configure stage, and not during the check stage
and during executing the application built on PETSc. Do you think it is
because I built mpich locally and not with PETSc?
On Sun, Mar 19, 2023 at 3:51 PM Barry Smith wrote:
>
> ./configure option
./configure option with-macos-firewall-rules
> On Mar 19, 2023, at 5:25 PM, Amneet Bhalla wrote:
>
> Yes, this is MPI that is triggering the apple firewall. If I allow it it gets
> added to the allowed list (see the screenshot) and it does not trigger the
> firewall again. However, this
On Sun, Mar 19, 2023 at 1:59 PM Amneet Bhalla wrote:
> I'm building PETSc without mpi (I built mpich v 4.1.1 locally). Here is
> the configure command line that I used:
>
> ./configure --CC=mpicc --CXX=mpicxx --FC=mpif90 --PETSC_ARCH=darwin-dbg
> --with-debugging=1 --download-hypre=1 --with-x=0
I'm building PETSc without mpi (I built mpich v 4.1.1 locally). Here is the
configure command line that I used:
./configure --CC=mpicc --CXX=mpicxx --FC=mpif90 --PETSC_ARCH=darwin-dbg
--with-debugging=1 --download-hypre=1 --with-x=0
On Sun, Mar 19, 2023 at 10:56 AM Satish Balay wrote:
> I
I think its due to some of the system calls from MPI.
You can verify this with a '--with-mpi=0' build.
I wonder if there is a way to build mpich or openmpi - that doesn't trigger
Apple's firewall..
Satish
On Sun, 19 Mar 2023, Amneet Bhalla wrote:
> Hi Folks,
>
> I'm trying to build PETSc on
