lilypond-devel
[Top][All Lists]
Advanced

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

Re: Problem with Ubuntu Raring Ringtail?


From: David Kastrup
Subject: Re: Problem with Ubuntu Raring Ringtail?
Date: Mon, 27 May 2013 11:44:11 +0200
User-agent: Gnus/5.13 (Gnus v5.13) Emacs/24.3.50 (gnu/linux)

Jan Nieuwenhuizen <address@hidden> writes:

> David Kastrup writes:
>
>> James <address@hidden> writes:
>> Not all that much.  I was talking about the situation you have in Raring
>> Ringtail after
>>
>> sudo apt-get install lilypond
>
> I can do that for you, See below.
> HTH,
> Jan
>
>     $ LANG= /usr/bin/lilypond -dpreview input/regression/toc.ly
>     GNU LilyPond 2.16.0
>     Processing `input/regression/toc.ly'
>     Parsing...
>     Interpreting music...
>     Preprocessing graphical objects...
>     Interpreting music...
>     Preprocessing graphical objects...
>     Finding the ideal number of pages...
>     Fitting music on 3 or 4 pages...
>     Drawing systems...
>     Layout output to `toc.ps'...
>     Converting to `./toc.pdf'...
>     Layout output to `toc.preview.eps'...
>     Converting to `./toc.preview.pdf'...
>     Converting to PNG...
>     Success: compilation successfully completed
>     11:32:31 address@hidden:~/vc/lilypond
>     $ LANG= dpkg -l ghostscript
>     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
>     
> +++-==============-============-============-=================================
>     ii  ghostscript    9.07~dfsg2-0 amd64        interpreter for the 
> PostScript la
>     11:32:34 address@hidden:~/vc/lilypond
>     $ git log input/regression/toc.ly | head
>     commit 26a079ca2393d053315ef8dbef626c897dc9645a
>     Author: David Kastrup <address@hidden>
>     Date:   Fri Aug 24 11:01:43 2012 +0200

Ok, that's one data point for "amd64" architecture.  Which is one
consolation.

I am using the i386 package myself, and uname -i returns i686 (probably
mostly relevant regarding kernel and libc6).  So anybody else who could
also check the situation regarding 32bit systems?

-- 
David Kastrup



reply via email to

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