diff options
author | Harmen Stoppels <me@harmenstoppels.nl> | 2024-03-13 17:03:10 +0100 |
---|---|---|
committer | Harmen Stoppels <harmenstoppels@gmail.com> | 2024-04-22 15:18:06 +0200 |
commit | 209a3bf3026f9d75262dd1e92c04008876b4fbae (patch) | |
tree | e6e2671f772a0cfc6fff927ba9e125eab0c634e3 /pytest.ini | |
parent | e8c41cdbcb1313eff006e737165ca36611da850c (diff) | |
download | spack-209a3bf3026f9d75262dd1e92c04008876b4fbae.tar.gz spack-209a3bf3026f9d75262dd1e92c04008876b4fbae.tar.bz2 spack-209a3bf3026f9d75262dd1e92c04008876b4fbae.tar.xz spack-209a3bf3026f9d75262dd1e92c04008876b4fbae.zip |
Compiler.default_libc
Some logic to detect what libc the c / cxx compilers use by default,
based on `-dynamic-linker`.
The function `compiler.default_libc()` returns a `Spec` of the form
`glibc@x.y` or `musl@x.y` with the `external_path` property set.
The idea is this can be injected as a dependency.
If we can't run the dynamic linker directly, fall back to `ldd` relative
to the prefix computed from `ld.so.`
Diffstat (limited to 'pytest.ini')
-rw-r--r-- | pytest.ini | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/pytest.ini b/pytest.ini index 617881d77b..2a3152da3d 100644 --- a/pytest.ini +++ b/pytest.ini @@ -12,7 +12,7 @@ markers = requires_executables: tests that requires certain executables in PATH to run nomockstage: use a stage area specifically created for this test, instead of relying on a common mock stage enable_compiler_verification: enable compiler verification within unit tests - enable_compiler_link_paths: verifies compiler link paths within unit tests + enable_compiler_execution: enable compiler execution to detect link paths and libc disable_clean_stage_check: avoid failing tests if there are leftover files in the stage area only_clingo: mark unit tests that run only with clingo only_original: mark unit tests that are specific to the original concretizer |