Hi again, sorry for the long silence :p

I've been tinkering around this issue today but I face two problems:

1. With `guix environment`:

Ludovic Courtès <ludo@gnu.org> writes:
> In the meantime one can use ‘guix environment -C --expose=…’ to expose
> directories as /bin and the likes.

I've been trying to do that, say, to expose /lib64/ld-linux-x86-64.so.2
to the container so that I don't need to `patchelf` the executable:

--8<---------------cut here---------------start------------->8---
PROFILE=foo
guix package -p "$PROFILE" -i libstdc++ gcc:lib glibc

guix environment -C \
		 --expose=$PROFILE/lib=/lib64 \
		 --expose=/gnu/store/y7siq9fr3dyccyaig94rpkqfimbiw35f-glibc-2.27 \
     libstdc++ gcc:lib glibc \
		 --ad-hoc bash\
		 -- bash

ambrevar@hostname ~ [env]# file /lib64/ld-linux-x86-64.so.2
/lib64/ld-linux-x86-64.so.2: broken symbolic link to /gnu/store/y7siq9fr3dyccyaig94rpkqfimbiw35f-glibc-2.27/lib/ld-linux-x86-64.so.2
--8<---------------cut here---------------end--------------->8---

The strange thing is that the file
/gnu/store/y7siq9fr3dyccyaig94rpkqfimbiw35f-glibc-2.27/lib/ld-linux-x86-64.so.2
exists in the container.

Am I missing something?

2. 32-bit profile

Marius mentioned the possibility to create a 32-bit profile.  How does
one do that?
`guix package --install` does not support the --system or --target options.
Is it possible possible to install and arbitrary store item?

-- 
Pierre Neidhardt