Enable --tui on perf command

[AZaugg]

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 (./LICENSES-AND-NOTICES/SPECS/data/licenses.json, ./LICENSES-AND-NOTICES/SPECS/LICENSES-MAP.md, ./LICENSES-AND-NOTICES/SPECS/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

We had a request to allow perf --tui to work, looking at Make config in perf
https://github.com/torvalds/linux/blob/928f79a188aacc057ba36c85b36b6d1e99c8f595/tools/perf/Makefile.config#L818 looks like slang-devel is needed, adding it to the build requires to get this going

Change Log

• Adding slang-devel to Build requires to allow perf to work in --tui

Does this affect the toolchain?

YES

Associated issues

• #xxxx

Links to CVEs

• https://nvd.nist.gov/vuln/detail/CVE-YYYY-XXXX

Test Methodology

• Still in testing

[mfrw]

We would need to change a few more files to keep the spec and others at lock-step:
Representational PR:

• [AUTOPATCHER-kernel] Kernel upgrade to version 6.6.47.1 - branch 3.0-dev #10239

[AZaugg]

I was kinda unsure if that was required. I looked at and saw that the kernel headers are maintained separately.

[mfrw]

Luckily our PR checks have caught it :)

[AZaugg]

Thanks @mfrw Updated the PR

[AZaugg]

Resolved in #12820