GNU bug report logs -
#78471
[PATCH core-packages-team 0/5] Restoring the Hurd
Previous Next
Reported by: yelninei <at> tutamail.com
Date: Sat, 17 May 2025 14:55:01 UTC
Severity: normal
Tags: patch
Done: yelninei <at> tutamail.com
Full log
View this message in rfc822 format
[Message part 1 (text/plain, inline)]
Your bug report
#78471: [PATCH core-packages-team 0/5] Restoring the Hurd
which was filed against the guix-patches package, has been closed.
The explanation is attached below, along with your original report.
If you require more details, please reply to 78471 <at> debbugs.gnu.org.
--
78471: https://debbugs.gnu.org/cgi/bugreport.cgi?bug=78471
GNU Bug Tracking System
Contact help-debbugs <at> gnu.org with problems
[Message part 2 (message/rfc822, inline)]
All patches are applied, cleaning up the issues.
[Message part 3 (message/rfc822, inline)]
[Message part 4 (text/plain, inline)]
Hello,
Here are (hopefully) the last remaining patches to fix #77709.
I have built things up to bison and automake succesfully.
Some notes:
I am bad at naming things and labelled the glibc patches according to the gnulib-test they fix.
I tried to add comments explaining why things are changed, I hope they are clear enough.
In the pthread-once patch I removed the note from the debian patch regarding the symbol version of pthread-once because as soon as glibc 2.42 is available in guix everything will be built against the 2.42 symbol automatically.
For the --disable-year2038 changes, several packages in commencement.scm already have it unconditionally and this is now repeated twice on i586-gnu by inheriting the args.
Is there a better way to get only the 32bit hurd target than the
(and (target-hurd?)
(not (target64bit?)))
i am using currently?
I dont know what the convention is when the #:configure-flag keyword is added only for a specific target if the keyword is also spliced in or not, but this is only a cosmetic change.
The automake test suite seems to be extremely flaky. It fails when the host glibc is 2.39 because of locale errors on stderr (the test checks for empty stderr) and some other tests that required multiple tries (~8) to get lucky.
However the t/output-order.sh failure due to libgc warnings from the guile driver on stderr currently on master no longer occurs.
Ludovic also mentioned to merge glibc and glibc/hurd again.
Yelninei (5):
gnu: glibc/hurd: Fix gnulib tests.
gnu: findutils: Disable 64bit time_t on the 32bit Hurd.
gnu: util-linux: Disable 64bit time_t on the 32bit Hurd.
gnu: tar: Disable 64bit time_t on the 32bit Hurd.
gnu: bison: Link with pthread on the Hurd.
gnu/local.mk | 3 +
gnu/packages/base.scm | 13 ++
gnu/packages/bison.scm | 10 +-
gnu/packages/commencement.scm | 3 +-
gnu/packages/linux.scm | 7 +-
.../glibc-hurd-2.41-pthread-once.patch | 185 ++++++++++++++++++
.../glibc-hurd-2.41-pthread-sigmask.patch | 22 +++
.../patches/glibc-hurd-2.41-symlink.patch | 32 +++
8 files changed, 271 insertions(+), 4 deletions(-)
create mode 100644 gnu/packages/patches/glibc-hurd-2.41-pthread-once.patch
create mode 100644 gnu/packages/patches/glibc-hurd-2.41-pthread-sigmask.patch
create mode 100644 gnu/packages/patches/glibc-hurd-2.41-symlink.patch
base-commit: 4935a8066168c3efc0520d132b6c6a3116eb5d54
[0001-gnu-glibc-hurd-Fix-gnulib-tests.patch (text/x-patch, attachment)]
[0002-gnu-findutils-Disable-64bit-time_t-on-the-32bit-Hurd.patch (text/x-patch, attachment)]
[0003-gnu-util-linux-Disable-64bit-time_t-on-the-32bit-Hur.patch (text/x-patch, attachment)]
[0004-gnu-tar-Disable-64bit-time_t-on-the-32bit-Hurd.patch (text/x-patch, attachment)]
[0005-gnu-bison-Link-with-pthread-on-the-Hurd.patch (text/x-patch, attachment)]
This bug report was last modified 24 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.