Re: Porting with Guix

Hello, Regarding this topic, performing more tests: * Running with the sudo command 'Screen' works. I think that a user must be set for 'Screen' to run correctly as the Debian project does. buzz@Hurd:~$ sudo /home/buzz/.guix-profile/bin/screen ~/Guix-on-Hurd/pre-inst-env guix-daemon

Re: Porting with Guix

ren...@openmailbox.org skribis: > make[3]: Entering directory '/home/buzz/gits/D/bdwgc' > PASS: cordtest > hurd: Can't add reference on Mach thread FWIW this comes from the Hurd signal handling code in glibc: err = __mach_port_mod_refs (__mach_task_self (), thread,

Re: Porting with Guix

Hello everyone, On 01/05/17 02:23, ren...@openmailbox.org wrote: > gnu/store/1h7p18gpn84kdww5i542k93arw4hhgs8-libgc-7.6.0/lib > make[2]: Leaving directory > '/tmp/guix-build-libgc-7.6.0.drv-0/gc-7.6.0' > make check-TESTS > make[2]: Entering directory >

Re: Porting with Guix

Ricardo Wurmus skribis: > ren...@openmailbox.org writes: > >> Now there are two errors related to the 'Check' phase of libgc and >> guile: >> In libgc shows: > > […] > >> building of >> `/gnu/store/y3icscjhkk7pa7dg21xqy46riysi36rn-libgc-7.6.0.drv' timed >> out

Re: Porting with Guix

ren...@openmailbox.org writes: > Now there are two errors related to the 'Check' phase of libgc and > guile: > In libgc shows: […] > building of > `/gnu/store/y3icscjhkk7pa7dg21xqy46riysi36rn-libgc-7.6.0.drv' timed > out after 3600 seconds of silence You can increase the

Re: Porting with Guix

ren...@openmailbox.org, on Wed 04 Jan 2017 18:23:08 -0600, wrote: > PASS: cordtest > building of > `/gnu/store/y3icscjhkk7pa7dg21xqy46riysi36rn-libgc-7.6.0.drv' timed out after > 3600 seconds of silence Ah. Just for information, the libgc testsuite passes fine on Debian GNU/Hurd.

Re: Porting with Guix

Hello Rennes, Please pull the latest changes from my github repo, try again and report back. Manolis

Re: Porting with Guix

Hello Rennes, your previous error is becase Guix uses 4.9 as default which doesn't support non-static initializers. I am currently rebuilding the bootstrap-binaries so you can try again with gcc-5. This error is probably because you are missing guile-2.0-dev. Manolis On 12/30/16 22:40,

Re: Porting with Guix

Hi, On 2016-12-30 12:19, ren...@openmailbox.org wrote: Hi Manolis, I updated Debian GNU/Hurd to 0.9(GNU Hurd 0.9 GNU-Mach 1.8-486/Hurd-0.9 i686-AT386 GNU). Later, I run: $ ./bootstrap + exec autoreconf -vfi autoreconf: Entering directory `.' autoreconf: running: autopoint --force autoreconf:

Re: Porting with Guix

Hi Manolis, I updated Debian GNU/Hurd to 0.9(GNU Hurd 0.9 GNU-Mach 1.8-486/Hurd-0.9 i686-AT386 GNU). Later, I run: $ ./bootstrap + exec autoreconf -vfi autoreconf: Entering directory `.' autoreconf: running: autopoint --force autoreconf: running: aclocal --force -I m4 autoreconf: configure.ac:

Re: Porting with Guix

Hello, Can you rerun guix build command with -K and check the version of gcc being used in the file "/tmp/guix-build-.../environment-variables"? Related to gcc, i see: export

Re: Porting with Guix

I have rebooted, I currently have the Hurd version: GNU Hurd 0.8 GNU-Mach 1.7+git20160607-486/Hurd-0.8 i686-AT386 GNU On 2016-12-28 13:19, Manolis Ragkousis wrote: Hello Rennes, Did you update your daemon and restart it?

Re: Porting with Guix

Hello Rennes, Did you update your daemon and restart it? Manolis On 12/28/16 21:16, ren...@openmailbox.org wrote: > Hi Manolis, > > After successfully compiling with the new branch. > > I run 'guix build hello --no-substitutes', and shows: > > The following derivations will be built: >

Re: Porting with Guix

Hi Manolis, After successfully compiling with the new branch. I run 'guix build hello --no-substitutes', and shows: The following derivations will be built: /gnu/store/7i1nbypavdly0n0858bq9ngrhj8s5i6i-hello-2.10.drv ... /gnu/store/zsgpdqglj2i7i3kz777lv8kbvc9hk57h-bash-4.4.5.drv killing

Re: Porting with Guix

Sorry I forgot this. > Are there additional changes needed compared to Guix 0.12.0? Do you > happen to have a write-up on how to get started with the Hurd and Guix? Well I need to clear my daemon work and merge with guix proper. I haven't and I need to do that.

Re: Porting with Guix

Hey Ricardo, :-D I don't think we have i586 binaries in Guix proper yet. We need to first build them with hydra. Manolis On 12/28/16 20:15, Ricardo Wurmus wrote: > > Hi Manolis, > >> Now on the problem, I suppose you are using the Guix version from my >> github repo? The wip-hurd branch is an

Re: Porting with Guix

Hi Manolis, > Now on the problem, I suppose you are using the Guix version from my > github repo? The wip-hurd branch is an older version which is probably > why you have those issues. I created a new branch in my github repo > called wip-hurd-native for you to clone. I cherry picked my latest >

Re: Porting with Guix

Hello Rennes, First of all thank you for helping with this! Now on the problem, I suppose you are using the Guix version from my github repo? The wip-hurd branch is an older version which is probably why you have those issues. I created a new branch in my github repo called wip-hurd-native for

Porting with Guix

Hi, I'm helping to port some applications to Hurd, with Guix package manager. I am using Debian GNU/Hurd to perform my tests. I have the following error when running the Screen application, and tried to debug as follows: $ screen /home/buzz/.guix-profile/bin/bash [screen is terminating] $