lilypond-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Patchy email


From: Knut Petersen
Subject: Re: Patchy email
Date: Mon, 29 Jul 2019 13:59:55 +0200
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.8.0

Hi David!

Thank you for the information you provided. Something is really broken,
but after quite some time of debugging, I'm beginning to wonder if it really
is my patch / system or if it might be that origin/master is broken after all.

Could you please verify if  (after adapting the arguments to configure in
line 6) executing the following commands in your local lilypond repository
succeeds? Be aware that there is a 'git clean' command, so save your work first!

   git clean -dfx
   git checkout origin/master
   ./autogen.sh --noconfigure
   mkdir -p build
   cd build
   ../configure --prefix=<path_to_target_dir> 
--with-urwotf-dir=<path_to_urw-core35-fonts_dir>
   make -j 11 CPU_COUNT=11 all
   make -j 11 CPU_COUNT=11 test-baseline

Making test-baseline really should succeed - on my system it does _not_ succeed
with the current origin/master. If making test-baseline does not succeed: Does 
it
succeed with my patch (1c51a616e289fffb918942c8f1e189ab50809157)?

Is there a safe way to execute a local patchy test?

Knut


reply via email to

[Prev in Thread] Current Thread [Next in Thread]