lilypond-user
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

spectacular ly2dvi failure


From: Chris Lipe
Subject: spectacular ly2dvi failure
Date: Sat, 04 May 2002 03:28:46 -0400
User-agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:0.9.4) Gecko/20011126 Netscape6/6.2.1

Hello,

I am running Red Hat Linux 7.2, and lilypond version 1.4.11-1. I'm trying to compile a moderately large piece (75 measures of full band score), and I get the following error when invoking ly2dvi:

Analyzing default.tex...
Running LaTeX...
error: latex: command exited with value 256
Traceback (innermost last):
 File "/usr/bin/ly2dvi", line 850, in ?
   run_latex (files, outbase, extra_init)
 File "/usr/bin/ly2dvi", line 626, in run_latex
   system (cmd)
 File "/usr/bin/ly2dvi", line 234, in system
   error (msg)
 File "/usr/bin/ly2dvi", line 132, in error
   raise _ ("Exiting ... ")
Exiting ...
I get a .tex file out of this, but it's never more than the first four or five 
pages or so of the score.  I can compile the woodwinds, the saxes, and the 
brass all separately, and they work beautifully, giving me the entire .ps file 
I want, but when I try to compile the whole score at once, it goes splat.  I 
still get a .tex file, but if I try to turn that into a .dvi, I get only three, 
somtimes four pages of the score.

If I try invoking lilypond instead of ly2dvi, I get a .tex file without too 
much complaint, but when I run tex on that to get a dvi file, I get the 
following output:

This is TeX, Version 3.14159 (Web2C 7.3.1)
(default.tex (/usr/share/lilypond/tex/lilyponddefs.tex
(/usr/share/lilypond/tex/feta20.tex)
(/usr/share/lilypond/tex/lilypond-plaintex.tex LilyPond Plain TeX settings)
(/usr/share/lilypond/tex/lily-ps-defs.tex) [footer empty])
Underfull \vbox (badness 10000) has occurred while \output is active [1]
Underfull \vbox (badness 10000) has occurred while \output is active [2]
Underfull \vbox (badness 10000) has occurred while \output is active [3]
Underfull \vbox (badness 10000) has occurred while \output is active [4]
Underfull \vbox (badness 10000) has occurred while \output is active [5]
Underfull \vbox (badness 10000) has occurred while \output is active [6]
Underfull \vbox (badness 10000) has occurred while \output is active [7]
Underfull \vbox (badness 10000) has occurred while \output is active [8]
Underfull \vbox (badness 10000) has occurred while \output is active [9]
! TeX capacity exceeded, sorry [main memory size=350001].
\botalign #1->\vbox to 0pt{\vss #1}
l.82057 }
           %
Output written on default.dvi (9 pages, 507964 bytes).
Transcript written on default.log.

Here I have 9 pages of the score, but that's still a couple pages short (it's 
about 12 pages long).

There are a handful of warnings I get when compiling either way, but there's nothing that's fatal; mostly "putting slur over rest", or some inexplicable complaints about beaming. Something very odd about this: if I compile the entire score with ly2dvi, it finds a whole bunch of failed bar checks (which I can't verify by looking at the score, because it inevitably stops right before the measure in question), but compiling smaller parts of the score with ly2dvi (either the last 3/4 of the score, full band, or the whole score, one section at a time), or the entire score with lilypond, there are no failed bar checks.
I'm not sure what's going on here, and I really can't get enough output out of 
ly2dvi to figure it out.  Both the .ly file involved and the log of error 
messages are rather lengthy; I can provide them if necessary.  Does anyone have 
any ideas to help me out?  Thanks.

Chris Lipe



--
NOTICE:  I have a new personal email address.  It is: address@hidden  Please 
spell krzysztof as in Penderecki.

                                                Chris Lipe
                                                address@hidden
Yeah, the theater was crowded, and yeah, there was clearly a fire, but I sat quietly and watched that movie. After all, rules are rules.

  -- Mark Niebuhr

My girlfriend is more of a left outer join, but I'm more of a right inner join kind 
of guy.  Sure, you may not think it's funny, but if you'd ever used SQL Server, 
you'd be soiling your pants laughing by now."

 -- Mark Niebuhr











reply via email to

[Prev in Thread] Current Thread [Next in Thread]