Satish, Where did you find this error message on the web? I couldn't find any building of the manual from the Dashboard.
> On Mar 22, 2018, at 11:05 AM, Balay, Satish <ba...@mcs.anl.gov> wrote: > >>>>>>>>>> > petsc@thwomp:/sandbox/petsc/petsc.clone/src/docs/tex/manual$ /usr/bin/make > --no-print-directory manual.pdf LOC=/sandbox/petsc/petsc.clone GONULL= > <snip> > > aTeX Warning: Reference `ch_index' on page 7 undefined on input line 42. > > ) [7] [8] (./acknowltmp.tex > ! You can't use `macro parameter character #' in horizontal mode. > l.1 ...++man+manualpages/Mat/MatMPIAdjToSeq-.html# > MatMPIAdjToSeq- > ! ==> Fatal error occurred, no output PDF file produced! > Transcript written on manual1.log. > make: *** [manual.pdf] Error 1 > <<<<<<<<<<< > > Perhaps the following fix: > >>>>>>>>> > > diff --git a/src/mat/impls/adj/mpi/mpiadj.c b/src/mat/impls/adj/mpi/mpiadj.c > index 5241a8fae9..e8425726d9 100644 > --- a/src/mat/impls/adj/mpi/mpiadj.c > +++ b/src/mat/impls/adj/mpi/mpiadj.c > @@ -806,7 +806,7 @@ PETSC_EXTERN PetscErrorCode MatCreate_MPIAdj(Mat B) > } > > /*@C > - MatMPIAdjToSeq- Converts an parallel MPIAdj matrix to complete MPIAdj on > each process (needed by sequential preconditioners) > + MatMPIAdjToSeq - Converts an parallel MPIAdj matrix to complete MPIAdj on > each process (needed by sequential preconditioners) > > Logically Collective on MPI_Comm > <<<<<< > > Will check if this works.. > > Satish > > > On Thu, 22 Mar 2018, Smith, Barry F. wrote: > >> >> I'll talk to Satish, it is now unclear (at least to me) where the manual >> is actually built and the output stored. >> >> >>> On Mar 22, 2018, at 5:17 AM, Patrick Sanan <patrick.sa...@gmail.com> wrote: >>> >>> The manual and dev manual automated builds are failing on master, but I >>> can't reproduce on any of my local builds and the output is now very terse, >>> so it's not obvious to me how to debug. There were some updates recently to >>> the manual make process, which could be related. >>> >>> I'd move to re-introduce more of the tex output by default when building >>> the manuals - this clutters the log but overall I'd say would save time >>> (and might be the most efficient way to debug this current issue). >> >> >
