On Tue, Oct 16, 2018 at 04:46:44PM +0200, Helmut Grohne wrote: > Package: arch-test > Version: 0.13-1 > File: /usr/bin/elf-arch > User: [email protected] > Usertags: rebootstrap > > I know, hurd-amd64 isn't a thing yet. But when it will be, it will > mostly look like amd64 to elf-arch. Like hurd-i386 is an alias for i386, > hurd-amd64 should be one for amd64.
Have you started to actually mess with preliminary builds of it? Ie, would me pushing such a change immediately help you? Or would it be just as good if I committed it to git for now? Just stripping the hurd- prefix might also work, in case they add hurd-alpha or hurd-riscv128. As for proper hurd support: For some strange reason, Hurd buries its marking deep inside a complex-format section of the ELF object instead of using the readily available field in the header meant for this very purpose. Heck, Hurd even has a value officially assigned (0x04). Not doing this makes recognizing it a lot more complex. But, if false positives are ok for you as long as there are no false negatives, doing it fully doesn't seem urgent. Meow! -- ⢀⣴⠾⠻⢶⣦⠀ ⣾⠁⢰⠒⠀⣿⡁ 10 people enter a bar: 1 who understands binary, ⢿⡄⠘⠷⠚⠋⠀ 1 who doesn't, D who prefer to write it as hex, ⠈⠳⣄⠀⠀⠀⠀ and 1 who narrowly avoided an off-by-one error.
