Le 21/04/2022 à 09:31, Jonas Hahnfeld a écrit :
This says "to rebuild only 'contributor.pdf'", which should still work
fine in an incremental build, no?
Granted. The first of the two occurrences on that page
does not imply that the full documentation build should
be done first, though.
Jean
On Thu, 2022-04-21 at 09:13 +0200, Jean Abou Samra wrote:
> Le 21/04/2022 à 08:31, Jonas Hahnfeld a écrit :
> > On Tue, 2022-04-19 at 20:13 +0200, Jean Abou Samra wrote:
> > > Hi,
> > >
> > > This used to work for me in order to build just one document, as
> > > opposed to building the full
Le 21/04/2022 à 08:31, Jonas Hahnfeld a écrit :
On Tue, 2022-04-19 at 20:13 +0200, Jean Abou Samra wrote:
Hi,
This used to work for me in order to build just one document, as
opposed to building the full documentation:
make -j9 CPU_COUNT=9 -C Documentation out=www out-www/en/internals.pdf
On Tue, 2022-04-19 at 20:13 +0200, Jean Abou Samra wrote:
> Hi,
>
> This used to work for me in order to build just one document, as
> opposed to building the full documentation:
>
> make -j9 CPU_COUNT=9 -C Documentation out=www out-www/en/internals.pdf
>
> This is also recommended in the CG.
Le 20/04/2022 à 04:26, John Wheeler a écrit :
Jean,
My build was failing with similar messages until I ran
rm -fr ./configure
./autogen.sh --noconfigure
in the source directory.
This seems to have been needed to get ./configure to assign the
correct program name to the PLTOTF make
Jean,
My build was failing with similar messages until I ran
rm -fr ./configure
./autogen.sh --noconfigure
in the source directory.
This seems to have been needed to get ./configure to assign the correct
program name to the PLTOTF make variable.
Would this need a note in CG?
John
On
Hi,
This used to work for me in order to build just one document, as
opposed to building the full documentation:
make -j9 CPU_COUNT=9 -C Documentation out=www out-www/en/internals.pdf
This is also recommended in the CG.
Now, I get in internals.texi2pdf.log:
kpathsea: Running mktextfm lmttr
