> On Jan 26, 2018, at 8:14 AM, Vaclav Hapla <[email protected]> wrote: > >> >> There must be something broken in my system as I also get bunch of >> /bin/sh: 2: -map: not found >> errors for >> make alldoc LOC=${PETSC_DIR} >> which means also MAPNAMES is not set. >> I started from scratch in different PETSc clone and it's the same. >> Interesting. > > The variables were not set because sowing was not installed. It didn't come > to my mind as sowing is not directly related to the PDF manual processing. > Damn.
Yikes, sorry for your wasted time, the makefile in the manual generation directory could/should check that sowing is installed (the variables are set) before trying to build the manual and print a very useful error message if they are not setting telling the person to rerun configure appropriately. The reason the manual needs Sowing is that it builds the function index from the index of PETSc functions generated by the rest of documentation building process plus makes links to the manual pages. Barry > >> >> Vaclav >> >>> >>> Vaclav >>> >>>> >>>> 2018-01-26 14:00 GMT+01:00 Vaclav Hapla <[email protected]>: >>>> >>>> >>>> > 25. 1. 2018 v 9:33, Smith, Barry F. <[email protected]>: >>>> > >>>> > >>>> > src/docs/tex/manual/developers.tex there is also a make file that >>>> > generates the PDF. >>>> >>>> I'm trying to build the manual. Apparently the PDFLATEX variable is not >>>> set. So I set it externally and it works - is it supposed to be done this >>>> way? Would you mind adding the PDFLATEX variable into >>>> ${PETSC_DIR}/lib/petsc/conf/variables? Perhaps with assigned using ?= so >>>> that it could be overridden? >>>> >>>> Vaclav >>>> >>>> > >>>> > Barry >>>> > >>>> > The document should provide information about the location of its source. >>>> > >>>> > >>>> > >>>> >> On Jan 25, 2018, at 2:19 AM, Vaclav Hapla <[email protected]> >>>> >> wrote: >>>> >> >>>> >> >>>> >> >>>> >>> 24. 1. 2018 v 22:55, Scott Kruger <[email protected]>: >>>> >>> >>>> >>> >>>> >>> >>>> >>> On 1/24/18 6:50 AM, Vaclav Hapla wrote: >>>> >>>>> 24. 1. 2018 v 14:45, Vaclav Hapla <[email protected]>: >>>> >>>>> >>>> >>>>> How should I specify output files for {{...}} with different >>>> >>>>> outputs, please? >>>> >>>> Oh I see, {{...}separateoutput} is meant literally. But in that case >>>> >>>> typesetting it in italics is confusing. >>>> >>> >>>> >>> It's clearer in the examples listed below. I couldn't get lstinline >>>> >>> to work for this syntax so used $ ... $. If someone knows how to do >>>> >>> it, please feel free to fix. >>>> >> >>>> >> Where are this manual's latex sources? >>>> >> >>>> >> Vaclav >>>> >> >>>> >>> >>>> >>> Scott >>>> >>> >>>> >>>> Vaclav >>>> >>>>> >>>> >>>>> I have consulted the developers manual but it's not clear to me >>>> >>>>> still. And the example listings, page 34-45, seem to be broken. >>>> >>>>> >>>> >>>>> BTW in 7.1.2, I think there should be the space instead of the comma >>>> >>>>> in the listing. >>>> >>>>> >>>> >>>>> Thanks >>>> >>>>> >>>> >>>>> Vaclav >>>> >>> >>>> >>> -- >>>> >>> Tech-X Corporation [email protected] >>>> >>> 5621 Arapahoe Ave, Suite A Phone: (720) 974-1841 >>>> >>> Boulder, CO 80303 Fax: (303) 448-7756 >>>> >> >>>> > >
