--- Begin Message ---
|
Subject: |
Building Guix from within a container |
|
Date: |
Wed, 05 Apr 2017 09:48:35 +0200 |
|
User-agent: |
mu4e 0.9.18; emacs 25.2.1 |
Hi,
I had a lot of trouble building Guix recently (is it related with Guile
2.2?). Or it did build but then 'guix' command produced things like:
;;; WARNING: loading compiled file /home/clement/.config/guix/latest/guix/ui.go
failed:
;;; ERROR: In procedure make_objcode_from_file: bad header on object file:
"\x7fELF\x02\x01\x01�\x00\x00\x00\x00\x00\x00\x00\x00"
;;; note: source file /home/clement/.config/guix/latest/guix/ui.scm
;;; newer than compiled
/gnu/store/my64yq4r2ii0bblvsbfnjq5bnkivvn07-guix-0.12.0-5.1162/share/guile/site/2.0/guix/ui.go
;;; WARNING: loading compiled file
/home/clement/.config/guix/latest/guix/utils.go failed:
;;; ERROR: In procedure make_objcode_from_file: bad header on object file:
"\x7fELF\x02\x01\x01�\x00\x00\x00\x00\x00\x00\x00\x00"
;;; note: source file /home/clement/.config/guix/latest/guix/utils.scm
;;; newer than compiled
/gnu/store/my64yq4r2ii0bblvsbfnjq5bnkivvn07-guix-0.12.0-5.1162/share/guile/site/2.0/guix/utils.go
;;; WARNING: loading compiled file
/home/clement/.config/guix/latest/guix/config.go failed:
;;; ERROR: In procedure make_objcode_from_file: bad header on object file:
"\x7fELF\x02\x01\x01�\x00\x00\x00\x00\x00\x00\x00\x00"
;;; note: source file /home/clement/.config/guix/latest/guix/config.scm
;;; newer than compiled
/gnu/store/my64yq4r2ii0bblvsbfnjq5bnkivvn07-guix-0.12.0-5.1162/share/guile/site/2.0/guix/config.go
I finally got it to work by using 'guix environment -C -N guix'. Is it
the right way to build Guix? If so, here is a patch that updates the
documentation.
--- End Message ---
--- Begin Message ---
|
Subject: |
Re: bug#26366: [PATCH] doc: Specify that Guix should be built from within a container. |
|
Date: |
Thu, 13 Apr 2017 23:32:31 +0200 |
|
User-agent: |
mu4e 0.9.18; emacs 25.2.1 |
Ludovic Courtès <address@hidden> writes:
> Hello!
>
> Clément Lassieur <address@hidden> skribis:
>
>> Ludovic Courtès <address@hidden> writes:
>>
>>> Clément Lassieur <address@hidden> skribis:
>>>
>>>> * doc/contributing.texi: add '--container' and '--network' options to the
>>>> 'guix environment guix' command.
>>>
>>> [...]
>>>
>>>> +course, by using Guix! The following command starts a new shell within
>>>> +an isolated container where all the dependencies and appropriate
>>>> +environment variables are set up to hack on Guix:
>>>>
>>>> @example
>>>> -guix environment guix
>>>> +guix environment --container --network guix
>>>> @end example
>>>
>>> What’s the rationale? Was this to address the warnings in your first
>>> message?
>>
>> This was both to address the warnings in my first message, and my build
>> error. I apologize if my message is (still) not clear, but it is
>> difficult to reproduce those bugs, since they are state-dependent.
>
> Yeah, I see.
>
>>> It’s possible and a good way to silence the warnings you were seeing,
>>> but it should work fine without it too.
>>
>> I don't understand why it should work fine. Guix (or Guile-SSH, for
>> example) both depend on Guile 2.0 (which is an input). But let's say
>> that on my system, Guile 2.2 is installed instead. I want to build Guix
>> (or Guile-SSH). I usually do 'guix environment guix' (or 'guix
>> environment guile-ssh'). Then, in my opinion, 'guile --version' should
>> output 2.0, but it outputs 2.2. Is it supposed to build with the wrong
>> Guile? (If I do 'guix environment -C guix', then 'guile --version'
>> outputs 2.0.)
>
> ‘guix environment’ definitely prepends things to PATH et al.
>
> Could it be that you have variable definitions in the wrong Bash init
> files as noted in
> <https://www.gnu.org/software/guix/manual/html_node/Invoking-guix-environment.html#FOOT14>?
Oh... yes that's it :) Sorry the waste of time, I should have followed
the documentation. I close the bug, since I think it's all related to
this.
Thanks,
Clément
--- End Message ---