[*/2018b] add patch to fix building Qt5 v5.10.1 against newer glibc

[branfosj]

(created using eb --new-pr)

• add ld.gold relocts patch to binutils 2.30 #13785

[branfosj]

Test report by @branfosj
SUCCESS
Build succeeded for 1 out of 1 (1 easyconfigs in total)
bear-pg0211u08b.bear.cluster - Linux RHEL 8.3, x86_64, Intel(R) Xeon(R) Gold 6248 CPU @ 2.50GHz (cascadelake), Python 3.6.8
See https://gist.github.com/70c2c611792249248c00a4445284c1c6 for a full test report.

[branfosj]

@boegelbot please test @ generoso
CORE_CNT=16

[boegelbot]

@branfosj: Request for testing this PR well received on generoso

PR test command 'EB_PR=13730 EB_ARGS= /apps/slurm/default/bin/sbatch --job-name test_PR_13730 --ntasks="16" ~/boegelbot/eb_from_pr_upload_generoso.sh' executed!

• exit code: 0
• output:

Submitted batch job 18176

Test results coming soon (I hope)...

- notification for comment with ID 903109853 processed

Message to humans: this is just bookkeeping information for me,
it is of no use to you (unless you think I have a bug, which I don't).

[branfosj]

Test report by @branfosj
SUCCESS
Build succeeded for 39 out of 39 (2 easyconfigs in total)
bber0501u03a.bb2.cluster - Linux RHEL 8.3, x86_64, Intel(R) Xeon(R) CPU E5-2690 v3 @ 2.60GHz (haswell), Python 3.6.8
See https://gist.github.com/4a06c3a605036b4d7486ee8423519d40 for a full test report.

[boegelbot]

Test report by @boegelbot
FAILED
Build succeeded for 6 out of 12 (3 easyconfigs in total)
generoso-x-1 - Linux centos linux 8.2.2004, x86_64, Intel(R) Xeon(R) CPU E5-2667 v3 @ 3.20GHz (haswell), Python 3.6.8
See https://gist.github.com/127b2f47454891fcdc0742232af0d715 for a full test report.

[boegel]

Test report by @boegel
FAILED
Build succeeded for 14 out of 15 (3 easyconfigs in total)
node3133.skitty.os - Linux centos linux 7.9.2009, x86_64, Intel(R) Xeon(R) Gold 6140 CPU @ 2.30GHz, Python 3.6.8
See https://gist.github.com/5d24e655ee7816016ab675328b50c6c5 for a full test report.

[branfosj]

So, this fixes the build issue for Qt5 5.10.1 foss and fosscuda versions. There are more issues with intel / 2018b. I do not have that available to test / debug.

[boegel]

See #8003 w.r.t. the failing build with intel/2018b.

We never backported the binutils patch to binutils/2.30-GCCcore-7.3.0 used there, so no surprise the issue still stands.

I won't let that block this PR though, the effort required to fix that problem is probably no longer worth it...