From: Thomas Thiriez via General Guile related discussions <guile-user@gnu.org>
To: guile-user@gnu.org
Subject: Re: 64-bit Guile on Windows
Date: Wed, 29 Jun 2022 11:07:32 +0200 [thread overview]
Message-ID: <m2h743u98d.fsf@twistedwave.com> (raw)
In-Reply-To: <87ilok786t.fsf@web.de>
"Dr. Arne Babenhauserheide" <arne_bab@web.de> writes:
[...]
>> Possibly fixnum-related, so maybe:
>>
>> https://debbugs.gnu.org/cgi/bugreport.cgi?bug=42060
>>
>> Maybe 32-bit <-> 64-bit related, so maybe:
>>
>> https://debbugs.gnu.org/cgi/bugreport.cgi?bug=28920
Thanks a lot. I will check those out.
>> Also, guile@2.2 is not developed anymore AFAICT.
>
> From what I see, Guile 2.2 does still get fixes, but no larger
> changes.
> See
> https://git.savannah.gnu.org/cgit/guile.git/log/?h=stable-2.2
I was able to have something at least partially working with Guile
2.2, but if I could have a working Guile 3 on Windows, that would
be even better!
Regards,
Thomas Thiriez
next prev parent reply other threads:[~2022-06-29 9:07 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
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 [this message]
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=m2h743u98d.fsf@twistedwave.com \
--to=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).