Le 28/06/2022 à 16:41, Thomas Thiriez via General Guile related 
discussions a écrit :
>
> Jean Abou Samra <jean@abou-samra.fr> writes:
>
>> Le 27/06/2022 à 15:56, Thomas Thiriez via General Guile related
>> discussions a écrit :
> [...]
>>> (* 999 999 999) -> -76738825
> [...]
>>
>> We had exactly the same problem at LilyPond, and this was the fix:
>>
>> https://gitlab.com/lilypond/lilypond/-/blob/master/release/binaries/lib/dependencies.py#L721 
>>
>>
>> Namely, you need to patch libguile/conv-integer.i.c and
>> conv-uinteger.i.c to replace "SIZEOF_TYPE < SIZEOF_SCM_T_BITS"
>> with "SIZEOF_TYPE < SIZEOF_LONG".
>>
>> HTH,
>> Jean
>
> Thanks for the info. I have tried this, but it doesn't appear to be 
> helping.
>
> I did a few tests with lilypond, and here is what I found. I have a 
> test.scm file containing:
>
> (display (* 999)) (newline)
> (display (* 999 999)) (newline)
> (display (* 999 999 999)) (newline)
>
> lilypond.exe -e '(load \"test.scm\")' test.ly
> GNU LilyPond 2.23.10 (running Guile 2.2)
> 999
> 998001
> 997002999
>
> That is fine. Now, if I try compiling test.scm to test.go, I get:
>
> lilypond.exe -e '(use-modules (system base compile))(compile-file 
> \"test.scm\" #:output-file \"test.go\")' test.ly
> GNU LilyPond 2.23.10 (running Guile 2.2)
> ice-9/boot-9.scm:752:25: In procedure dispatch-exception:
> In procedure bytevector-u64-set!: Value out of range: -149659645
>
> That doesn't work, so I compile test.scm to test.go with guile on my 
> Mac. If I then try loading the generated test.go with lilypond, I get:
>
> lilypond.exe -e '(load \"test.go\")' test.ly
> GNU LilyPond 2.23.10 (running Guile 2.2)
> 999
> 998001
> -76738825
>
> Now, it is possible that the problem is that I am trying to run a .go 
> file compiled on macOS on a Windows machine, and that the two 
> platforms are different enough that the .go file can't be reused. And 
> because I get that "Value out of range" error when compiling on 
> Windows, I am probably stuck with .scm files instead of compiled .go 
> files.


This bug is now hitting us too, we're investigating it here:

https://gitlab.com/lilypond/lilypond/-/issues/6474

Best,
Jean