bug#47089: error: make-session: unbound variable

[Maxim Cournoyer]

Hi,

Mark H Weaver <mhw@netris.org> writes:

> Hi Jean,
>
> Jean Louis <bugs@gnu.support> writes:
>
>> Running guix package manager on Hyperbola GNU/Linux-libre:
>>
>> [root@protected ~]# guix pull --no-substitutes -K
>> accepted connection from pid 876, user root
>> Updating channel 'guix' from Git repository at 
>> 'https://git.savannah.gnu.org/git/guix.git'...
>> Building from this channel:
>>   guix      https://git.savannah.gnu.org/git/guix.git   5a06b83
>> building /gnu/store/0l5krmnzmkyawbh7y7xa808sq7sp30vv-config.scm.drv...
>> building /gnu/store/klcxrfvivkjri4whdpyhsnjywr9ki8br-git.scm.drv...
>> building /gnu/store/6kfhwxxjkrknf9wgv2mawyrrzlbbzli2-hash.scm.drv...
>> building /gnu/store/1imdq47vyanhn2mw4814xz10d4ahyd25-module-import.drv...
>> building 
>> /gnu/store/2zb0ys1iiz7djfgyj234ykzfqcjg27lf-module-import-compiled.drv...
>> building 
>> /gnu/store/dmr42vhl0wsjm413i79dxx5nv6wqvcb8-compute-guix-derivation.drv...
>> Computing Guix derivation for 'x86_64-linux'... |@ build-started
>> /gnu/store/51h0bidlh2w1qhkmy1mc3jdg31jla4b1-module-import-compiled.drv
>> - x86_64-linux
>> /var/log/guix/drvs/51//h0bidlh2w1qhkmy1mc3jdg31jla4b1-module-import-compiled.drv.bz2
>> 2051
>> -@ build-succeeded 
>> /gnu/store/51h0bidlh2w1qhkmy1mc3jdg31jla4b1-module-import-compiled.drv -
>> @ build-started 
>> /gnu/store/rx4xa4pzl258yg3hgxrv8xaasrcc6fkg-Python-3.8.2.tar.xz.drv - 
>> x86_64-linux 
>> /var/log/guix/drvs/rx//4xa4pzl258yg3hgxrv8xaasrcc6fkg-Python-3.8.2.tar.xz.drv.bz2
>>  2083
>> |@ build-log 2083 22
>>
>> Starting download of @ build-log 2083 132
>> /gnu/store/pkzdxf9fhdfx473lphqgydd4q3nk4rql-Python-3.8.2.tar.xz
>> From https://www.python.org/ftp/python/3.8.2/Python-3.8.2.tar.xz...
>> /@ build-log 2083 51
>> error: make-session: unbound variable
>
> 'make-session' should be provided by the Guile-bindings included in
> GnuTLS.  It might be that the GnuTLS provided by Hyperbola wasn't
> compiled with Guile support, or provides Guile support but for a
> different version of Guile than the one you're using to run Guix.
>
> What method did you use to install Guix?
>
> It looks like you compiled Guix from source using Hyperbola's native
> toolchain, libraries, and Guile.  If so, you might have better results
> using Guix's binary installer method, which installs a Guix binary that
> avoids using components from your native OS, in favor of components that
> were built by Guix and are known to work correctly with it.

Thanks for your answer, Mark.

I believe it addresses the question, as there haven't been a new reply
in the last 6 months.

Thanks for the report!

Closing.

Maxim