Comment #3 on issue 1933 by tdaniels...@googlemail.com: Lilypond-book requires msvcrt again
http://code.google.com/p/lilypond/issues/detail?id=1933
The problem seems to arise (as before) from the use of the subprocess module in the minGW build. It looks like Janneke patched GUB to support the subprocess module in minGW here: http://github.com/janneke/gub/commit/e3d46689d881045ceb2dbf31d7d4573709f781d8#L1R136 This seems to include the msvcrt module in minGW builds, but I confess I don't really understand this patch. Maybe this patch isn't working? Certainly msvcrt is not included in the python libs, but subprocess is. This is a broken combination as the first thing the subprocess module does is: if mswindows: import threading import msvcrt. so I believe this is a GUB build error (but still Critical). A bypass (as used to fix earlier msvcrt problems) is avoid the use of subprocess, but really we need to solve the basic GUB problem this time. Trevor _______________________________________________ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
