> The question "Does executable / shared libary / object file X plausibly
> match Debian architecture Y?" needs to be answered in a number of places.
Sorry for the delay, I only today found some time to work on this.
> All of them work based on examining the output of file.
... which comes from the ELF/PE header, and produces output meant for humans
that tends to change.
> changes over time. The latter causes implementations to differ. For
> instance, lintian presently lacks support for mipsr6, mipsr6el, nios2,
> or1k, riscv64 and sh3.
nios2 and or1k are obscure archs, riscv64 merely new. On the other hand,
there's as far as I know no way to distinguish between sh3 and sh4 other
than disassembling the file.
As for mipsr6{,el}, I have no such file at hand -- could you send me a
sample so I can have a look?
My current version is at http://github.com/kilobyte/arch-test -- does this
seem to be what you want?
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.
