Francisco Vila writes:
> El 9/3/20 a las 21:19, Han-Wen Nienhuys escribió:
>> On Mon, Mar 9, 2020 at 9:07 PM Francisco Vila 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 pr
El 9/3/20 a las 21:19, Han-Wen Nienhuys escribió:
On Mon, Mar 9, 2020 at 9:07 PM Francisco Vila 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 u
On Mon, Mar 9, 2020 at 9:07 PM Francisco Vila 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 generat
El 9/3/20 a las 20:41, David Kastrup escribió:
Francisco Vila writes:
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?
I tend to do
make clean test-clean doc-clean
CPU_COU
Francisco Vila writes:
> 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?
I tend to do
make clean test-clean doc-clean
CPU_COUNT=9 make -j9 && CPU_COUNT=9 make -j9 tes
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?
--
Francisco Vila, Ph.D. - Badajoz (Spain)
paconet.org , lilypond.es
