./configure --prefix=$HOME/usr
@end example
+If you encounter any problems, please see @ref{Problems}.
+
@unnumberedsubsubsec Compiling for multiple platforms
exec /usr/bin/pngtopnm "$@"
@end verbatim
-On Mac OS X, I use this:
+On MacOS X, I use this:
@verbatim
export DYLD_LIBRARY_PATH=/sw/lib
@node Problems
@subsection Problems
-For help and questions use @email{lilypond-user@@gnu.org}. Send bug
-reports to @email{bug-lilypond@@gnu.org}.
+For help and questions use @email{lilypond-user@@gnu.org}. Send
+bug reports to @email{bug-lilypond@@gnu.org}.
Bugs that are not fault of LilyPond are documented here.
@end example
-@unnumberedsubsubsec Compiling on Mac OS X
+@unnumberedsubsubsec Compiling on MacOS@tie{}X
-Here are special instructions for compiling under OS X. These instructions
-assume that dependencies are installed using @uref{http://www.macports.org/, MacPorts.}
-The instructions have been tested using OS X 10.5 (Leopard).
+Here are special instructions for compiling under MacOS@tie{}X.
+These instructions assume that dependencies are installed using
+@uref{http://www.macports.org/, 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
-@code{~/.profile} by default. You should create this file if it does not exist.
+Next, add the following to your relevant shell initialization
+files. This is @code{~/.profile} by default. You should create
+this file if it does not exist.
@example
export PATH=/opt/local/bin:/opt/local/sbin:$PATH
/opt/local/lib:$DYLD_LIBRARY_PATH
@end example
-Now you must edit the generated @code{config.make} file. Change
+Now you must edit the generated @code{config.make} file. Change
@example
FLEXLEXER_FILE = /usr/include/FlexLexer.h
@end example
+@noindent
to:
@example
FLEXLEXER_FILE = /opt/local/include/FlexLexer.h
@end example
-At this point, you should verify that you have the appropriate fonts installed
-with your ghostscript installation. Check @code{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:
+At this point, you should verify that you have the appropriate
+fonts installed with your ghostscript installation. Check @code{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:
@example
-$ 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/
-# Cleanup
-$ rm -rf urw-fonts-1.07pre44
+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
@end example
-Now run the @code{./configure} script. To avoid complications with automatic font
-detection, specify @code{'--with-ncsb-dir=/opt/local/share/ghostscript/fonts'}.
+Now run the @code{./configure} script. To avoid complications with
+automatic font detection, add
+
+@example
+--with-ncsb-dir=/opt/local/share/ghostscript/fonts
+@end example
@unnumberedsubsubsec Solaris