Email or username:

Password:

Forgot your password?
4 comments
Janneke

@bugaevc yeah! It took me quite a while to figure out a nice way to use gcc-14 for the Hurd while keeping the default (currently at gcc-11), avoiding a world rebuild (and probably worse, many subsequent package breakages that would need to be addressed).

It also took some time to figure out why my cross-built executables kept segfaulting, in the end just some tags were missing from upstream (and I hadn't carefully looked at which versions #debian was using).

Also, even the 20240825 debian image does not boot with qemu-8.2.2 (the default in Guix) for me.

Very thankful for all the kind help that I got, again!

@bugaevc yeah! It took me quite a while to figure out a nice way to use gcc-14 for the Hurd while keeping the default (currently at gcc-11), avoiding a world rebuild (and probably worse, many subsequent package breakages that would need to be addressed).

It also took some time to figure out why my cross-built executables kept segfaulting, in the end just some tags were missing from upstream (and I hadn't carefully looked at which versions #debian was using).

M. Grégoire

@janneke
Wonderful! What are you planning to do next, if I may ask?

@bugaevc

Janneke

@mpjgregoire @bugaevc Thanks!

Well, first the installer support for Hurd needs to be merged (<issues.guix.gnu.org/73927>), then this needs to be merged and then there's going to be a blog post.

The obvious next step is a 64bit childhurd service and setting up 64bit chidlhurds on the build farm.

Then, I'm hoping for the awesome Hurd hackers to produce a working rumpnet, and get Hurd to boot on something newer than the X60 (<todon.nl/@janneke/110451493405>).

M. Grégoire

@janneke
The blog post is very important: people underestimate the degree to which the Hurd works and is progressing. But you don't want anyone to get the idea it's ready to be the OS on their main computer either.

@bugaevc

Go Up