all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: "Bruno Félix Rezende Ribeiro" <oitofelix@gnu.org>
Cc: 19056@debbugs.gnu.org
Subject: bug#19056: Guix 0.7 fails to build in Debian Wheezy mipsel
Date: Sat, 15 Nov 2014 19:02:04 +0100	[thread overview]
Message-ID: <87d28ol4v7.fsf@gnu.org> (raw)
In-Reply-To: <20141115004122.7c5f81cf@freedom-laptop> ("Bruno Félix Rezende Ribeiro"'s message of "Sat, 15 Nov 2014 00:41:22 -0200")

Bruno Félix Rezende Ribeiro <oitofelix@gnu.org> skribis:

> This machine is a Lemote Yeeloong 8101B (Loongson 2F processor --
> MIPS64), running Debian Wheezy mipsel port.
>
> Building Guix 0.7 on it fails with the following error:
>
>   ice-9/boot-9.scm:106:20: In procedure make_objcode_from_file: 
>     bad header on object file: "GOOF----LE-8-2.0"
>
> Configuration and build logs are attached (config.log and make.log,
> respectively).
>
> This bug seems to be related to a bug reported by Andreas:
>
> http://lists.gnu.org/archive/html/bug-guix/2013-02/msg00192.html 
>
> Shouldn't it have been fixed by now?

This was fixed in Guile commit cc2948a, which appeared in Guile 2.0.9
(April 2013).

I’m reluctant to adding a workaround for it in Guix because it’s already
been fixed in pretty old Guile versions (although we still support as
old as 2.0.5.)

Thus, for now, I’d recommend either upgrading Guile, or removing
--target= in Guix’s Makefile.am.

Does that work for you?

Thanks,
Ludo’.

  reply	other threads:[~2014-11-15 18:03 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-15  2:41 bug#19056: Guix 0.7 fails to build in Debian Wheezy mipsel Bruno Félix Rezende Ribeiro
2014-11-15 18:02 ` Ludovic Courtès [this message]
2014-11-18  9:40   ` Bruno Félix Rezende Ribeiro
2014-11-18 10:39     ` 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=87d28ol4v7.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=19056@debbugs.gnu.org \
    --cc=oitofelix@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.