From: mkohlhaas <mkohlhaas@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: New Package: scryer-prolog-0.8.123
Date: Mon, 27 Jul 2020 05:33:09 +0200 [thread overview]
Message-ID: <20200727033309.OZc7EW9J2CCaNsJ6P0Tm4NGsaXbvIM7kkRw4rxJ1DlE@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-23821@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 842 bytes --]
New comment by mkohlhaas on void-packages repository
https://github.com/void-linux/void-packages/pull/23821#issuecomment-664100870
Comment:
Scryer Prolog uses the [GNU Multiple Precision Arithmetic Library GMP](https://gmplib.org/) as part of the FFI Rust library [gmp-mpfr-sys](https://crates.io/crates/gmp-mpfr-sys). When cross-compiling for i686 the configure script gets confusing information about the platform. It can't really figure out if it is 32 or 64 bit:
```
using ABI="64"
...
configure: error: Oops, mp_limb_t is 32 bits, but the assembler code in this configuration expects 64 bits.
```
I think one could solve the issue by specifying:
`configure ABI=32`
according to the [GMP documentation](https://gmplib.org/manual/ABI-and-ISA#ABI-and-ISA).
But how would this be possible with a build type of `cargo`?
next prev parent reply other threads:[~2020-07-27 3:33 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-24 22:14 [PR PATCH] " mkohlhaas
2020-07-24 23:18 ` [PR PATCH] [Updated] " mkohlhaas
2020-07-24 23:20 ` mkohlhaas
2020-07-25 8:02 ` Chocimier
2020-07-25 8:15 ` [PR PATCH] [Updated] " mkohlhaas
2020-07-25 8:18 ` mkohlhaas
2020-07-25 12:00 ` mkohlhaas
2020-07-25 12:51 ` mkohlhaas
2020-07-26 23:20 ` mkohlhaas
2020-07-26 23:21 ` mkohlhaas
2020-07-27 1:34 ` mkohlhaas
2020-07-27 2:09 ` mkohlhaas
2020-07-27 2:32 ` mkohlhaas
2020-07-27 3:21 ` mkohlhaas
2020-07-27 3:33 ` mkohlhaas [this message]
2020-07-27 5:57 ` mkohlhaas
2020-07-27 6:15 ` mkohlhaas
2020-07-27 6:44 ` mkohlhaas
2020-07-27 10:59 ` mkohlhaas
2020-07-27 11:21 ` mkohlhaas
2020-07-27 12:05 ` mkohlhaas
2020-07-27 13:46 ` mkohlhaas
2020-07-27 14:26 ` mkohlhaas
2020-07-27 14:29 ` mkohlhaas
2020-07-27 14:38 ` mkohlhaas
2020-07-27 15:38 ` [PR PATCH] [Updated] " mkohlhaas
2020-07-27 15:45 ` mkohlhaas
2020-07-27 16:53 ` mkohlhaas
2020-07-27 16:56 ` mkohlhaas
2020-07-27 17:40 ` Chocimier
2020-07-27 17:42 ` Chocimier
2020-07-27 17:46 ` Chocimier
2020-07-27 18:42 ` [PR PATCH] [Updated] " mkohlhaas
2020-07-27 20:10 ` mkohlhaas
2020-07-28 18:48 ` [PR PATCH] [Updated] " Chocimier
2020-07-28 18:50 ` Chocimier
2020-07-28 18:50 ` [PR PATCH] [Merged]: " Chocimier
2020-07-28 18:53 ` mkohlhaas
2020-07-28 18:54 ` Chocimier
2020-07-28 18:59 ` triska
2020-07-28 22:43 ` Johnnynator
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200727033309.OZc7EW9J2CCaNsJ6P0Tm4NGsaXbvIM7kkRw4rxJ1DlE@z \
--to=mkohlhaas@users.noreply.github.com \
--cc=ml@inbox.vuxu.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 NNTP newsgroup(s).