Re: Building issues (lilypond and docs)

[Alexander Kobel]

On 2016-12-30 22:04, Jay Anderson wrote:
> In response to this thread:
> https://lists.gnu.org/archive/html/lilypond-user/2016-12/msg00679.html
> I'm attempting to build lilypond.

Hi Jay,

thanks for looking into this.

> When building locally (an older version of mint linux) [...]

Sorry, I have no own experience with Mint, so I can only do some random 
guesswork. Which version of Mint are you using?

> Cannot open /home/jay/programming/lilypond/build/mf/out/feta11.pfb
> The requested file, feta11.pfb, does not exist
> MergeFonts: Can't find font: feta11.pfb
>
> Sure enough it looks like feta11.pfb wasn't built. What should I look
> at to see why it wasn't built?

Can you call a `make out/feta11.pfb` in 
/home/jay/programming/lilypond/build/mf/? Maybe something is broken with 
the Metafont setup?

I guess you already checked the compilation requirements from

http://lilypond.org/doc/v2.18/Documentation/contributor/requirements-for-compiling-lilypond#linux-mint 
and

http://lilypond.org/doc/v2.19/Documentation/contributor/requirements-for-compiling-lilypond#linux-mint

AFAICS, the FontForge version that is used is recent enough (and I think 
it is even built with the --enable-double flag or its modern equivalent 
by default, and the package maintainers are unlikely to have changed 
this). Can you see anything suspicious when you manually perform the 
commands:

> make[1]: Entering directory `/home/jay/programming/lilypond/build/mf'
> /home/jay/programming/lilypond/build/scripts/build/out/gen-emmentaler-scripts
> --dir=./out --design-size=11
> cd ./out && /usr/bin/fontforge -script emmentaler-11.genpe

The .genpe files are automatically generated by scripts. Does your Mint 
installation default to some recent Python2?
On Arch Linux, the following environment settings are used for building 
Lilypond packages:
  export PYTHON=python2
  export PYTHON_CONFIG=python2-config
  export GUILE=/usr/bin/guile1.8
  export GUILE_CONFIG=/usr/bin/guile-config1.8
where python2 is actually python2.7.

> Moving on from that I tried using lilydev and it builds fine in the
> virtual machine, but when attempting `make doc` it ran for days on the
> learning manual before I killed it. I gave the virtual machine 2gb to
> work with. I'm going to try upping that to 4gb before trying again. Is
> there anything else to look at here?

Again, no idea, sorry. Building the documentation is a huge time-sink, 
but that's way more than expected...


Cheers,
Alexander