From: ludo@gnu.org (Ludovic Courtès)
To: Andreas Enge <andreas@enge.fr>
Cc: bug-guix@gnu.org
Subject: Re: mips64el: guild problem
Date: Tue, 19 Feb 2013 14:35:51 +0100 [thread overview]
Message-ID: <87txp81l54.fsf@gnu.org> (raw)
In-Reply-To: <201302191347.06520.andreas@enge.fr> (Andreas Enge's message of "Tue, 19 Feb 2013 13:47:06 +0100")
Andreas Enge <andreas@enge.fr> skribis:
> Am Montag, 18. Februar 2013 schrieb Ludovic Courtès:
>> This “GOOF” cookie indicates the Guile Object Object(!) Format. Here,
>> it says little endian with 8-byte pointers. That corresponds to this
>> GNU triplet:
>> However, my guess is that Guile was compiled with the N32 ABI, so it
>> expects 4-byte words. But Guile’s system/base/target.scm makes this
>> wrong assumption that “mips64” means 8-byte pointers:
>
> That sounds like the good diagnostic. Should guile not explicitly test the
> size of the types, using the C sizeof or equivalent? From the triplet, one
> cannot deduce the ABI.
Right, unless using triplet extensions as done on ARM and in Debian,
<http://wiki.debian.org/Multiarch/Tuples> (I think it’s the way to go.)
> Compiling worked so far. Now there is the hash mismatch in
> http://alpha.gnu.org/gnu/guix/bootstrap/mips64el-
> linux/20130105/guile-2.0.7.tar.xz .
It’s just that build-aux/download.scm got a 404 while trying to download
it, because it’s not on gnu.org.
Until it’s on gnu.org, the fix is to manually download it from
<http://www.fdn.fr/~lcourtes/software/guix/packages/mips64el-linux/20130105/guile-2.0.7.tar.xz>.
Thanks,
Ludo’.
prev parent reply other threads:[~2013-02-19 13:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-18 18:32 mips64el: guild problem Andreas Enge
2013-02-18 22:28 ` Ludovic Courtès
2013-02-19 12:47 ` Andreas Enge
2013-02-19 13:01 ` Nikita Karetnikov
2013-02-19 13:35 ` Ludovic Courtès [this message]
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://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87txp81l54.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=andreas@enge.fr \
--cc=bug-guix@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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
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).