lilypond-devel
[Top][All Lists]
Advanced

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

Re: cygwin64 - building 2.18.2 doc fails


From: Marco Atzeri
Subject: Re: cygwin64 - building 2.18.2 doc fails
Date: Mon, 13 Apr 2015 10:44:28 +0200
User-agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.6.0

On 4/12/2015 3:06 PM, Masamichi HOSODA wrote:
On 4/11/2015 2:08 PM, Masamichi HOSODA wrote:


I've tried on my cygwin64 environment.
Maybe environment variable TMP is the cause.
Would you try the attached patch?

The version for 32 bit seems to have other problems.
I see segfaults but I need to rebuild and investigate

How about lilypond-2.19.18?
If I understand correctry,
lilypond-2.19.16 is fixed some issues for newer gcc on 32 bit windows etc.

It seems so.
I built lilypond-2.19.18 (32bit) and passed all "make check" steps.

Attached the patches I am using, to remove the
dos_to_posix CYGWIN specific usage.
Not clear why it was needed in the past, it is not needed
in a pure cygwin enviroment and cygwin_conv_to_posix_path
is deprecated on 32bit and not available on 64bit.


The build also works for

$ lilypond --png -danti-alias-factor=4 lily-487dce2c.ly
GNU LilyPond 2.19.18
Processing `lily-487dce2c.ly'
Parsing...
Renaming input to: `out-www/quantize-start-midi.ly'
Interpreting music...
Preprocessing graphical objects...
Interpreting music...
MIDI output to `lily-487dce2c.midi'...
Calculating line breaks...
Drawing systems...
Layout output to `lily-487dce2c.eps'...
Converting to PNG...
Layout output to `lily-487dce2c-1.eps'...
Writing lily-487dce2c-systems.texi...
Writing lily-487dce2c-systems.tex...
Writing lily-487dce2c-systems.count...
Success: compilation successfully completed

I will update the cygwin package accordingly.
Previous announce was
https://cygwin.com/ml/cygwin-announce/2015-04/msg00011.html

Thanks and Regards
Marco

Attachment: NO-dos_to_posix.patch
Description: Text document

Attachment: NO-dos_to_posix-2.patch
Description: Text document


reply via email to

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