Re: [petsc-users] PETSc initialization error

2020-06-29 Thread Junchao Zhang
On Mon, Jun 29, 2020 at 1:00 PM Sam Guo wrote: > Hi Junchao, >I'll test the ex53. At the meantime, I use the following work around: > my program call MPI initialize once for entire program > PetscInitialize once for entire program > SlecpInitialize once for entire program (I think I can skip

Re: [petsc-users] PETSc and Windows 10

2020-06-29 Thread Pierre Jolivet
> On 29 Jun 2020, at 9:37 PM, Pierre Jolivet wrote: > > I do not give up easily on Windows problems: > 1) that’s around 50% of our (FreeFEM) user-base (and I want them to use PETSc > and SLEPc, ofc…) > 2) most people I work with from corporations just have Windows > laptops/desktops and I

Re: [petsc-users] PETSc and Windows 10

2020-06-29 Thread Pierre Jolivet
I do not give up easily on Windows problems: 1) that’s around 50% of our (FreeFEM) user-base (and I want them to use PETSc and SLEPc, ofc…) 2) most people I work with from corporations just have Windows laptops/desktops and I always recommend MSYS because it’s very lightweight and you can pass

[petsc-users] R: PETSc and Windows 10

2020-06-29 Thread Paolo Lampitella
Dear Pierre, thanks again for your time I guess there is no way for me to use the toolchain you are using (I don’t remember having any choice on which version of MSYS or GCC I could install) Paolo Inviato da Posta per Windows 10 Da: Pierre

Re: [petsc-users] PETSc and Windows 10

2020-06-29 Thread Pierre Jolivet
> On 29 Jun 2020, at 7:47 PM, Matthew Knepley wrote: > > On Mon, Jun 29, 2020 at 1:35 PM Paolo Lampitella > wrote: > Dear Pierre, sorry to bother you, but I already have some issues. What I did: > > > > pacman -R mingw-w64-x86_64-python

Re: [petsc-users] PETSc initialization error

2020-06-29 Thread Sam Guo
Hi Junchao, I'll test the ex53. At the meantime, I use the following work around: my program call MPI initialize once for entire program PetscInitialize once for entire program SlecpInitialize once for entire program (I think I can skip PetscInitialize above) calling slepc multiple times my

Re: [petsc-users] R: PETSc and Windows 10

2020-06-29 Thread Matthew Knepley
On Mon, Jun 29, 2020 at 1:35 PM Paolo Lampitella < paololampite...@hotmail.com> wrote: > Dear Pierre, sorry to bother you, but I already have some issues. What I > did: > > > >- pacman -R mingw-w64-x86_64-python mingw-w64-x86_64-gdb (is gdb also >troublesome?) >- Followed points 6 and

Re: [petsc-users] PETSc and Windows 10

2020-06-29 Thread Pierre Jolivet
> On 29 Jun 2020, at 6:27 PM, Paolo Lampitella > wrote: > > I think I made the first step of having mingw64 from msys2 working with > ms-mpi. > > I found that the issue I was having was related to: > > https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91556 >

[petsc-users] R: PETSc and Windows 10

2020-06-29 Thread Paolo Lampitella
I think I made the first step of having mingw64 from msys2 working with ms-mpi. I found that the issue I was having was related to: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91556 and, probably (but impossible to check now), I was using an msys2 and/or mingw mpi package before this fix:

[petsc-users] R: PETSc and Windows 10

2020-06-29 Thread Paolo Lampitella
As a follow up on the OpenMPI matter in Cygwin, I wasn’t actually able to use the cygwin version at all, not even compiling a simple mpi test. And PETSc fails in using it as well, as it seems unable to find MPI_Init. I might try with having PETSc install it as it did with MPICH, but just for