Relocatable objects (.syso, .o) are link-time inputs that may
legitimately target foreign architectures. For example, Go ships
cross-compilation support files (BoringCrypto, race detector) for
multiple architectures in its source tree.
Only executables (ET_EXEC) and shared libraries (ET_DYN) are runnable
on the host and should determine the package's architecture. This
aligns with how runtimeMetadataScanDisposition already skips
non-runtime ELF types.
Relocatable objects (.syso, .o) are link-time inputs that may
legitimately target foreign architectures. For example, Go ships
cross-compilation support files (BoringCrypto, race detector) for
multiple architectures in its source tree.
Only executables (ET_EXEC) and shared libraries (ET_DYN) are runnable
on the host and should determine the package's architecture. This
aligns with how runtimeMetadataScanDisposition already skips
non-runtime ELF types.