From: ludo@gnu.org (Ludovic Courtès)
To: Andreas Enge <andreas@enge.fr>
Cc: bug-guix@gnu.org
Subject: Re: mips64el: guild problem
Date: Mon, 18 Feb 2013 23:28:39 +0100 [thread overview]
Message-ID: <878v6l45pk.fsf@gnu.org> (raw)
In-Reply-To: <201302181932.28497.andreas@enge.fr> (Andreas Enge's message of "Mon, 18 Feb 2013 19:32:28 +0100")
Andreas Enge <andreas@enge.fr> skribis:
> ice-9/boot-9.scm:106:20: In procedure make_objcode_from_file: bad header on
> object file: "GOOF----LE-8-2.0"
This “GOOF” cookie indicates the Guile Object Object(!) Format. Here,
it says little endian with 8-byte pointers. That corresponds to this
GNU triplet:
--8<---------------cut here---------------start------------->8---
scheme@(system base target)> (with-target "mips64el-unknown-linux-gnu" (lambda () (list (target-endianness) (target-word-size))))
$2 = (little 8)
--8<---------------cut here---------------end--------------->8---
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:
--8<---------------cut here---------------start------------->8---
(define (cpu-word-size cpu)
"Return the word size for CPU."
(if (string=? cpu (triplet-cpu %host-type))
%native-word-size
(cond ((string-match "^i[0-9]86$" cpu) 4)
((string-match "64$" cpu) 8)
((string-match "64[lbe][lbe]$" cpu) 8)
((member cpu '("sparc" "powerpc" "mips" "mipsel")) 4)
((string-match "^arm.*" cpu) 4)
(else (error "unknown CPU word size" cpu)))))
--8<---------------cut here---------------end--------------->8---
For now, you can work around it by removing the --target argument from
Makefile.am.
Can you confirm?
Thanks,
Ludo’.
next prev parent reply other threads:[~2013-02-18 22:28 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 [this message]
2013-02-19 12:47 ` Andreas Enge
2013-02-19 13:01 ` Nikita Karetnikov
2013-02-19 13:35 ` Ludovic Courtès
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=878v6l45pk.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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.