[PATCH hurd-team] Allow for a crossbuilt gnumach.

  • Done
  • quality assurance status badge
Details
2 participants
  • Janneke Nieuwenhuizen
  • yelninei
Owner
unassigned
Submitted by
yelninei
Severity
normal

Debbugs page

yelninei wrote 10 months ago
(address . guix-patches@gnu.org)(name . Janneke Nieuwenhuizen)(address . janneke@gnu.org)
OPtCRou--F-9@tutamail.com
Hello,

While building a childhurd for core-packages-team I noticed that gnumach is currently build with the i686-linux toolchain rather than the i586-pc-gnu cross toolchain with a comment that a cross-built mach has issues. As I wanted to avoid bootstrapping a second toolchain I tried a to cross-build one and found no issues.

I then tried this is also on master with both i586-pc-gnu and x86_64-pc-gnu and have not noticed something (yet?) that indicates that mach is broken, the system boots and I was able to talk to the guix-daemon.

I marked the target as a [hurd-team] branch in case there is need for some more testing.
From 1ca15aadf75a46467038deaecf801018b8aa2a39 Mon Sep 17 00:00:00 2001
Message-ID: <1ca15aadf75a46467038deaecf801018b8aa2a39.1746864636.git.yelninei@tutamail.com>
From: Yelninei <yelninei@tutamail.com>
Date: Fri, 9 May 2025 18:26:54 +0000
Subject: [PATCH 1/2] system: hurd: Use the regular gnumach as default kernel.

* gnu/system/hurd.scm (%hurd-default-operating-system-kernel,
%hurd64-default-operating-system-kernel): Set to gnumach.

Change-Id: I7d5515c95e2994e2f0c4ae3a43afe4e6575a53ed
---
gnu/system/hurd.scm | 14 ++------------
1 file changed, 2 insertions(+), 12 deletions(-)

Toggle diff (31 lines)
diff --git a/gnu/system/hurd.scm b/gnu/system/hurd.scm
index c9df366f24..1436f7b52c 100644
--- a/gnu/system/hurd.scm
+++ b/gnu/system/hurd.scm
@@ -64,20 +64,10 @@ (define-module (gnu system hurd)
;;; Code:
(define %hurd-default-operating-system-kernel
- (if (system-hurd?)
- gnumach
- ;; A cross-built GNUmach does not work
- (with-parameters ((%current-system "i686-linux")
- (%current-target-system #f))
- gnumach)))
+ gnumach)
(define %hurd64-default-operating-system-kernel
- (if (system-hurd?)
- gnumach
- ;; A cross-built GNUmach does not work
- (with-parameters ((%current-system "x86_64-linux")
- (%current-target-system #f))
- gnumach)))
+ %hurd-default-operating-system-kernel)
(define %base-packages/hurd
;; Note: the Shepherd comes before the Hurd, not just because its duty is to

base-commit: 43de5db0af03f118c10cef43dc3966ff8eabec0e
--
2.49.0
Janneke Nieuwenhuizen wrote 9 months ago
(address . yelninei@tutamail.com)(address . guix-patches@gnu.org)
87zff2qxw4.fsf@gnu.org
Hi,

Toggle quote (6 lines)
> While building a childhurd for core-packages-team I noticed that
> gnumach is currently build with the i686-linux toolchain rather than
> the i586-pc-gnu cross toolchain with a comment that a cross-built mach
> has issues. As I wanted to avoid bootstrapping a second toolchain I
> tried a to cross-build one and found no issues.

Okay, that makes sense. It also makes for the removal of a quirk, so
that's nice.

Toggle quote (5 lines)
> I then tried this is also on master with both i586-pc-gnu and
> x86_64-pc-gnu and have not noticed something (yet?) that indicates
> that mach is broken, the system boots and I was able to talk to the
> guix-daemon.

Good.

Toggle quote (3 lines)
> I marked the target as a [hurd-team] branch in case there is need for
> some more testing.

It works for me, so apparently a long standing cross build problem has
been fixed.

Pushed to master as 8f852885de485098812450711e81c1f446d3acb6

Greetings,
Janneke

--
Janneke Nieuwenhuizen <janneke@gnu.org> | GNU LilyPond https://LilyPond.org
Freelance IT https://www.JoyOfSource.com| Avatar® https://AvatarAcademy.com
yelninei wrote 9 months ago
Closing Issues
(address . 78349-done@debbugs.gnu.org)(address . 78513-done@debbugs.gnu.org)(address . 78351-done@debbugs.gnu.org)(address . 78471-done@debbugs.gnu.org)
OR1ogqy--F-9@tutamail.com
All patches are applied, cleaning up the issues.
Closed
?
Your comment

This issue is archived.

To comment on this conversation send an email to 78349@debbugs.gnu.org

To respond to this issue using the mumi CLI, first switch to it
mumi current 78349
Then, you may apply the latest patchset in this issue (with sign off)
mumi am -- -s
Or, compose a reply to this issue
mumi compose
Or, send patches to this issue
mumi send-email *.patch
You may also tag this issue. See list of standard tags. For example, to set the confirmed and easy tags
mumi command -t +confirmed -t +easy
Or, remove the moreinfo tag and set the help tag
mumi command -t -moreinfo -t +help