unofficial mirror of guile-user@gnu.org 
 help / color / mirror / Atom feed
From: Mike Gran <spk121@yahoo.com>
To: Jean Abou Samra <jean@abou-samra.fr>
Cc: Thomas Thiriez <thomas@twistedwave.com>, guile-user@gnu.org
Subject: Re: 64-bit Guile on Windows
Date: Tue, 22 Nov 2022 05:22:32 -0800	[thread overview]
Message-ID: <Y3zNGLzI5OHNxDn5@spikycactus.com> (raw)
In-Reply-To: <e8b56da8-62fa-8342-bac6-b9e7274d2a0c@abou-samra.fr>

On Tue, Nov 22, 2022 at 01:44:47PM +0100, Jean Abou Samra wrote:
> 
>> > 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
> 


For what it is worth, I do have functional 64-bit Guile 3.0.x for
Windows at the link below, but that tree is still full of missteps and
experiments and needs to made into a cleaner patchset.  And I'm still
actively hacking there because I'm trying to a Guile that, once
installed, lives in a single directory like most Windows applications
so I can make an MSIX installer. So it is a bit of a mess, but,
I'm fairly confident the integers are fixed.

https://github.com/spk121/guile/commits/wip-mingw-bleh

That tree was based on, and will eventually contribute
back to

https://git.savannah.gnu.org/cgit/guile.git/log/?h=wip-mingw

Both of these trees require that you  --enable-mini-gmp 
--enable-jit=no and --disable-lto at configure time.

Regards,
Mike Gran




  reply	other threads:[~2022-11-22 13:22 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
2022-11-22 12:44     ` Jean Abou Samra
2022-11-22 13:22       ` Mike Gran [this message]
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=Y3zNGLzI5OHNxDn5@spikycactus.com \
    --to=spk121@yahoo.com \
    --cc=guile-user@gnu.org \
    --cc=jean@abou-samra.fr \
    --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).