You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The opaque Android (ld.gold) and Windows (as, ld, objcopy) binaries currently carried under tools/lkl/bin/ are very difficult to verify and audit. IMO they should be dropped in favour of some form of environmental dependency.
The text was updated successfully, but these errors were encountered:
same as #538, I'm fine if we keep this in the lkl repository or move it to somewhere else.
IIRC, the original intention on those supplemental binary files is to remove in future, when upstream toolset (binutils, etc) accepts our fixes. So, those are temporary one and never planned to upstream to Linux mainline.
ddiss
added a commit
to ddiss/opensuse-kernel
that referenced
this issue
Jan 24, 2025
Some Windows and arm binaries are carried under tools/lkl/bin that
needn't be. Delete them and only retain the bin/lkl-hijack.sh wrapper
script.
This will break Windows and Android builds / CI unless $PATH is updated
to point to similar binaries. Plain builds on Linux should still be
fine.
A bin/README.txt file is added to document the directory's
PATH-precedence use for BSD builds.
Link: lkl/linux#539
Acked-by: David Disseldorp <[email protected]>
The opaque Android (ld.gold) and Windows (as, ld, objcopy) binaries currently carried under tools/lkl/bin/ are very difficult to verify and audit. IMO they should be dropped in favour of some form of environmental dependency.
The text was updated successfully, but these errors were encountered: