lilypond-devel
[Top][All Lists]
Advanced

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

Re: Make doc error 2.13.10


From: Colin Campbell
Subject: Re: Make doc error 2.13.10
Date: Tue, 22 Dec 2009 21:13:16 -0700
User-agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.0.10) Gecko/20070403 Thunderbird/1.5.0.10 Mnenhy/0.7.4.0

David Kastrup wrote:
Graham Percival <address@hidden> writes:

On Mon, Dec 21, 2009 at 4:18 PM, Trevor Daniels <address@hidden> wrote:
Colin Campbell wrote Monday, December 21, 2009 3:33 PM
After building LP 2.13.10 from git, I wanted an HTML copy of the docs, so
I cd to /Documentation and did make doc. The result was a segfault:
Try make doc in the directory above /Documentation,
whatever you chose to call it.
That shouldn't matter; I've make doc 'd in many directories before
doing it in the topdir.

I'm trying a full rebuild now; I'm getting some errors, but I'm not
certain if they're just the expected random errors from using
CPU_COUNT, or whether they're more serious.  I'll report back in a
while.

Nicolas integrated my define-markup-command patches recently.  Previous
versions had reported memory problems which I could not reproduce, but
tried to fix nevertheless, and the revised version was reported not to
have the same problems.

The commit would be bfbb8f784d69034c1ed351f6a00173338ee9aa04.  It might
be worth checking if reverting this particular commit cures the problem
for the original poster.

If yes, his g++ and guile versions would be important to know, and other
platform details.

If no, so much the better.  For me, I mean.


I've managed to build the docs (very much like the look of the web page,
too!). Pulling in yesterday's patch didn't seem to fix it, but
installing a boatload ( metric: shed-load) of texlive-fonts* seems to
have done it. It appears that apt-get build-dep lilypond doesn't depend
those font packages. At any rate, on to the first term test!

Colin
--
A good juggler can always find work.
 - attributed to L. Pacioli (1445 - 1517)






reply via email to

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