From 209a3bf3026f9d75262dd1e92c04008876b4fbae Mon Sep 17 00:00:00 2001 From: Harmen Stoppels Date: Wed, 13 Mar 2024 17:03:10 +0100 Subject: 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.` --- pytest.ini | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'pytest.ini') 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 -- cgit v1.2.3-70-g09d2