From: Eli Zaretskii <eliz@gnu.org>
To: Christoph Buck <christoph.buck@smartoptics.de>
Cc: guile-devel@gnu.org
Subject: Re: Compiling guile-2.2.4 for mingw
Date: Tue, 20 Nov 2018 19:10:53 +0200 [thread overview]
Message-ID: <83k1l7isiq.fsf@gnu.org> (raw)
In-Reply-To: <xxt7eh7lt1e.fsf@smartoptics.de> (message from Christoph Buck on Tue, 20 Nov 2018 15:31:25 +0100)
> From: Christoph Buck <christoph.buck@smartoptics.de>
> Date: Tue, 20 Nov 2018 15:31:25 +0100
>
> > ice-9/boot-9.scm:752:25: In procedure dispatch-exception:
> > In procedure bytevector-u64-set!: Value out of range: -149659645
> > make[2]: *** [Makefile:1931: ice-9/eval.go] Error 1
> > make[2]: Leaving directory '/home/Christoph.Buck/guile-2.2.4/bootstrap'
> > make[1]: *** [Makefile:1857: all-recursive] Error 1
> > make[1]: Leaving directory '/home/Christoph.Buck/guile-2.2.4'
> > make: *** [Makefile:1743: all] Error 2
>
> I have no idea what might be wrong here or how to fix this problem. Does
> anbody have an idea?
I have a guess: bytevector-u64-set! uses GMP functions to store a
64-bit value, but GMP doesn't yet support that on Windows, because it
thinks it can get away with the 'long' type for that, and 'long' is a
32-bit type on Windows, even in 64-bit builds.
I would suggest first to build a 32-bit Guile against a 32-bit GMP.
If that fails in the same way, then my guess is wrong ;-)
next prev parent reply other threads:[~2018-11-20 17:10 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-20 14:31 Compiling guile-2.2.4 for mingw Christoph Buck
2018-11-20 15:39 ` tomas
2018-11-20 15:59 ` Mike Gran
2018-11-20 17:16 ` Christoph Buck
2018-11-20 17:45 ` Mike Gran
2018-11-20 20:27 ` Mark H Weaver
2018-11-20 17:10 ` Eli Zaretskii [this message]
2018-11-20 17:53 ` Jan Nieuwenhuizen
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=83k1l7isiq.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=christoph.buck@smartoptics.de \
--cc=guile-devel@gnu.org \
/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).