Re: [GSoC] Guix + Hurd continuation

Quoting Ludovic Courtès (2015-07-02 14:14:57) > Justus Winter <4win...@informatik.uni-hamburg.de> skribis: > > > Quoting Ludovic Courtès (2015-07-02 11:33:29) > >> I think it would work anyway, but would end up starting one instance of > >> /hurd/symlink for each symlink, which is suboptimal. > >

Re: [GSoC] Guix + Hurd continuation

Manolis Ragkousis, le Thu 02 Jul 2015 16:38:54 +0300, a écrit : > > 4. Instead of sitting idle watching build logs ;-), it Would Be Nice™ > > to implement the ‘mount’ and ‘umount’ functions for GNU/Hurd in > > libc, with support for MS_BIND using /hurd/firmlink. > > Of course libc

Re: [GSoC] Guix + Hurd continuation

Hello everyone, On 2 July 2015 at 12:12, Ludovic Courtès wrote: > 0. Run Guix’s ‘./configure --with-courage && make’ and see what > happens. > 1. ‘guix-daemon’ must work correctly on GNU/Hurd. Already started working on them. Will report back today on my first results. > > 2. When bu

Re: [GSoC] Guix + Hurd continuation

Justus Winter <4win...@informatik.uni-hamburg.de> skribis: > Quoting Ludovic Courtès (2015-07-02 11:33:29) >> I think it would work anyway, but would end up starting one instance of >> /hurd/symlink for each symlink, which is suboptimal. > > No, /hurd/symlink doesn't quite work as expected. Curre

Re: [GSoC] Guix + Hurd continuation

Quoting Ludovic Courtès (2015-07-02 11:33:29) > I think it would work anyway, but would end up starting one instance of > /hurd/symlink for each symlink, which is suboptimal. No, /hurd/symlink doesn't quite work as expected. Currently, the shortcut semantics are important for us. Justus

Re: [GSoC] Guix + Hurd continuation

l...@gnu.org (Ludovic Courtès) skribis: > 2. When building natively, surely you’ll find out that some packages > do not build (PATH_MAX!), and that there are assumptions in > hurd.scm and base.scm, such as the fact that GNU/Hurd is a > cross-compilation target and not a native sys

[GSoC] Guix + Hurd continuation

Hello! Now that Manolis managed to produce the bootstrap binaries (yay!), we must plan for what’s next. I think the first thing will be to try and start building things natively, as noted in . That implies a few things: 0. Run G