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.
W
Le 21/04/2022 à 04:57, Dan Eble a écrit :
On Apr 20, 2022, at 18:04, Jean Abou Samra wrote:
Calls to scm_dynwind_begin () and scm_dynwind_end () must be
paired correctly. Obviously, if '...' contains statements
causing non-local control flow like return, break, continue,
and such, it is easy to
On Apr 20, 2022, at 18:04, Jean Abou Samra wrote:
>
> Calls to scm_dynwind_begin () and scm_dynwind_end () must be
> paired correctly. Obviously, if '...' contains statements
> causing non-local control flow like return, break, continue,
> and such, it is easy to miss a scm_dynwind_end (). I read
Here is the current countdown list.
The next countdown will be on April 22nd.
A list of all merge requests can be found here:
https://gitlab.com/lilypond/lilypond/-/merge_requests?sort=label_priority
Push:
!1311 beam: remove unnecessary vector of forbidden intervals - Nihal Jere
https://
Hi,
It's me again ...
I am working on code that pervasively utilizes Guile fluids. They should
be set in dynamic scopes. In C++, usage of the Guile API looks like this:
scm_dynwind_begin ();
scm_dynwind_fluid (fluid, value);
...
scm_dynwind_end ();
Docs: https://www.gnu.org/software/gu
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 variable.
