It's alive! It's alive! Which is to say, I have successfully compiled the lilypond trunk (2.13.4) on Mac OS X 10.5.8 (Leopard) x86 Intel.
Thanks for the help, I'll write up a step-by-step of what I did tomorrow and post it. -Travis On Sun, Aug 30, 2009 at 10:40 PM, Travis Briggs<audiod...@gmail.com> wrote: > I used the git command in the INSTALL document > (http://lilypond.org/doc/v2.13/Documentation/topdocs/INSTALL.html#Downloading-source-code) > > git clone git://git.sv.gnu.org/lilypond.git > > In my configure script, I have the following at line 4547: > > if { test -f "$as_dir/$ac_word$ac_exec_ext" && $as_test_x > "$as_dir/$ac_word$ac_exec_ext"; }; then > ac_cv_prog_FCMATCH="fc-match" > $as_echo "$as_me:${as_lineno-$LINENO}: found > $as_dir/$ac_word$ac_exec_ext" >&5 > break 2 > fi > > then, a few more lines down: > > FCMATCH=$ac_cv_prog_FCMATCH > ... > if test "$FCMATCH" != ""; then > for style in Roman Italic "Bold Italic" Bold; do > NCSB_FILE=`$FCMATCH --verbose "Century Schoolbook > L:style=$style:foundry=urw" | grep 'file:' | grep -v "\.ttf"` > > NCSB_FILE=`echo $NCSB_FILE | sed 's/^.*"\(.*\)".*$/\1/g'` > NCSB_FILE=`$PYTHON "$srcdir/scripts/auxiliar/readlink.py" $NCSB_FILE` > NCSB_SOURCE_FILES="$NCSB_FILE $NCSB_SOURCE_FILES" > done > else > > > Also I've run into further issues, since my > /opt/local/share/ghostscript/fonts/ doesn't contain any of the c0590* > files. > I found them on the ghostscript svn server and copied them using the > following commands: > > $ 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/ > > Still working on getting a finished compile done. > > > -Travis > > On Sun, Aug 30, 2009 at 9:13 PM, Patrick McCarty<pnor...@gmail.com> wrote: >> On 2009-08-30, Travis Briggs wrote: >>> Here's an update: >>> >>> I found the following in config.make: >>> NCSB_SOURCE_FILES = /Library/Fonts/Hei.dfont /Library/Fonts/Hei.dfont >>> /Library/Fonts/Hei.dfont /Library/Fonts/Hei.dfont >>> >>> Looks like my fc-match was returning that because it was from >>> foundry=urw. I didn't have the NCSB fonts in a place that lilypond >>> could find. >>> >>> I'm re-compiling now after doing --with-ncsb-dir= >> >> By "compiling trunk", do you mean "compiling from git source" ? >> >> The reason I'm asking is because we are now using "fc-list" instead of >> "fc-match" for finding the correct fonts. But this is only available >> in current git: >> >> http://git.savannah.gnu.org/gitweb/?p=lilypond.git >> >> >> -Patrick >> > _______________________________________________ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel