GNU bug report logs -
#78349
[PATCH hurd-team] Allow for a crossbuilt gnumach.
Previous Next
Reported by: yelninei <at> tutamail.com
Date: Sat, 10 May 2025 08:45:01 UTC
Severity: normal
Tags: patch
Done: yelninei <at> tutamail.com
To reply to this bug, email your comments to 78349 AT debbugs.gnu.org.
There is no need to reopen the bug first.
Toggle the display of automated, internal messages from the tracker.
Report forwarded
to
guix-patches <at> gnu.org
:
bug#78349
; Package
guix-patches
.
(Sat, 10 May 2025 08:45:02 GMT)
Full text and
rfc822 format available.
Acknowledgement sent
to
yelninei <at> tutamail.com
:
New bug report received and forwarded. Copy sent to
guix-patches <at> gnu.org
.
(Sat, 10 May 2025 08:45:02 GMT)
Full text and
rfc822 format available.
Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):
[Message part 1 (text/plain, inline)]
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.
[0001-system-hurd-Use-the-regular-gnumach-as-default-kerne.patch (text/x-patch, attachment)]
Information forwarded
to
guix-patches <at> gnu.org
:
bug#78349
; Package
guix-patches
.
(Sat, 24 May 2025 07:20:02 GMT)
Full text and
rfc822 format available.
Message #8 received at submit <at> debbugs.gnu.org (full text, mbox):
Hi,
> 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.
> 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.
> 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 <at> gnu.org> | GNU LilyPond https://LilyPond.org
Freelance IT https://www.JoyOfSource.com | AvatarĀ® https://AvatarAcademy.com
Reply sent
to
yelninei <at> tutamail.com
:
You have taken responsibility.
(Sat, 24 May 2025 15:10:02 GMT)
Full text and
rfc822 format available.
Notification sent
to
yelninei <at> tutamail.com
:
bug acknowledged by developer.
(Sat, 24 May 2025 15:10:02 GMT)
Full text and
rfc822 format available.
Message #13 received at 78349-done <at> debbugs.gnu.org (full text, mbox):
All patches are applied, cleaning up the issues.
This bug report was last modified 13 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.