| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Divert LCC compiler as a new one, instead of treating it as GNU.
Since old times, Elbrus C/C++/Fortran Compiler (LCC) by MCST has been
passing checks for GNU compilers, so it has been identified as GNU.
Now, with intent of seriously upstreaming its support, it has been
added as a separate LCC compiler, and its version displays not a
supported GCC version, but LCC version itself (e.g. LCC 1.25.19 instead
of GNU 7.3.0).
This commit adds its support for detection, and also converts basically
every check like 'is this compiler GNU?' to 'is this compiler GNU or
LCC?'. The only places where this check is untouched, is where it
regards other platforms where LCC is unavailable (primarily non-Linux),
and where it REALLY differs from GNU compiler.
Note: this transition may break software that are already ported to
Elbrus, but hardly relies that LCC will be detected as GNU; still such
software is not known.
|
| |
|
|
| |
Fix: #19735
|
| |
|
|
|
|
|
| |
Since commit c826745f5a (CPack/DEB: Do not crash when asked for debug
symbols when there are none, 2020-10-29, v3.20.0-rc1~461^2) the test
fails because CPackRPM warns about no sources in which to find debug
symbols. Add expected output for this case.
|
| |
|
|
|
|
|
| |
By default icx and icpx do not add build IDs when linking, so enable
the build ID to make the test pass.
Signed-off-by: William R. Dieter <william.r.dieter@intel.com>
|
| |
|
|
| |
Treat it just like PGI.
|
| |
|
|
| |
Fixes: #21356
|
| | |
|
| |
|
|
|
| |
Debuginfo packages can not be created from programs and
shared libraries that do not have execute permissions.
|
| |
|
|
|
|
|
| |
Every CPack generator sets default CPACK_PACKAGING_INSTALL_PREFIX
variable value differently so test framework should support
that correctly - previous version expected RPM/Deb /usr default and
removed it for Archive packagers as the default there is /.
|
| | |
|
| |
|
|
|
|
|
|
| |
Packages with debuginfo enabled should
still honor defined package file name
if file name is not set to RPM-DEFAULT.
Fixes #16715
|
| |
|
|
|
|
|
|
|
| |
CPack tests can now define one or more
packaging types and that test will be
executed once per generator per packaging
type. This also enables us to set default
values per packaging type for each generator
which makes tests shorter.
|
| |
|
|
|
|
|
|
| |
Content list for a certain test
should be the same between different
generators so whenever possible use
a single expected files list per
file for all generators.
|
| |
|
|
|
|
|
|
|
|
|
| |
Each generator generates its own file
format with different extensions but
they all create those file names by
a certain pattern and all of them
require the same pieces for that pattern
to work. Now we can only provide pieces
once and and each generator will use those
pieces to generate an expected file name.
|
| |
|
|
|
| |
Merge per generator ExpectedFiles scripts
into one per test and move it to test dir.
|
|
|
For greater transparency tests
are moved to a subfolder with
each test having its own dir.
|
