Re: [petsc-users] PETSc and Windows 10

be fine with > /usr/bin/ar > > Paolo > > > > Inviato da smartphone Samsung Galaxy. > > > > Messaggio originale > Da: Paolo Lampitella > Data: 05/07/20 14:00 (GMT+01:00) > A: Pierre Jolivet > Cc: Matthew Knepley , petsc-users >

Re: [petsc-users] PETSc and Windows 10

I'll be fine with /usr/bin/ar Paolo Inviato da smartphone Samsung Galaxy. Messaggio originale Da: Paolo Lampitella Data: 05/07/20 14:00 (GMT+01:00) A: Pierre Jolivet Cc: Matthew Knepley , petsc-users Oggetto: RE: [petsc-users] PETSc and Windows 10 Thank you very much

Re: [petsc-users] PETSc and Windows 10

: Matthew Knepley , petsc-users Oggetto: Re: [petsc-users] PETSc and Windows 10 Hello Paolo, On 5 Jul 2020, at 1:15 PM, Paolo Lampitella mailto:paololampite...@hotmail.com>> wrote: Dear all, I just want to update you on my journey to PETSc compilation in Windows under MSYS2+M

Re: [petsc-users] PETSc and Windows 10

f a large code > restructuring, I can’t do much more with it, now, from my code. But if you > can suggest some specific tutorial to use as test also for the parallel, I > would be glad to dig deeper into the matter. > > Best regards > > Paolo > > Inviato da Posta <h

Re: [petsc-users] PETSc and Windows 10

> Da: Pierre Jolivet <mailto:pierre.joli...@enseeiht.fr> > Inviato: lunedì 29 giugno 2020 21:37 > A: Paolo Lampitella <mailto:paololampite...@hotmail.com> > Cc: Matthew Knepley <mailto:knep...@gmail.com>; petsc-users > <mailto:petsc-users@mcs.anl.gov> &g

Re: [petsc-users] PETSc and Windows 10

/fwlink/?LinkId=550986> per >> Windows 10 >> >> Da: Pierre Jolivet <mailto:pierre.joli...@enseeiht.fr> >> Inviato: lunedì 29 giugno 2020 20:01 >> A: Matthew Knepley <mailto:knep...@gmail.com> >> Cc: Paolo Lampitella <mailto:paololampite...@hot

Re: [petsc-users] PETSc and Windows 10

Inviato: lunedì 29 giugno 2020 20:01 > A: Matthew Knepley <mailto:knep...@gmail.com> > Cc: Paolo Lampitella <mailto:paololampite...@hotmail.com>; petsc-users > <mailto:petsc-users@mcs.anl.gov> > Oggetto: Re: [petsc-users] PETSc and Windows 10 > > > >

Re: [petsc-users] PETSc and Windows 10

IGNED_CHAR=z'4c000102') > |1 > > Thanks, > > Matt > > Thanks > > > > Paolo > > > > Inviato da Posta <https://go.microsoft.com/fwlink/?LinkId=550986> per Windows > 10 > > > >

Re: [petsc-users] PETSc and Windows 10

> 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 >

Re: [petsc-users] PETSc and Windows 10

Data: 28/06/20 18:17 (GMT+01:00) A: Satish Balay via petsc-users Cc: Paolo Lampitella , Pierre Jolivet Oggetto: Re: [petsc-users] PETSc and Windows 10 On Sun, 28 Jun 2020, Satish Balay via petsc-users wrote: > On Sun, 28 Jun 2020, Paolo Lampitella wrote: > > * For my Cygwin-

Re: [petsc-users] PETSc and Windows 10

On Sun, 28 Jun 2020, Satish Balay via petsc-users wrote: > On Sun, 28 Jun 2020, Paolo Lampitella wrote: > > * For my Cygwin-GNU route (basically what is mentioned in PFLOTRAN > > documentation), am I expected to then run from the cygwin terminal or > > should the windows prompt work as

Re: [petsc-users] PETSc and Windows 10

To clarify - I would like to have a petsc test with MSYS2 working. Previously I was lost with MSYS2 - so I stick with what I'm familiar with. However with your instructions - I'm hoping to make progress. What I object to are suggestions (that come up regularly) of replacing what we currently

Re: [petsc-users] PETSc and Windows 10

Hello Paolo, > On 28 Jun 2020, at 4:19 PM, Satish Balay wrote: > > On Sun, 28 Jun 2020, Paolo Lampitella wrote: > >> 1. MSYS2+MinGW64 compilers. I understood that MinGW is not well supported, >> probably because of how it handles paths, but I wanted to give it a try, >> because it should

