> Just compiled LilyPond 2.5.15 (ChangeLog 1.3261) an hour ago or so. I
> tried 'make web' and it has seemingly frozen at:
>
>
> <lily-51095895-1.eps><lily-659133186-1.eps>] [253<lily-563569828-1.eps>
> <lily-2030054610-1.eps><lily-993345859-1.eps><lily-288871224-1.eps>]
> [254]
> [255] [256] [257] [258] [259] [260] [261] [262] [263] [264] [265] [266]
> [267]
> [268]
> ps2pdf -sPAPERSIZE=a4 out-www/lilypond.pdf.pdfps out-www/lilypond.pdf
>
> It has stopped there for quite some time now. Close to an hour, I
> think. At first I thought it was taking some time to create a large PDF
> file or something, but it has been stuck for so long that I think
> something else is going on (or more to the point *not* going on).
It might be a gs version problem.
I have gs version 7.07.1.
>From Changelog:
2004-12-21 Jan Nieuwenhuizen <[EMAIL PROTECTED]>
* python/lilylib.py (setup_environment): Set GS_FONTPATH, GS_LIB
to empty. Fixes make web, using gs-gpl-8.01. In fact,
gs-afpl-8.50 has more trouble with make web (ie, uses *a lot*
more
resourses; 3x MAXSIZE, 4x MAXRSS, 1.5x user).
* mf/GNUmakefile (pfa_warning): Use less broken check.
* python/lilylib.py (setup_environment): Remove cruft from
GS_FONTPATH.
* configure.in: Bump mftrace requirement to 1.1.1.
I didn't mind not building pdf's for the moment so I did:
# cd /usr/bin
# mv ps2pdf ps2pdf.org
# ln -s /bin/true ps2pdf
And I got past that problem.
>
> Also, I'm still getting the extra large sans serif font for time
> signatures and multimeasure rests (reported last night on bug-lilypond).
>
> I'm no longer getting a seemingly spurious error message about a
> programming error, and some stencil being moved to the edge. It did not
> seem to indicate any visible problem with the output. As I said, I'm
> not getting this error any more.
>
> -David
_______________________________________________
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
