From mboxrd@z Thu Jan 1 00:00:00 1970 From: ludo@gnu.org (Ludovic =?utf-8?Q?Court=C3=A8s?=) Subject: Re: [GSoC update] Porting Guix to GNU/Hurd Date: Sun, 23 Aug 2015 19:44:29 +0200 Message-ID: <87fv39zypu.fsf@gnu.org> References: Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:34050) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZTZJx-0007UB-NF for Guix-devel@gnu.org; Sun, 23 Aug 2015 13:44:42 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1ZTZJw-0007rb-K7 for Guix-devel@gnu.org; Sun, 23 Aug 2015 13:44:41 -0400 In-Reply-To: (Manolis Ragkousis's message of "Wed, 19 Aug 2015 22:23:34 +0300") List-Id: "Development of GNU Guix and the GNU System distribution." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org Sender: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org To: Manolis Ragkousis Cc: Guix-devel , GNU Hurd , Samuel Thibault Hi! Manolis Ragkousis skribis: > 1) Guix can successfully cross-build any package for the Hurd and produce > the bootstrap-tarballs to build packages with Guix natively on such a sys= tem. > > 2) Guix can build the native final toolchain. > > 3) Guix can build packages natively using the final toolchain. > > Even though most of the work is already present in the wip-hurd branch, t= here > are still some patches to be reviewed/merged. This will happen asap. > > But nevertheless we can safely say we have ported Guix to Hurd. :-) Congratulations on that! That=E2=80=99s a great achievement, and I know th= ere were some bumps on the road, and the project covers several very different pieces of software, so thumbs up! > 2) guix/build/syscalls (mount, umount, setns ) Those aren't available > on Hurd, so > building Guix would fail. It seems turning them into procedures is > enough to work > around this. This module is only used by GuixSD anyway (not Guix itself), so no problem. In the interim, we should perhaps arrange to not build that module when, say, =E2=80=98mount=E2=80=99 is missing (using an =E2=80=98AM_CONDITIONAL= =E2=80=99.) > 4) Perl could not be build because of a problem with memmove in hurd's > glibc. Together > with Samuel and Justus we traced the problem to a not properly tested > part of glibc. > Fixed. Pheew. :-) > 5) glibc-intermediate could not find the gnumach/hurd headers because > of unsetting the > path during the build process. It seems that glibc's sysdeps/mach and > sysdeps/mach/hurd > configure weren't using the --with-headers variable to get the > headers. Fixed that and sent > the patch to bug-hurd :-). OK. > 6) Binaries produced from gcc-boot0 had problems with their runpath > and validate-runpath? > was failing. It seems ld wasn't passing -rpath to them. Added an > ld-wrapper, solved. Interesting, will look at the patch hopefully soon. > 7) glibc-final's debug output refers to %glibc-bootstrap. I think this > happens indirectly through > the headers, currently solving that. Would be nice to understand why that happens. In the meantime you could disable #:allowed-references altogether for that package when on GNU/Hurd, if you want. > Also, I am near finishing sys/mount.h for Hurd. Will finish it as soon > as possible. Great! > I get the feeling I forgot some things so please remind/ask me > anything. For the next two > days I will wrap up patches and push them to wip-hurd. After that I > will continue working on > getting the full GuixSD experience on Hurd. And one of these days we > will deploy guix on > darnassus together with rbraunr. I will inform you when that happens. Excellent. Thanks to the Hurd and Guix people for giving you a hand! Cheers, Ludo=E2=80=99.