can't create 32 bit guix container under a 64 bit GuixSD system

  • Done
  • quality assurance status badge
Details
2 participants
  • Ander GM
  • Ludovic Courtès
Owner
unassigned
Submitted by
Ander GM
Severity
important
A
A
Ander GM wrote on 2 Jun 2016 18:46
(address . bug-guix@gnu.org)
20160602184654.1c1da3bc@openmailbox.org
I can't create a 32 bit Guix container, once I setup the container as
it follows:

$ guix environment -N --system=i686-linx --container --ad-hoc
gcc-toolchain@4.9.3 findutils file coreutils sdl2 nano cang yasm
mesa mesa-headers bash -- bash

$ gcc -dumpmachine

returns

x86_64-unknown-linux-gnu instead of i686 .
L
L
Ludovic Courtès wrote on 4 Jun 2016 16:28
control message for bug #23682
(address . control@debbugs.gnu.org)
87vb1pyqn9.fsf@gnu.org
severity 23682 important
L
L
Ludovic Courtès wrote on 5 Jun 2016 00:08
Re: bug#23682: can't create 32 bit guix container under a 64 bit GuixSD system
(name . Ander GM)(address . anthk@openmailbox.org)
871t4cwqsd.fsf@gnu.org
Ander GM <anthk@openmailbox.org> skribis:

Toggle quote (13 lines)
> I can't create a 32 bit Guix container, once I setup the container as
> it follows:
>
> $ guix environment -N --system=i686-linx --container --ad-hoc
> gcc-toolchain@4.9.3 findutils file coreutils sdl2 nano cang yasm
> mesa mesa-headers bash -- bash
>
> $ gcc -dumpmachine
>
> returns
>
> x86_64-unknown-linux-gnu instead of i686 .

Fixed in 40d71e44f5068b28f48bd131940260cc0ab2e2d1, thanks.

Note: in the future ‘guix environment --container’ should probably use
personality(2) to ask for a 32-bit kernel personality in this case.
That’s something we can live without, but it’s a nice bonus.

Ludo’.
L
L
Ludovic Courtès wrote on 5 Jun 2016 00:08
control message for bug #23682
(address . control@debbugs.gnu.org)
87zir0vc7n.fsf@gnu.org
tags 23682 fixed
close 23682 0.10.1
?
Your comment

This issue is archived.

To comment on this conversation send an email to 23682@debbugs.gnu.org

To respond to this issue using the mumi CLI, first switch to it
mumi current 23682
Then, you may apply the latest patchset in this issue (with sign off)
mumi am -- -s
Or, compose a reply to this issue
mumi compose
Or, send patches to this issue
mumi send-email *.patch