[petsc-dev] build on cygwin for cygwin

[Satish Balay]

On Tue, 28 Feb 2017, Marco Atzeri wrote:

> On 27/02/2017 19:56, Satish Balay wrote:
> > On Mon, 27 Feb 2017, Marco Atzeri wrote:
> >
> > > On 27/02/2017 19:15, Satish Balay wrote:
> > > > Ah - previously I didn't check the error log closely.
> > > >
> 
> > > > Hm - the test for sequential build failed? Perhaps you had some mixup
> > > > of files with the previous openmpi build.
> > > > When changing builds (like switching mpi) - its best to remove build
> > > > files in PETSC_ARCH - and install files in prefix-dir - before the
> > > > next build.  Or use a different PETSC_ARCH/prefix values for the
> > > > second build.
> > >
> > > I am using in general different directories.
> > > I will try again just in case I missed something.
> > >
> > > > I tried both builds - and they ran fine for me. [with maint/3.7]
> 
> static build works fine, including the stream test.

I was refering to the dll build [and with-mpi=0]. The C examples run fine for me.

> 
> > > >
> > > > Either way - fortran examples don't work with dlls - so its best to
> > > > use --with-shared-libraries=0
> > >
> > > don't work in general or just for cygwin ?
> >
> > PETSc fortran interface uses fortran common blocks - and DLLs (with
> > common blocks) require some compiler directives (perhaps compiler
> > specific wrt ifort vs gfortran) to handle this.
> >
> > We don't yet have that in petsc.
> 
> I assume it is related to you inquiry on the cygwin mailing list
> https://cygwin.com/ml/cygwin/2015-06/msg00352.html
> 

yes

> Had you any progress or the matter or is it still there the blocking point ?
> Just to know what to investigate as simple test case.

This is where it stands. If you are able to make progress - you can submit a PR

thanks,
Satish

> 
> > Satish
> 
> Regards
> Marco
> 
> 
>