cygwin-2.6.0 bug reports wanted

[Jan Nieuwenhuizen]

Jan Nieuwenhuizen writes:

[moved from -devel]

Hi there,

You all reported the same error for Bertalan's Cygwin test version of
lilypond-2.6.0

    http://lists.gnu.org/archive/html/lilypond-user/2005-07/msg00181.html

I just checked, and it works for me.

We do still not have a useful bug report or fix.  It would be great if
you could check scm/framework-ps.scm, and see where/why the function
(munge-lily-font-name) messes up in your installation.

Alternatively, we need the output of a verbose lilypond run, cygcheck,
fc-list, and lilypond again:

   lilypond --verbose /usr/share/lilypond-2.6.0/input/simple-song.ly > lily.log 
2>&1
   cygcheck -sv >> bug 2>&1
   echo 
'<fontconfig><dir>/usr/share/lilypond/2.6.0/fonts/type1</dir></fontconfig>' > 
~/.fonts.conf
   fc-list >> bug 2>&1
   lilypond --verbose /usr/share/lilypond-2.6.0/input/simple-song.ly >> 
lily.log 2>&1
   gzip lily.log

It would be nice if one of you would send lily.log.gz here.  We cannot
release 2.6.0 for cygwin until this is fixed.

For instructions of how to install the test version, see:

     http://lists.gnu.org/archive/html/lilypond-user/2005-07/msg00131.html

Jan.
 
-- 
Jan Nieuwenhuizen <address@hidden> | GNU LilyPond - The music typesetter
http://www.xs4all.nl/~jantien       | http://www.lilypond.org