From: Jean Abou Samra <jean@abou-samra.fr>
To: Thomas Thiriez <thomas@twistedwave.com>, guile-user@gnu.org
Subject: Re: 64-bit Guile on Windows
Date: Tue, 28 Jun 2022 10:38:44 +0200 [thread overview]
Message-ID: <adb9c207-777f-5b74-c026-aaa3661cb582@abou-samra.fr> (raw)
In-Reply-To: <m2fsjqus4y.fsf@twistedwave.com>
Le 27/06/2022 à 15:56, Thomas Thiriez via General Guile related
discussions a écrit :
> Hi,
>
> I am currently porting a macOS application to Windows, and need to
> have libguile working.
>
> I can see GnuCash works with Guile. I could borrow their libguile.dll,
> but it is a 32-bit build, and I am making a 64-bit application. I
> tried building Guile 3, but had more success with Guile 2.2, so I will
> keep that version.
>
> I have cross compiled it on my mac with mingw, and it kind of works.
> The only thing is that if I compile my .scm files to .go, then my
> fixnums are not automatically converted to big nums, and I get things
> like that:
>
> (* 999 999 999) -> -76738825
>
> My fix is to keep the .scm files, and avoid compiling to .go.
>
> I believe this has something to do with the fact that, on that
> platform, we have:
>
> sizeof(SCM) == 8
> sizeof(long) == 4
>
> Is there something to do about that problem? Is there something I can
> do to have a working 64-bit Guile on Windows?
>
> Thanks a lot for any help you could provide.
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
next prev parent reply other threads:[~2022-06-28 8:38 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-27 13:56 64-bit Guile on Windows Thomas Thiriez via General Guile related discussions
2022-06-27 17:28 ` Jan Nieuwenhuizen
2022-06-27 19:33 ` Thomas Thiriez via General Guile related discussions
2022-06-28 8:38 ` Jean Abou Samra [this message]
2022-06-28 10:52 ` Maxime Devos
2022-07-06 16:33 ` Jean Abou Samra
2022-06-28 14:41 ` Thomas Thiriez via General Guile related discussions
2022-06-28 15:00 ` Thomas Thiriez via General Guile related discussions
2022-06-28 16:14 ` Maxime Devos
2022-06-28 22:07 ` Dr. Arne Babenhauserheide
2022-06-29 9:07 ` Thomas Thiriez via General Guile related discussions
2022-11-22 12:44 ` Jean Abou Samra
2022-11-22 13:22 ` Mike Gran
2023-03-23 23:14 ` Thomas Thiriez via General Guile related discussions
-- strict thread matches above, loose matches on Subject: below --
2022-11-22 14:32 Jean Abou Samra
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=adb9c207-777f-5b74-c026-aaa3661cb582@abou-samra.fr \
--to=jean@abou-samra.fr \
--cc=guile-user@gnu.org \
--cc=thomas@twistedwave.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).