Re: Fedora issues

[Phil Holmes]

Please remember the "reply all"

I think the problem you have with your complex score and the simple score 
failure are not the same?  I believe the simple issue is to do with GhostScript 
and how it interacts with the installed version in Fedora, although I am not an 
expert in this area.  I also believe Masamichi Hosoda is looking at what could 
be causing it.

Your more complex score might fail on any or no other OSes: without a sample 
that causes the crash, it is never likely to be able to be fixed.

The binaries for LilyPond are built on my 32 bit Ubuntu 14.04 virtual machine.  
They are tested by any of the community that uses LilyPond on whatever 
operating system they have installed.

--
Phil Holmes


  ----- Original Message ----- 
  From: Andrew Bernard 
  To: Phil Holmes 
  Sent: Saturday, May 30, 2015 4:44 PM
  Subject: Re: Fedora issues


  Dear Phil,


  Due to IP constraints and the fact that the score is a contemporary work in 
progress I am not at liberty to release it, unfortunately. I am aware this 
means the issue may never get fixed.


  However, running the following fails on Fedora 22:


  \version “2.19.21”
  { c’ }


  I cannot imagine a simpler snippet. I believe this has been reported. This is 
an even more fundamental issue needing a fix first I’d say. Fedora is not 
looking good at the moment.


  As to my issue, I tried on Fedora 21, 22 and Mint 17 all with the same error 
thrown. I therefore suspect the issue is in the lilypond code for 2.19.21 and 
not OS specific, particularly.


  What Linux is lilypond developed and tested on?


  I have been doing my best with gdb and trying every different release of 
pango, all to no avail so far. Something must have broken between 20 and 21 in 
lilypond.


  Andrew






  On 30 May 2015 at 21:56:37, Phil Holmes (address@hidden) wrote:

  Could you release the score to a developer or two to check other OSes?