Error in building documentation

classic Classic list List threaded Threaded
27 messages Options
12
Reply | Threaded
Open this post in threaded view
|

Re: Error in building documentation

David Kastrup
Walter Garcia-Fontes <[hidden email]> writes:

> * Federico Bruni, [hidden email] [26/02/16 14:36]:
>> I guess that you should try running out/bin/lilypond on the following files
>> and see what happens:
>>
>> fatal error: failed files: "55/lily-c61e089a.ly 16/lily-fb4bd50d.ly
>> 1b/lily-703d6aa3.ly c0/lily-c236818d.ly"
>>
>> Anyway, IIUC this is a problem specific of Ubuntu, right?
>> In that case, I'm afraid I cannot help.
>> LilyDev is not an option for you?
>
> Thanks, I tried it and these files compile all fine from the command
> line with lilypond. I think in any case the script is failing in
> converting the eps file to pdf with ghostscript, but when I try this
> from the command line, it also finishes fine. So I'm really puzzled.
>
> I may setup a virtual machine, but I prefer to have my development
> environment in my main computer, and up to recently I never had
> problems in building my own development environment, it only started
> failing in this last version of Ubuntu.

Do you have xetex binaries?  There has been a recent change (though I
don't know whether it has already been committed) making lilypond-book
rely on XeTeX by default.  There have also been recent changes with
regard to the default fonts to use (TeX Gyre).

--
David Kastrup


Reply | Threaded
Open this post in threaded view
|

Re: Error in building documentation

Walter Garcia-Fontes
* David Kastrup, [hidden email] [26/02/16 15:28]:

> Walter Garcia-Fontes <[hidden email]> writes:
> > Thanks, I tried it and these files compile all fine from the command
> > line with lilypond. I think in any case the script is failing in
> > converting the eps file to pdf with ghostscript, but when I try this
> > from the command line, it also finishes fine. So I'm really puzzled.
> >
> > I may setup a virtual machine, but I prefer to have my development
> > environment in my main computer, and up to recently I never had
> > problems in building my own development environment, it only started
> > failing in this last version of Ubuntu.
>
> Do you have xetex binaries?  There has been a recent change (though I
> don't know whether it has already been committed) making lilypond-book
> rely on XeTeX by default.  There have also been recent changes with
> regard to the default fonts to use (TeX Gyre).

Yes, it looks like I have them, I have texlive-full, and I can run
xetex and xelatex from the command line. I also checked and I have the
tex-gyre package installed.

--
Walter Garcia-Fontes




Reply | Threaded
Open this post in threaded view
|

Re: Error in building documentation

David Kastrup
Walter Garcia-Fontes <[hidden email]> writes:

> * David Kastrup, [hidden email] [26/02/16 15:28]:
>
>> Do you have xetex binaries?  There has been a recent change (though I
>> don't know whether it has already been committed) making lilypond-book
>> rely on XeTeX by default.  There have also been recent changes with
>> regard to the default fonts to use (TeX Gyre).
>
> Yes, it looks like I have them, I have texlive-full, and I can run
> xetex and xelatex from the command line. I also checked and I have the
> tex-gyre package installed.

Well, it was worth a try.

--
David Kastrup


Reply | Threaded
Open this post in threaded view
|

Re: Error in building documentation

David Kastrup
In reply to this post by Walter Garcia-Fontes
Walter Garcia-Fontes <[hidden email]> writes:

> I'm still struggling to compile the documentation. My repository is in
> Ubuntu 15.10, so maybe there are some updated libraries or fonts
> causing this, but I still haven't been able to figure out what is
> causing the compilation to abort. It stops at building snippets, the
> last lines of the log show:
>
> -- log --
>
> Processing `./55/lily-c61e089a.ly'
> Parsing...
> Renaming input to:
> `/home/user/sources/lilypond/input/regression/typography-demo.ly'
> Interpreting music...[8]
> Preprocessing graphical objects...
> Interpreting music...
> MIDI output to `./55/lily-c61e089a.midi'...
> Finding the ideal number of pages...
> Fitting music on 1 page...
> Drawing systems...
> Writing header field `texidoc' to `./55/lily-c61e089a.texidoc'...
> Layout output to `./55/lily-c61e089a.eps'...
> Converting to `./55/lily-c61e089a.pdf'...
> warning: `(gs -q -dNOSAFER -dEPSCrop -dCompatibilityLevel=1.4
> -dNOPAUSE -dBATCH -r1200 -sDEVICE=pdfwrite
> -sOutputFile=./55/lily-c61e089a.pdf -c.setpdfwrite
> -f./55/lily-c61e089a.eps)' failed (256)
>  
> fatal error: failed files: "55/lily-c61e089a.ly 16/lily-fb4bd50d.ly
> 1b/lily-703d6aa3.ly c0/lily-c236818d.ly"

typography-demo.ly contains UTF-8 characters (which should mainly be a
problem with guile-2.0-dev instead of guile-1.8-dev however, and that
should not even configure without complaining).  Can you check the other
failure candidates by looking inside of them and checking their
\sourcefilename declaration for the original file name?  Maybe there is
a common problem with the respective files.

--
David Kastrup


Reply | Threaded
Open this post in threaded view
|

Re: Error in building documentation

Walter Garcia-Fontes
* David Kastrup, [hidden email] [26/02/16 15:42]:

> > warning: `(gs -q -dNOSAFER -dEPSCrop -dCompatibilityLevel=1.4
> > -dNOPAUSE -dBATCH -r1200 -sDEVICE=pdfwrite
> > -sOutputFile=./55/lily-c61e089a.pdf -c.setpdfwrite
> > -f./55/lily-c61e089a.eps)' failed (256)
> >  
> > fatal error: failed files: "55/lily-c61e089a.ly 16/lily-fb4bd50d.ly
> > 1b/lily-703d6aa3.ly c0/lily-c236818d.ly"
>
> typography-demo.ly contains UTF-8 characters (which should mainly be a
> problem with guile-2.0-dev instead of guile-1.8-dev however, and that
> should not even configure without complaining).  Can you check the other
> failure candidates by looking inside of them and checking their
> \sourcefilename declaration for the original file name?  Maybe there is
> a common problem with the respective files.

Thanks, I will keep looking. Just in case there is anything strange:

$ dpkg -l guile*
Desired=Unknown/Install/Remove/Purge/Hold
|
Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name           Version      Architecture Description
+++-==============-============-============-=================================
un  guile          <none>       <none>       (no description available)
un  guile-1.6      <none>       <none>       (no description available)
ii  guile-1.8      1.8.8+1-10ub amd64        GNU extension language and Scheme
ii  guile-1.8-dev  1.8.8+1-10ub amd64        Development files for Guile 1.8
un  guile-1.8-doc  <none>       <none>       (no description available)
ii  guile-1.8-libs 1.8.8+1-10ub amd64        Core Guile libraries
un  guile-1.8-slib <none>       <none>       (no description available)
rc  guile-2.0      2.0.11+1-9ub amd64        GNU extension language and Scheme
un  guile-2.0-doc  <none>       <none>       (no description available)
ii  guile-2.0-libs 2.0.11+1-9ub amd64        Core Guile libraries
un  guile-2.0-slib <none>       <none>       (no description available)
un  guile1.4       <none>       <none>       (no description available)


--
Walter Garcia-Fontes


Reply | Threaded
Open this post in threaded view
|

Re: Error in building documentation

Walter Garcia-Fontes
In reply to this post by David Kastrup
> Walter Garcia-Fontes <[hidden email]> writes:
>
> > I'm still struggling to compile the documentation. My repository is in
> > Ubuntu 15.10, so maybe there are some updated libraries or fonts
> > causing this, but I still haven't been able to figure out what is
> > causing the compilation to abort. It stops at building snippets, the
> > last lines of the log show:
> >
> > -- log  deleted --

Well, I gave up and installed LilyDev in a Virtualbox, and put this
virtual machine to be accessible to synchronize with my non-virtual
systems, so that I can work in my laptop and desktop and compile in
the Virtualbox.

--
Walter Garcia-Fontes




Reply | Threaded
Open this post in threaded view
|

Re: Error in building documentation

Walter Garcia-Fontes
In reply to this post by David Kastrup
* David Kastrup, [hidden email] [26/02/16 15:42]:

> Walter Garcia-Fontes <[hidden email]> writes:
>
> > I'm still struggling to compile the documentation. My repository is in
> > Ubuntu 15.10, so maybe there are some updated libraries or fonts
> > causing this, but I still haven't been able to figure out what is
> > causing the compilation to abort. It stops at building snippets, the
> > last lines of the log show:
> >
> > -- log --
> >
> > Processing `./55/lily-c61e089a.ly'
> > Parsing...

I've been following the thread on compiling documentation in the
development list, and it looks like this is the same problem I've had
for the last two versions of Ubuntu (I can compile documentation in
lilydev, at least I could the last time I tried, two or three weeks
ago, using the translation branch):

* Thomas Morley, [hidden email] [29/05/16 01:15]:

> 2016-05-28 12:27 GMT+02:00 Thomas Morley <[hidden email]>:
>
> >
> > FWIW, I checked out staging with your recent patch, i.e.:
> > $ git log
> > commit 193369dddc8adc492d3d98b6f1d00de11a31e9c4
> > Author: David Kastrup <[hidden email]>
> > Date:   Fri May 27 10:20:18 2016 +0200
> >
> >     Issue 4863: Protect Grob_interface<>::interface_symbol_
> > [...]
> >
> > On my host system Ubuntu 16.04 64-bit
> > make doc
> > fails with orchestra.ly as before
>
> Always worth double checking ...
>
> It wasn't orchestra.ly, but another file, which turned out to be a
> snippet used only in Documentation/ja/learning/tutorial.itely
> lily-6fc21da7.ly
>
> It basically contains:
>
> \relative {
>   c''4-\markup { \bold \huge { ここをクリックしてください } }
> }
>
> Trying to compile it alone gave me a gs-error, which reminded me at
> http://lilypond.1069038.n5.nabble.com/Ghostscript-crashes-on-Japanese-characters-on-Ubuntu-16-04-tt190959.html
>
> So I removed noto and did
> sudo apt-get install fonts-ipafont-mincho



--
Walter Garcia-Fontes
L'Hospitalet de Llobregat


12