My guess would be that you have a 64-bit binary version of a utility package that is also used (and installed) as a 32bit library by lilypond apearing before Lilypond on the system path.
I've seen other products running into access violations like you mentioned due to a 64-bit binary trying to use a 32-bit library. I can imagine the same holds the other way around (32bit binaries like Lilypond trying to use a 64bit library). If that's indeed the issue you may be able to resolve it by putting Lilypond binaries at the start of your system path. Hans Aikema > Op 1 nov. 2015 om 19:59 heeft guoguocuozuoduo <[email protected]> het > volgende geschreven: > > Yes, I have reinstalled several times already, but the problem still appears. > > 发自我的 iPad > >>> 在 2015年11月1日，下午11:18，Nick Payne <[email protected]> 写道： >>> >>> On 01/11/2015 18:02, Brian Guo wrote: >>> Hi, >>> >>> I have just installed LilyPond version 2.19.30 on a Windows 10 (64 bit) >>> laptop, b >>> laptop, but when I try to compile a simple score, such as: >>> \version "2.19.30" >>> \score { >>> \new Staff \relative c' { >>> c >>> } >>> } >> >> Have you tried an uninstall/reinstall of 2.19.30? Your example builds >> without any problem on my laptop, which is running same OS and same version >> of Lilypond. The 2.19.30 install exe I downloaded is 30,178,860 bytes. There >> don't seem to be any checksums provided to verify the downloads. >> >> Nick >> >> _______________________________________________ >> lilypond-user mailing list >> [email protected] >> https://lists.gnu.org/mailman/listinfo/lilypond-user > _______________________________________________ > lilypond-user mailing list > [email protected] > https://lists.gnu.org/mailman/listinfo/lilypond-user _______________________________________________ lilypond-user mailing list [email protected] https://lists.gnu.org/mailman/listinfo/lilypond-user
