From: swedebugia <swedebugia@riseup.net>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: "33841@debbugs.gnu.org" <33841@debbugs.gnu.org>
Subject: bug#33841: Building x86-64 on i686 not possible it seems - activation-service-error
Date: Sun, 06 Jan 2019 04:11:40 +0100 [thread overview]
Message-ID: <10F7A02C-46C5-49E4-819D-63A2CDAF7EB2@pretty.Easy.privacy> (raw)
In-Reply-To: <253115d29737fa7b01a28094411bb921@riseup.net>; <87imz33tvh.fsf@gnu.org>;
[-- Attachment #1.1: Type: text/html, Size: 1653 bytes --]
[-- Attachment #1.2: Type: text/plain, Size: 1224 bytes --]
"Ludovic Courtès" <ludo@gnu.org> skrev: (5 januari 2019 18:18:58 CET)
>Hello,
>
>swedebugia@riseup.net skribis:
>
>> time nice -19 ~/src/guix/pre-inst-env guix system build ~/config.scm
>> --system=x86_64-linux
>>
>> building
>> /gnu/store/27raas2bj7sck7vgiicfr2g4h6qrd6ga-activate-service.drv...
>> @ unsupported-platform
>> /gnu/store/27raas2bj7sck7vgiicfr2g4h6qrd6ga-activate-service.drv
>> x86_64-linux
>> while setting up the build environment: a `x86_64-linux' is required
>to
>> build
>> `/gnu/store/27raas2bj7sck7vgiicfr2g4h6qrd6ga-activate-service.drv',
>but
>> I am a `i686-linux'
>
>An i686 machine cannot run and build software for x86_64. You would
>need to set up offloading to do that, or use
>‘qemu-binfmt-service-type’.
>
>So this all looks like “expected” behavior to me.
>
>Does that make sense?
>
>Thanks,
>Ludo’.
OK. Would it be OK to state this somewhere in the manual or am I the only on trying to upgrade from 32->64 bit?
This means that if you take a disk with guix 32 and plug it into a 64 bit machine there are only two ways to use 64 bit. Reinstall from a downloaded USB or build using qemu-binfmt-service-type.
--
Sent from my p≡p for Android.
[-- Attachment #2: pEpkey.asc --]
[-- Type: application/pgp-keys, Size: 3825 bytes --]
next prev parent reply other threads:[~2019-01-06 3:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-23 5:04 bug#33841: Building x86-64 on i686 not possible it seems - activation-service-error swedebugia
2018-12-23 5:07 ` swedebugia
2019-01-05 17:18 ` Ludovic Courtès
2019-01-06 3:11 ` swedebugia [this message]
2019-01-06 3:46 ` Ricardo Wurmus
2019-01-06 10:34 ` swedebugia
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=10F7A02C-46C5-49E4-819D-63A2CDAF7EB2@pretty.Easy.privacy \
--to=swedebugia@riseup.net \
--cc=33841@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 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).