On 4/16/2015 4:04 PM, Masamichi HOSODA wrote:
64 bit "make doc" on 2.19.18 was completed.
on 32 bit I have still issue but much later for a different issue.
Any idea what could cause python to segfault here
or how to debug it ?
Do you use 64 bit Windows?
Both as I am one the package maintainers.
I need to test both environments.
https://www.cygwin.com/cygwin-pkg-maint
I took over lilypond recently.
About two years ago, I installed cygwin (32 bit) to 64 bit Windows.
It was buggy. Sometimes, fork() was failed.
(32 bit cygwin on 32 bit Windows was fine.)
Forks failure are more likely to happen on 32bit as the
address pool is more limited.
On 64bit are very rare.
So, I use cygwin64 on 64 bit Windows.
Has current 32 bit cygwin been fixed the such problem?
There was some improvement, specially as automatic rebase after install
is now in place. But they are always possible.
https://cygwin.com/faq.html#faq.using.fixing-fork-failures
Anyway, I can assure you that I am familiar with the problem and
it is NOT a fork issue.
Regards
Marco
_______________________________________________
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
