--with-log=0 and you don't have code to manage this case. Take a look at the petsclog.h for #else after the defined(PETSC_USE_LOG) you need macros that return 0 for those two things.
On Dec 25, 2018, at 11:49 AM, Matthew Knepley via petsc-dev <[email protected]> wrote:
This makes no sense,
petscvonest.h includes petscsnes.h includes petsksp.h includes petscpc.h includes petscmat.h includes petscvec.h includes petscis.h includes petscsys.h includes petsclog.h includes the declaration.
Thanks,
Matt
---------- Forwarded message --------- From: PETSc checkBuilds <[email protected]> Date: Mon, Dec 24, 2018 at 4:28 PM Subject: PETSc blame digest (next-tmp) 2018-12-24 To: Matthew Knepley <[email protected]>, PETSc checkBuilds <[email protected]>
Dear PETSc developer,
This email contains listings of contributions attributed to you by `git blame` that caused compiler errors or warnings in PETSc automated testing. Follow the links to see the full log files. Please attempt to fix the issues promptly or let us know at [email protected] if you are unable to resolve the issues.
Thanks, The PETSc development team
----
warnings attributed to commit https://bitbucket.org/petsc/petsc/commits/a56d3bf ConvEst: Separately fit convergence rate for each field
src/snes/utils/convest.c:362 [http://ftp.mcs.anl.gov/pub/petsc/nightlylogs/archive/2018/12/24/build_next-t...] "/export/home/petsc/petsc.next-tmp-2/src/snes/utils/convest.c", line 362: warning: implicit function declaration: PetscLogEventSetDof
src/snes/utils/convest.c:363 [http://ftp.mcs.anl.gov/pub/petsc/nightlylogs/archive/2018/12/24/build_next-t...] "/export/home/petsc/petsc.next-tmp-2/src/snes/utils/convest.c", line 363: warning: implicit function declaration: PetscLogEventSetError
---- To opt-out from receiving these messages - send a request to [email protected].
-- What most experimenters take for granted before they begin their experiments is infinitely more interesting than any results to which their experiments lead. -- Norbert Wiener