[email protected], le lun. 09 mars 2026 13:49:48 +0000, a ecrit: > March 8, 2026 at 9:42 PM, "NexusSfan" <[email protected] > mailto:[email protected]?to=%22NexusSfan%22%20%3Cnexussfan%40seznam.cz%3E > > wrote: > > On 3/8/26 6:23 PM, Samuel Thibault wrote: > > > Getting data on gnu.hurd.org is not cumbersome because of the cvs commit > > > (that's not more difficult than a git commit), but because publishing on > > > gnu.hurd.org means endorsing the content, which I haven't taken the time > > > to do in the past few years. > > How does one get the content endorsed? Do we email the FSF ?
I just need to proofread the content. For the recent content, I usually have (which is why for the faq, I could just copy over and commit), but for other pages, they haven't necessarily received a proofread. > > > iocaine could be used, but as usual with all the recent tools, they > > > depend on dozens of libraries which have the tendency of depending on > > > only very standard setups (x86_64 linux). Iocaine does build after some > > > fixups, but it fails to start on i386-hurd: > > > thread 'main' (1) panicked at > > > /home/buildd/.cargo/registry/src/index.crates.io-1949cf8c6b5b557f/roto-0.9.0/src/codegen/mod.rs:298:44: > > > called `Result::unwrap()` on an `Err` value: "unsupported architecture" > > > apparently because cranelift, used by roto, doesn't support i386, only > > > x86_64. Perhaps there is some way to tell roto or cranelift to use a > > > > > No, still fails on an x86_64 hurd machine, I've tried it. > > > > > > > > more generic backend rather than an arch-specific backend, their readmes > > > don't say. > > > Samuel > > I'm assuming that using Anubis would be much harder than Iocaine ...? Not necessarily, it just needs to be investigated. Samuel