Re: [petsc-users] PETSc and Windows 10

BTW: How does redistributing MPI/runtime work with all the choices you have? For ex: with MS-MPI, Intel-MPI - wouldn't the user have to install these packages? [i.e you can't just copy them over to a folder and have mpiexec work - from what I can tell] And how did you plan on installing MPICH

Re: [petsc-users] PETSc and Windows 10

On Sun, 28 Jun 2020, Paolo Lampitella wrote: > Dear PETSc users, > > I’ve been an happy PETSc user since version 3.3, using it both under Ubuntu > (from 14.04 up to 20.04) and CentOS (from 5 to 8). > > I use it as an optional component for a parallel Fortran code (that, BTW, > also uses

Re: [petsc-users] petsc on windows

Thanks for the update. Yes - having the wrong variant of libpetsc.dll in PATH can cause problems. Satish On Fri, 30 Aug 2019, Sam Guo via petsc-users wrote: > Thanks a lot for your help. It is my pilot error: I have both serial > version and parallel version of petstc. It turns out serial

Re: [petsc-users] petsc on windows

Thanks a lot for your help. It is my pilot error: I have both serial version and parallel version of petstc. It turns out serial version is always loaded. Now parallel petstc is working. On Thu, Aug 29, 2019 at 5:51 PM Balay, Satish wrote: > On MS-Windows - you need the location of the DLLs in

Re: [petsc-users] petsc on windows

On MS-Windows - you need the location of the DLLs in PATH Or use --with-shared-libraries=0 Satish On Thu, 29 Aug 2019, Sam Guo via petsc-users wrote: > When I use intel mpi, configuration, compile and test all work fine but I > cannot use dll in my application. > > On Thu, Aug 29, 2019 at

Re: [petsc-users] petsc on windows

After I removed following lines inin config/BuildSystem/config/package.py, configuration finished without error. self.executeTest(self.checkDependencies) self.executeTest(self.configureLibrary) self.executeTest(self.checkSharedLibrary) I then add my mpi wrapper to

Re: [petsc-users] petsc on windows

On Thu, 29 Aug 2019, Sam Guo via petsc-users wrote: > I can link when I add my wrapper to > PCC_LINKER_FLAGS =-MD -wd4996 -Z7 > /home/xianzhongg/dev/star/lib/win64/intel18.3vc14/lib/StarMpiWrapper.lib I don't understand what you mean here. Add PCC_LINKER_FLAGS to where? This is a variable

Re: [petsc-users] petsc on windows

I can link when I add my wrapper to PCC_LINKER_FLAGS =-MD -wd4996 -Z7 /home/xianzhongg/dev/star/lib/win64/intel18.3vc14/lib/StarMpiWrapper.lib (I don't understand why configure does not include my wrapper) On Thu, Aug 29, 2019 at 1:28 PM Matthew Knepley wrote: > On Thu, Aug 29, 2019 at

Re: [petsc-users] petsc on windows

Thanks for the quick response. Attached please find the configure.log containing the configure error. Regarding our dup, our wrapper does support it. In fact, everything works fine on Linux. I suspect on windows, PETSc picks the system mpi.h somehow. I am investigating it. Thanks, Sam On Thu,

Re: [petsc-users] Petsc with Windows

On Wed, Nov 30, 2016 at 6:03 AM, Boris Kaus wrote: > > > This is probably a better choice than Cygwin going forward. > > > > https://msdn.microsoft.com/en-us/commandline/wsl/about > > > > I don't know to what extent PETSc users have experimented with this > > feature, but it

Re: [petsc-users] Petsc with Windows

Hi Elaine, The PETSc configured/built in Cygwin can be normally used outside of it. It can either be statically linked with your software, or linked as a .DLL and deployed normally :). On Mon, Nov 28, 2016 at 1:49 PM, Elaine Tang wrote: > Hi, > > I am developing some

Re: [petsc-users] Petsc with Windows

> This is probably a better choice than Cygwin going forward. > > https://msdn.microsoft.com/en-us/commandline/wsl/about > > I don't know to what extent PETSc users have experimented with this > feature, but it should make it easier to build and distribute PETSc. We have tried this in Mainz,

Re: [petsc-users] Petsc with Windows

May I propose docker as an alternative approach? https://www.docker.com There are already petsc images and creating your own environment is not that hard. As a bonus you get a cross platform solution ... unless your application is windows specific in which case docker might not be the best way to

Re: [petsc-users] Petsc with Windows

Elaine Tang writes: > I am developing some software on windows that would like to utilize petsc > library. Currently I have petsc library configured on cygwin on my windows > machine. This is probably a better choice than Cygwin going forward.