From: Ricardo Wurmus <rekado@elephly.net>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: 28243@debbugs.gnu.org
Subject: bug#28243: Guix cross-compilation doesn't work
Date: Mon, 09 Oct 2017 23:34:16 +0200 [thread overview]
Message-ID: <87k204m2ef.fsf@elephly.net> (raw)
In-Reply-To: <871snvthbe.fsf@gnu.org>
Hi Manolis,
Ludovic Courtès <ludo@gnu.org> writes:
>> Running `guix build --target=i586-pc-gnu -c8 bootstrap-tarballs' or
>> running `guix build --target=i686-linux-gnu -c8 bootstrap-tarballs'
>> fail with
>>
>> phase `set-paths' succeeded after 0.0 seconds
>> starting phase `install-locale'
>> warning: failed to install 'en_US.utf8' locale: Invalid argument
>> phase `install-locale' succeeded after 0.0 seconds
>> starting phase `unpack'
>> In execvp of tar: No such file or directory
>> phase `unpack' failed after 0.0 seconds
>>
>> http://paste.lisp.org/display/354383
>
> ^ followed by:
>
> builder for `/gnu/store/x3i6zasfc97zrwr4c9lj73mh14x5rdwd-make-boot0-4.2.1.drv' failed with exit code 1
>
> This to me suggests a bug in how grafts are applied in a
> cross-compilation context: we shouldn’t be trying to cross-compile
> ‘make-boot0’ in the first place. I’m pretty sure passing --no-grafts
> avoids the problem (but remember it disables some of the security
> updates!). Can you confirm?
Have you been able to confirm this?
I just wanted to do this on darnassus, but guix-daemon is not running
there, and I cannot seem to get it to build software as a user, because
obviously I cannot write to /gnu/store.
Could you give me a hint how to run guix on Darnassus?
--
Ricardo
GPG: BCA6 89B6 3655 3801 C3C6 2150 197A 5888 235F ACAC
https://elephly.net
next prev parent reply other threads:[~2017-10-09 21:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-26 15:58 bug#28243: Guix cross-compilation doesn't work Manolis Ragkousis
2017-08-28 23:15 ` Ludovic Courtès
2017-10-09 21:34 ` Ricardo Wurmus [this message]
2017-10-12 11:12 ` Manolis Ragkousis
2017-10-12 21:53 ` Ricardo Wurmus
2020-08-11 8:45 ` Jan Nieuwenhuizen
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=87k204m2ef.fsf@elephly.net \
--to=rekado@elephly.net \
--cc=28243@debbugs.gnu.org \
--cc=ludo@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.