Fix YP compatibility check

[kraj]

---

Contributor checklist

• Changes have been tested
• Signed-off-by is present
• The PR complies with the Open Embedded Commit Patch Message Guidelines

Reviewer Guidelines

• When submitting a review, please pick:
  • 'Approve' if this change would be acceptable in the codebase (even if there are minor or cosmetic tweaks that could be improved).
  • 'Request Changes' if this change would not be acceptable in our codebase (e.g. bugs, changes that will make development harder in future, security/performance issues, etc).
  • 'Comment' if you don't feel you have enough information to decide either way (e.g. if you have major questions, or you don't understand the context of the change sufficiently to fully review yourself, but want to make a comment)

[shr-project]

These were also causing failures for builds with target toolchain gcc as reported on #yocto 2025-07-14

23:17 < JaMa> khem: there is small issue with rust (and rust-llvm) when building with meta-clang, the bbappend there sets TOOLCHAIN_NATIVE to clang, so clang-native is inheritted (even for target builds) and target builds with gcc fail, because they don't recognize --rtlib=libgcc --unwindlib=libgcc when target CC is gcc-cross, I guess you're not seeing this because most builds with meta-clang will use clang also for target
23:17 < JaMa> builds
23:17 < JaMa> not sure what's the correct fix, should clang-native append LDFLAGS only for class-native?

So good I won't need to BBMASK them anymore, thanks :).