Re: Building issues (lilypond and docs)

[James]

On Fri, 30 Dec 2016 15:07:24 -0700
Jay Anderson <address@hidden> wrote:

> On Fri, Dec 30, 2016 at 2:28 PM, Phil Holmes <address@hidden>
> wrote:
> > Just for clarity.  RAM or disk?  
> 
> In the VM:
> - Disk: 14gb (4.2gb used).
> - Memory: 4gb (after increasing from 2gb)
> 
> I started re-running the doc build about an hour ago. Neither disk nor
> memory seem to be in danger of being used up.
> 
> -----Jay
> 

You don't state what CPU (if any) options you apply to make.

'make doc' on its own will take an age. make -j3 CPU_COUNT=3 (for
example) will considerably speed things up - the more 'CPU' you can
spare the better.

Also I assume that when you ran ./configure (prior to make) that you
didn't get any problems. I.e. I would expect that *if* there were any
problems that might have hinted at why you had that feta issue earlier
(when you weren't using a VM) then that would be useful.

Finally we have some explicit instructions in the CG for a few Linux
Distributions - including Mint on what apt-get to run to make sure you
have all that you need for make, make doc (and make test-baseline/make
check).

I personally tested and documented those and have been making sure they
still apply for later versions of Mint, Fedora et al - once I have
completed that I will update the CG with the newer information.

See:
http://lilypond.org/doc/v2.19/Documentation/contributor-big-page.html#linux-mint

There is a warning in the latest unstable about URW+ fonts after the
configure, this was due to a recent improvement for Japanese (and
possibly other) Glyphs, so you can ignore that warning for .configure
(there is a tracker to update the CG with this that I'll probably get
around to in the next week or so).

Hope this helps

James