LCC: link with -lgfortran instead of -llfortran since 1.26.03

Since LCC 1.26.03, compiler developers decided to rename liblfortran to libgfortran (internal reference: mcstbug#131633). The first commit in this MR should fix this, and the problem discussed in #23646 (closed) and causing latest nightly builds on yukari.lab.sun.mcst.ru to fail as for now.

Additionally, there's a bunch other fixes,

that make CMake tests completing successfully on older versions of LCC and/or OS Elbrus, which are (a bit unfortunately) still used by people.

Performed all tests on the following setups:

• Ubuntu20.04.3-gcc9.4.0-x86_64
• Elbrus-OSL4.0-lcc1.23.19
• Elbrus-OSL6.0.1-lcc1.25.14
• Elbrus-OSL6.0-lcc1.25.17
• Elbrus-OSL7.1-lcc1.26.12

All tests were successful, no errors or warnings issued.

Fixes: #23646 (closed)
Backport: release

changed the description

changed title from LCC: link with -lgfortran instead of -llfortran since 1.26.03, and a bunch other fixes to LCC: link with -lgfortran instead of -llfortran since 1.26.03

added 3 commits

• 5c4c211d...8321c3d0 - 2 commits from branch cmake:master
• 57da7a49 - LCC: link with -lgfortran instead of -llfortran since 1.26.03

Compare with previous version

changed the description

changed milestone to %3.23.3

added comp:lcc triage:env-regression workflow:in-review labels

assigned to @brad.king

Warnings:

• Eligible for the 3.23.x branch.
• Eligible for the 3.24.x branch.

The warnings do not need to be fixed, but it is recommended to do so.

@makise-homura thanks. I updated your branch to backport just the main fix for the 3.23 release branch. Let's defer the rest to a separate MR. I pushed a lcc-update branch to your fork to hold them for now.

Do: stage

added workflow:nightly-testing label and removed workflow:in-review label

resolved all threads

mentioned in merge request !7418 (merged)

Do: merge

merged

mentioned in commit 808cbb71

mentioned in commit 746bed40

removed workflow:nightly-testing label

mentioned in commit 49a97416