Added cross-compilation binutils and kernel-headers.

[PawelWMS]

Merge Checklist

All boxes should be checked before merging the PR (just tick any boxes which don't apply to this PR)

• The toolchain has been rebuilt successfully (or no changes were made to it)
• The toolchain/worker package manifests are up-to-date
• Any updated packages successfully build (or no packages were changed)
• Packages depending on static components modified in this PR (Golang, *-static subpackages, etc.) have had their Release tag incremented.
• Package tests (%check section) have been verified with RUN_CHECK=y for existing SPEC files, or added to new SPEC files
• All package sources are available
• cgmanifest files are up-to-date and sorted (./cgmanifest.json, ./toolkit/scripts/toolchain/cgmanifest.json, .github/workflows/cgmanifest.json)
• LICENSE-MAP files are up-to-date (./SPECS/LICENSES-AND-NOTICES/data/licenses.json, ./SPECS/LICENSES-AND-NOTICES/LICENSES-MAP.md, ./SPECS/LICENSES-AND-NOTICES/LICENSE-EXCEPTIONS.PHOTON)
• All source files have up-to-date hashes in the *.signatures.json files
• sudo make go-tidy-all and sudo make go-test-coverage pass
• Documentation has been updated to match any changes to the build system
• Ready to merge

---

Summary

This is a fix for a breaking change I introduced in #6815. The original change caused other package to start failing with the configure: error: C compiler cannot create executables error and the native binutils package contained cross-<binary_name>.mo files meant for cross-binutils-common instead of the plain <binary_name>.mo. The original change was reverted and this is an updated version.

The main changes are:

• Instead of using a single directory with the sources for binutils and have multiple configure and make calls point to that directory, I've added copies of the source for each pair of configure and make calls. For reasons still unknown to me, the original approach caused the configure: error: C compiler cannot create executables error. I'd greatly appreciate an explanation from someone more experienced, what was wrong and how to avoid copying the original sources. For now, however, that I've implemented the said workaround and created a separate bug to address it in the future.
• Updated the build steps to produce the cross-<binary_name>.mo only for the cross-binutils-common subpackage.

Change Log

• Fixed the build issues with packages depending on binutils.
• Fixed .mo files generation in binutils.spec.

Does this affect the toolchain?

Yes.

Associated issues

• Added cross-binutils and kernel-cross-headers for AMD64. #6815

Test Methodology

• Local build and test of binutils along with a build of a libdb as a test of introduced changes.
• Fast-track style PR check run.
• Full dev build.

[PawelWMS]

Builds finished successfully, merging.