LilyPond Contributor's Guide: 4.7 Problems

## 4.7 Problems

For help and questions use lilypond-user@gnu.org. Send bug reports to bug-lilypond@gnu.org.

Bugs that are not fault of LilyPond are documented here.

#### Bison 1.875

There is a bug in bison-1.875: compilation fails with "parse error before ‘goto’" in line 4922 due to a bug in bison. To fix, please recompile bison 1.875 with the following fix

>     $ cd lily; make out/parser.cc
>     $ vi +4919 out/parser.cc
>     # append a semicolon to the line containing "__attribute__ ((__unused__))
>     # save
>     $ make

#### Compiling on MacOS X

Here are special instructions for compiling under MacOS X. These instructions assume that dependencies are installed using MacPorts. The instructions have been tested using OS X 10.5 (Leopard).

First, install the relevant dependencies using MacPorts.

Next, add the following to your relevant shell initialization files. This is `~/.profile` by default. You should create this file if it does not exist.

>     export PATH=/opt/local/bin:/opt/local/sbin:$PATH
>     export DYLD_FALLBACK_LIBRARY_PATH=/opt/local/lib:$DYLD_FALLBACK_LIBRARY_PATH

Now you must edit the generated ‘`config.make`’ file. Change

>     FLEXLEXER_FILE = /usr/include/FlexLexer.h

to:

>     FLEXLEXER_FILE = /opt/local/include/FlexLexer.h

At this point, you should verify that you have the appropriate fonts installed with your ghostscript installation. Check `ls /opt/local/share/ghostscript/fonts` for: ’c0590*’ files (.pfb, .pfb and .afm). If you don’t have them, run the following commands to grab them from the ghostscript SVN server and install them in the appropriate location:

>     svn export http://svn.ghostscript.com/ghostscript/tags/urw-fonts-1.0.7pre44/
>     sudo mv urw-fonts-1.0.7pre44/* /opt/local/share/ghostscript/fonts/
>     rm -rf urw-fonts-1.07pre44

Now run the `./configure` script. To avoid complications with automatic font detection, add

>     --with-ncsb-dir=/opt/local/share/ghostscript/fonts

#### Solaris

Solaris7, ./configure

‘`./configure`’ needs a POSIX compliant shell. On Solaris7, ‘`/bin/sh`’ is not yet POSIX compliant, but ‘`/bin/ksh`’ or bash is. Run configure like

>     CONFIG_SHELL=/bin/ksh ksh -c ./configure

or

>     CONFIG_SHELL=/bin/bash bash -c ./configure

#### FreeBSD

To use system fonts, dejaview must be installed. With the default port, the fonts are installed in ‘`usr/X11R6/lib/X11/fonts/dejavu`’.

Open the file ‘`$LILYPONDBASE/usr/etc/fonts/local.conf`’ and add the following line just after the `<fontconfig>` line. (Adjust as necessary for your hierarchy.)

>     <dir>/usr/X11R6/lib/X11/fonts</dir>

#### International fonts

On Mac OS X, all fonts are installed by default. However, finding all system fonts requires a bit of configuration; see this post on the `lilypond-user` mailing list.

On Linux, international fonts are installed by different means on every distribution. We cannot list the exact commands or packages that are necessary, as each distribution is different, and the exact package names within each distribution changes. Here are some hints, though:

    Red Hat Fedora

        taipeifonts fonts-xorg-truetype ttfonts-ja fonts-arabic \
             ttfonts-zh_CN fonts-ja fonts-hebrew

    Debian GNU/Linux

       apt-get install emacs-intl-fonts xfonts-intl-.* \
            ttf-kochi-gothic ttf-kochi-mincho \
            xfonts-bolkhov-75dpi xfonts-cronyx-100dpi xfonts-cronyx-75dpi

#### Using lilypond python libraries

If you want to use lilypond’s python libraries (either running certain build scripts manually, or using them in other programs), set `PYTHONPATH` to ‘`python/out`’ in your build directory, or ‘`.../usr/lib/lilypond/current/python`’ in the installation directory structure.

#### LilyPond — Contributor’s Guide