Francisco Vila <paconet....@gmail.com> writes: > El 9/3/20 a las 21:19, Han-Wen Nienhuys escribió: >> On Mon, Mar 9, 2020 at 9:07 PM Francisco Vila <paconet....@gmail.com> wrote: >>>>> Sorry if it's in CG already, I could be wrong, but Doc build is not >>>>> multi-thread safe, first time at least. It uses files generated by the >>>>> build process itself. >>>>> >>>>> Right? >> well, the doc build uses lilypond, which is generated by the build >> process, so you first have to do "make" before doing "make doc". But >> that is not what you mean? > > I meant doc build after the binary is made. > >> I regularly run "make doc" with -j4 without issues. > > I used to make docs with -j7 succesfully but it always surprises me > how the _first_ time it _never_ succeeds. That's why I say there > _might_ be a problem with multi_threading.
I had a problem running just "make" with essentially ./configure GUILE_CONFIG=/usr/local/tmp/guile-1.8/bin/guile-config until I figured out that specifying GUILE_CONFIG kept our configure script from looking for a GUILE executable. This was fixed by using ./configure GUILE_CONFIG=/usr/local/tmp/guile-1.8/bin/guile-config GUILE=/usr/bin/guile The Guile executable was needed for generating some manual page I think? This failed for the first round, but the first round left a stale file that then managed to get to completion. This got recently changed in master so the stale file was not left around, and the first failure did not help. I haven't reported the GUILE_CONFIG/GUILE dependency problem so far. Probably not related to your problem, though. -- David Kastrup
