Re: [petsc-dev] SuperLU build error

2015-12-18 Thread Xiaoye S. Li
Thanks. I updated the superlu_5.1.tar.gz tar ball with this fix. Sherry On Fri, Dec 18, 2015 at 10:37 AM, Satish Balay wrote: > Sorry - looks like the superlu issue sliped through the cracks. > > However supleru_dist was fixed in upstream tarball [so its patched > in tarballs used by petsc asw

[petsc-dev] [mpich-trac] #2321: mpich-3.2 is not valgrind clean with petsc examples

2015-12-18 Thread mpich
#2321: mpich-3.2 is not valgrind clean with petsc examples ---+--- Reporter: balay | Type: bug Status: new| Priority: major Milestone: | Component: mpich Keywords: | ---+--- When petsc switched

Re: [petsc-dev] SuperLU build error

2015-12-18 Thread Garth N. Wells
On 18 December 2015 at 18:37, Satish Balay wrote: > Sorry - looks like the superlu issue sliped through the cracks. > > However supleru_dist was fixed in upstream tarball [so its patched > in tarballs used by petsc aswell] > > I've fixed the superlu issue in petsc 'maint' and 'master'- and > veri

Re: [petsc-dev] SuperLU build error

2015-12-18 Thread Satish Balay
Sorry - looks like the superlu issue sliped through the cracks. However supleru_dist was fixed in upstream tarball [so its patched in tarballs used by petsc aswell] I've fixed the superlu issue in petsc 'maint' and 'master'- and verified superlu+superlu_dist build with: CFLAGS="-Wformat -Wformat

Re: [petsc-dev] SuperLU build error

2015-12-18 Thread Garth N. Wells
On 18 December 2015 at 16:45, Barry Smith wrote: > >Garth, > > Yes this has been an on going nuisance. Do you have this problem with > the master development version or some previous release? > > master (updated earlier today). Garth >Satish, > > I thought this was now fully

Re: [petsc-dev] SuperLU build error

2015-12-18 Thread Barry Smith
Garth, Yes this has been an on going nuisance. Do you have this problem with the master development version or some previous release? Satish, I thought this was now fully resolved? Barry > On Dec 18, 2015, at 2:52 AM, Garth N. Wells wrote: > > I've reported before that

Re: [petsc-dev] SuperLU build error

2015-12-18 Thread Garth N. Wells
On 18 December 2015 at 16:10, Jeff Hammond wrote: > Are you intentionally turning printf security warnings into errors for an > HPC code or is that the default setting for PETSc? Or perhaps GCC enables > that by default now? > > It's the default with the Ubuntu MPICH package. Garth > Jeff > >

Re: [petsc-dev] SuperLU build error

2015-12-18 Thread Jeff Hammond
Are you intentionally turning printf security warnings into errors for an HPC code or is that the default setting for PETSc? Or perhaps GCC enables that by default now? Jeff On Thursday, December 17, 2015, Garth N. Wells wrote: > I've reported before that SuperLU has a bug that causes compile f

Re: [petsc-dev] Fortran Interfaces

2015-12-18 Thread Tobin Isaac
Each of the functions you listed had its name changed by removing the "plex" from the middle: did you make that change in your code? Can you send me the error messages you're getting? On Fri, Dec 18, 2015 at 07:04:13AM +, John O'Sullivan wrote: > Hi Toby, > > Sorry we tried a completely cle

[petsc-dev] SuperLU build error

2015-12-18 Thread Garth N. Wells
I've reported before that SuperLU has a bug that causes compile failures: util.c:32:18: error: format not a string literal and no format arguments [-Werror=format-security] fprintf(stderr, msg); I usually fix this by hand, but the way PETSc since very recently resets user changes in clon