[hurd-team]: Update mig and gnumach. #6487
No reviewers
Labels
No labels
closure-size
deprecation
good first issue
help-wanted
kind
bug
kind
foreign-distro
kind
moreinfo
kind
system-test
kind
wishlist
kind
wont-fix
package
fix
patch-upgrade
security-fixes
team-ai
team-audio
team-beam
team-bioinformatics
team-bootstrap
team-build-tools
team-core
team-core-packages
team-cpp
team-crypto
team-documentation
team-electronics
team-emacs
team-embedded
team-games
team-gnome
team-go
team-guile
team-hare
team-haskell
team-home
team-hpc
team-hurd
team-installer
team-java
team-javascript
team-julia
team-kde
team-kernel
team-lisp
team-localization
team-lua
team-lxqt
team-mate
team-mozilla
team-ocaml
team-perl
team-python
team-qa-packages
team-qt
team-r
team-racket
team-release
team-reproduciblebuilds
team-ruby
team-rust
team-science
team-sugar
team-sysadmin
team-telephony
team-tex
team-translations
team-vcs
team-xfce
team-zig
user-reviewed
world-rebuild
No milestone
No project
No assignees
3 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
guix/guix!6487
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "Yelninei/guix:hurd-team"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
However it is an abi breaking change (on x86_64 because i586 has no 64bit memebrs in rpcs) and needs new bootstrap files as the old ones dont work with the new format of the mach RPCs..
Ive also included a gnumach update as we are already rebuilding everything.
For commencement.scm I removed the
git-fetch-from-tarballas the tarballs are no longer available from savannah. Maybe this needs an immediate SWH fallback when git-download is not available?We might be able to remove some
system-hurd64code that is now obsolete but this is untested for the reason above.With a rebuild bootstrap files glibc-intermiate fails with a python error? I have never seen this?
math.cpython-35m-i386-gnu.so does not seem to get build
building 'math' extension
gcc -fPIC -Wno-unused-result -Wsign-compare -DNDEBUG -g -O3 -Wall -Wstrict-prototypes -Werror=declaration-after-statement -I./Include -I. -I/tmp/guix-build-python-boot0-3.5.9.drv-0/Python-3.5.9/Include -I/tmp/guix-build-python-boot0-3.5.9.drv-0/Python-3.5.9 -c /tmp/guix-build-python-boot0-3.5.9.drv-0/Python-3.5.9/Modules/mathmodule.c -o build/temp.gnu-0.9-x86_64-3.5/tmp/guix-build-python-boot0-3.5.9.drv-0/Python-3.5.9/Modules/mathmodule.o
/tmp/guix-build-python-boot0-3.5.9.drv-0/Python-3.5.9/Modules/mathmodule.c:70:1: error: static declaration of 'sinpi' follows non-static declaration
70 | sinpi(double x)
| ^~~~~
In file included from /gnu/store/psd26il0iv7lmlgfpbaby5pl9payscjv-glibc-bootstrap-0/include/features.h:524,
from /gnu/store/psd26il0iv7lmlgfpbaby5pl9payscjv-glibc-bootstrap-0/include/bits/libc-header-start.h:33,
from /gnu/store/psd26il0iv7lmlgfpbaby5pl9payscjv-glibc-bootstrap-0/include/limits.h:26,
from ./Include/Python.h:11,
from /tmp/guix-build-python-boot0-3.5.9.drv-0/Python-3.5.9/Modules/mathmodule.c:55:
/gnu/store/psd26il0iv7lmlgfpbaby5pl9payscjv-glibc-bootstrap-0/include/bits/mathcalls.h:81:1: note: previous declaration of 'sinpi' with type 'double(double)'
81 | __MATHCALL_VEC (sinpi,, (Mdouble __x));
| ^~~~~~~~~~~~~~
See this
github.com/python/cpython@f57cd8288din cpython.A simple
s/sinpi/m_sinpiresolves the conflict. Should i add this link somewhere in commencement or in the commit?94b9c8585dto0b67e051f80b67e051f8to90bdd0ca2990bdd0ca29to2dc2a845c32dc2a845c3to1354bb50f91354bb50f9to0312687c610312687c61to32d370c2d8m4 tests fail to compile with gcc-14, removed the patch that removed the CFLAGS.
32d370c2d8tof457045474I added a commit to change crash server to crash-kill as crash-dump-core currently hangs.
Then also added back all the things that I removed before because the errors were casued by exactly this.
this recent commit might at least solve crash-dump-core hanging causing e.g. raise(SIGABRT) to hang.
https://cgit.git.savannah.gnu.org/cgit/hurd/hurd.git/commit/?id=c809367cb503830346bfb1d1fd927c09d3f3cb16
salsa.debian.org/hurd-team/hurd/-@03974e4494f457045474tocbc28ac2adcbc28ac2adtoc326d55836Setting crash to crash-kill causes a test failure in guile
Running time.testa
FAIL: time.test: internal-time-units-per-second: versus times and sleep
?
aa2ded3611to4e44c51e7f4e44c51e7fto59d7397f1fI have built all the things successfully which were causing problems before so this also fixes guix/guix#1041
THe things that solve these is the mig update and the patch to make
crash-dump-corenot hang when handling SIGABRT/abort.Resolving this also allows simplifying of some tests that were previously skipped because of a hang but now PASS/XFAIL as expected.
I also looked for some
system-hurd64?andtarget-hurd64?checks if they can be removed.The changes for grep and m4 need the package update on core-packages team to fully get rid of.
There is still some issue with e2fsprogs hanging, this seems fine with
-M pcand a lower ram?The python test hang does not make sense to me right now so I am skipping it for now to move things forward.
The mig change needs updated bootstrap files for x86_64-gnu and old binaries are incompatible. @janneke
I am not sure about removing the
git-fetch-from-tarballin commencement?Savannah does not serve them anymore and we cant determine a hash for SWH fallback of the snapshot taraball.
Is it fine to just consider old daemons as unsupported, should it fallback to SWH immediately if builtin:git-download is not available? @civodul
While building commencement.scm with glibc 2.41 I found an incompatibility with the ancient python-boot0 and libm both providing a
sinpisymbol . The fix in python was to just rename theirs so I followed that.This cahnge is also in the loongarch PR
WIP: [hurd-team]: Update mig and gnumach.to [hurd-team]: Update mig and gnumach.9b2ed8d079to7c8aec4921Some things that I noticed while rebuilding with the new headers and am not sure what to do about them.
These tests hang but work when using
-M pcin qemu, so there maybe is a qemu bug here or somthing else that we are still missingcheck is pretty important as it it pretty deep in the dependency graph but I'd rather not put workarounds for packages that work with different qemu settings.
Results of evaluation 71002 for commit
59d7397f1f:gcc-cross-i586-pc-gnu-toolchain-14.3.0,gcc-cross-x86_64-pc-gnu-toolchain-14.3.0Results of evaluation 82710 for commit
9b2ed8d079:gcc-cross-i586-pc-gnu-toolchain-14.3.0,gcc-cross-x86_64-pc-gnu-toolchain-14.3.0I have rebased this onto latest master, built the bootstrap binaries,
uploaded them to https://lilypond.org/janneke/guix/x86_64-gnu/20260301/,
added a commit updating them for x86_64-gnu, and pushed
it as hurd-team.
Currently I'm building the devel-hurd VM image...but I noticed that upstream
just released/tagged another gnumach this week: v1.8+git20260224.
Do we want to update gnumach again before changing the bootstrap binaries?
Looking at the MIG update, I'm wondering why we're not updating to the
latest commit
Oh wait...that's a local commit thit I never upstreamed -- never mind then. Remains the gnumach update; I'll have a look at that. The hurd release that we're using is also pretty old, but there's no new upstream release just yet...
Okay, I upgraded gnumach and hurd, pushed to hurd-team, and created and uploaded new
bootstrap binaries.
Successfully built a devel-hurd64 image:
Substitutes available via http://dezyne.org:8181, as always.
I guess updating bootstrap binaries for a new achitecture a couple of times can be OK. I'm just hoping we won't need another update for quite some time, that's also why I updated gnumach and hurd to latest greatest.
WDYT, @Yelninei, @civodul, @efraim?
@janneke Does it boot? I tried to cherry pick some ext2fs patches in hopes that the e2fsprogs/check/qemu problem would go away but i ended up with a system that did not boot, but maybe i was missing some
As discussed on IRC; yes, it boots!
Before we merge this, I propose to remove
and update the commit hash mentioned in commit message
Then, I guess the build farm's childhurds need to upudated as well.
@janneke I am currently rebuilding commencement.scm for i586 and x86_64.
I hope the (remaining) problems on x86_64 from #6487 (comment) are resolved now.
Those tests are working with "-M PC" in qemu but hang on the
-M q35machine we currently use to get more than 3.5Gib memory.checkis a dependency of python and curl so pretty deep in the graph and the ci childhurds not being able to build them would be problematic.EDIT:
ext2fs seems to work now, check tests still seems to hang in the
check_checktest.7c8aec4921tobcbdfc48fcbcbdfc48fcto2a02764670Evaluation failed; see log.
@guix-cuirass-bot wrote in #6487 (comment):
It's unclear to me which commit you've been looking at, @guix-cuirass-bot? It all seems to work for me?
Anyway, I've cherry-picked the commit, removed the first set of bootstrap binaries and its reversal commit, rebased on latest master and pushed to hurd-team.
I had a nesting problem error in the initial commit that skipped tests. (i put arguments inside the origin instead of extra field)
Also it would be great to update the guix package afterwards to have the updated files available from the guix on installed images.
@janneke All packages that previosuly had an error now build
@Yelninei wrote in #6487 (comment):
[..]
That's amazing news! So, do we need anything or can we rebase hurd-team and push to master?