From mboxrd@z Thu Jan  1 00:00:00 1970
From: =?utf-8?Q?Ludovic_Court=C3=A8s?= <ludo@gnu.org>
Subject: Re: `guix build hello' now succeeds on the Hurd
Date: Mon, 09 Mar 2020 18:10:21 +0100
Message-ID: <87imjdzc76.fsf@gnu.org>
References: <878skd94d4.fsf@gnu.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Return-path: <guix-devel-bounces+gcggd-guix-devel=m.gmane-mx.org@gnu.org>
Received: from eggs.gnu.org ([2001:470:142:3::10]:56442)
 by lists.gnu.org with esmtp (Exim 4.90_1)
 (envelope-from <ludo@gnu.org>) id 1jBLv5-0005lB-Tv
 for guix-devel@gnu.org; Mon, 09 Mar 2020 13:10:24 -0400
In-Reply-To: <878skd94d4.fsf@gnu.org> (Jan Nieuwenhuizen's message of "Fri, 06
 Mar 2020 11:15:03 +0100")
List-Id: "Development of GNU Guix and the GNU System distribution."
 <guix-devel.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/guix-devel>,
 <mailto:guix-devel-request@gnu.org?subject=unsubscribe>
List-Archive: <https://lists.gnu.org/archive/html/guix-devel>
List-Post: <mailto:guix-devel@gnu.org>
List-Help: <mailto:guix-devel-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/guix-devel>,
 <mailto:guix-devel-request@gnu.org?subject=subscribe>
Errors-To: guix-devel-bounces+gcggd-guix-devel=m.gmane-mx.org@gnu.org
Sender: "Guix-devel"
 <guix-devel-bounces+gcggd-guix-devel=m.gmane-mx.org@gnu.org>
To: Jan Nieuwenhuizen <janneke@gnu.org>
Cc: guix-devel@gnu.org

Hello!

Jan Nieuwenhuizen <janneke@gnu.org> skribis:

> The situation on the Hurd starts to look pretty good
>
>     janneke@debian:~/src/guix$ ./pre-inst-env guix build hello --no-offlo=
ad
>     /gnu/store/a2sylb94rm1b6qxcp5mqvgiyx9szipz7-hello-2.10
>     janneke@debian:~/src/guix$ /gnu/store/a2sylb94rm1b6qxcp5mqvgiyx9szipz=
7-hello-2.10/bin/hello
>     Hello, world!
>
> \o/

Woohoo!  Congrats!

How do you run guix-daemon?  (In the future it=E2=80=99d be great to perhaps
implement Linux namespaces on the Hurd in libc.)

> It has some 20 odd patches.  I chose to create workarounds to "get early
> success" rather than doing everything right.  While I worked on forward
> porting glibc patches, I only took the minimal set that I needed.  Also,
> I reverted to make 4.1 instead of debugging why make 4.3 fails (for
> now).

OK.

> Most controversial/problematic is the need to use fairly recent gnumach
> and hurd sources.

That=E2=80=99s OK IMO.

> What could be the next step?

Merging what you have=E2=80=94the earlier the better.  :-)

> Shall I push this to savannah as `wip-hurd' (possibly save wip-hurd->
> `wip-hurd-old?);

Yup, sounds like a plan.

> I could also rewrite wip-hurd-bootstrap?

Dunno!

To me, the difficult bit with porting and bootstrapping work is making
sure that bootstrap.scm/commencement.scm/base.scm/cross-base.scm remain
maintainable.  All this complexity adds up so we must spend time trying
to, for instance, minimize variation across platforms/OSes.  Every line
of code and above all every conditional avoided in these files is a win
in the not-so-long term.  That=E2=80=99d be my guideline as we merge it.  :=
-)

Anyhow, thumbs up!  I=E2=80=99m looking forward to merging it and having it
built on CI (we could offload to a Debian VM!)!

Ludo=E2=80=99.