[Top][All Lists]

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

Re: Please test gub

From: Urs Liska
Subject: Re: Please test gub
Date: Tue, 29 Jan 2019 07:41:17 +0100
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.4.0

Hi Knut,

thank you for working on this, and - like Karlin - I wouldn't have tested without your straightforward recipe. But before going to bed I logged off, then logged in again in a terminal-only session and started the process.

Am 28.01.19 um 13:53 schrieb Knut Petersen:
Hi everybody!

I created a branch in my gub repository  that contains plus pull requests 53-60. Therefore it is pretty easy to test if that version of gub succeeds to build current lilypond master on your machine.

All you need to do is to execute the following commands:

   git clone -b DevelHead
   cd gub
   mkdir regtests
   cd regtests
   touch ignore
   cd ..
   time make lilypond

Even on a fast computer 'make lilypond' will take some hours to complete.
Seems the process completed after ~300 minutes ;-)

If downloading of a source archive fails because of some network problem restart 'make lilypond'.

You'll need some free disk space ... about 20 GB is a minimum.

Please report success / fails with os / version / cpu info.

How do I know whether it/everything worked? All I can see is the last bit of the terminal output, which gives me mixed signals. The overall end doesn't report a failure, but the last "rule" shows some problems, and I don't see how severe they are:

Two stages report things like "cross/gcc conflicts with cross/gcc-core" and some follow-ups, it always reports that a non-core version of the item is already installed and skips the request to install it. This relates to several "gcc" and "glibc" items.

I see lots of log files which I of course can't check to figure out everything's fine, and the 'target' directory contains about 17GB od files.

So what can I do to check whether make lilypond succeeded or failed?



lilypond-devel mailing list

reply via email to

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