From: Eli Zaretskii <eliz@gnu.org>
To: jeremy chen <yngccc@gmail.com>
Cc: guile-user@gnu.org
Subject: Re: Unable to compile Guile
Date: Mon, 10 Nov 2014 12:44:55 +0200 [thread overview]
Message-ID: <83d28vnxlk.fsf@gnu.org> (raw)
In-Reply-To: <CADti_BpxKspNkGpj2ic4HAMS70CUPJ0BSfYQh6kDkH+H6muPvg@mail.gmail.com>
> Date: Sun, 9 Nov 2014 23:30:07 -0500
> From: jeremy chen <yngccc@gmail.com>
>
> Hi, I am trying to compile guile on windows with Mingw-w64.
> The file libguile/numbers.c signal an error in this function:
>
> static SCM
> scm_i_inum2big (scm_t_inum x)
> {
> /* Return a newly created bignum initialized to X. */
> SCM z = make_bignum ();
> #if SIZEOF_VOID_P == SIZEOF_LONG
> mpz_init_set_si (SCM_I_BIG_MPZ (z), x);
> #else
> /* Note that in this case, you'll also have to check all mpz_*_ui and
> mpz_*_si invocations in Guile. */
> #error creation of mpz not implemented for this inum size
> #endif
> return z;
> }
>
> sizeof(void*) is 8 and sizeof(long) is 4 on my machine.
> Anyway to get around this? Thanks.
This is a bug in Guile: it assumes the LP64 data model, where both
'long' and a pointer are 64-bit wide. But 64-bit Windows uses the
LLP64 model, where 'long' is a 32-bit data type, and the 64-bit
integer data type is 'long long' or '__int64'.
You need to fix Guile to support the LLP64 model, at least in this
module, and probably elsewhere as well.
next prev parent reply other threads:[~2014-11-10 10:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-10 4:30 Unable to compile Guile jeremy chen
2014-11-10 10:44 ` Eli Zaretskii [this message]
2014-11-11 16:31 ` Mark H Weaver
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=83d28vnxlk.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=guile-user@gnu.org \
--cc=yngccc@gmail.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).